[cisco-voip] looks like we're back to rebooting the cluster

Fri Apr 26 14:22:43 EDT 2019

The way I read the advisory, is that this is a “happens only if” scenario, namely:

“Cisco has identified an issue where, after a successful VMware Tools upgrade, the initramfs image located in the boot partition is corrupted in varying degrees. This corruption of the initramfs image does not lead to a VMware Tools upgrade failure and the Unified Communications application continues to operate without exhibiting any issues. However, the next time the server node is rebooted for any reason the Linux BootLoader fails to load the initramfs image, which prevents the OS from booting back up.”

I rebooted my lab cluster without an issue does that mean it’s safe to say, even though it’s running the affected version, it was not affected by this bug?

We had our upgrade completed by a partner – so I’m not sure if they upgraded the VMware tools after the initial CUCM upgrades were done or if it’s running the stock tools. I’m guessing no tools upgrade was done, so we’re not actually affected?

I don’t know enough about the virtualization world to know if there are files I can see without having to take down a VM, i.e. can I look at this initramfs image?

---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354 | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>

www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

From: Matthew Loraditch <MLoraditch at heliontechnologies.com>
Sent: Friday, April 26, 2019 1:54 PM
To: Lelio Fulgenzi <lelio at uoguelph.ca>; Pawlowski, Adam <ajp26 at buffalo.edu>; 'cisco-voip at puck.nether.net' <cisco-voip at puck.nether.net>
Subject: RE: [cisco-voip] looks like we're back to rebooting the cluster

What do you mean? It lists the affected releases and the ones with the fix?

Matthew Loraditch

Sr. Network Engineer

p: 443.541.1518<tel:443.541.1518>

w: www.heliontechnologies.com<http://www.heliontechnologies.com/>

 |

e: MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>

[Helion Technologies]<http://www.heliontechnologies.com/>

[Facebook]<https://facebook.com/heliontech>

[Twitter]<https://twitter.com/heliontech>

[LinkedIn]<https://www.linkedin.com/company/helion-technologies>

From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> On Behalf Of Lelio Fulgenzi
Sent: Friday, April 26, 2019 1:49 PM
To: Pawlowski, Adam <ajp26 at buffalo.edu<mailto:ajp26 at buffalo.edu>>; 'cisco-voip at puck.nether.net' <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] looks like we're back to rebooting the cluster

It’s too bad they don’t have instructions on how to check if you are vulnerable. Not that I could figure out anyways. At least there’s a work around. Now to find that recovery disk image.

---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354 | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>

www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> On Behalf Of Pawlowski, Adam
Sent: Friday, April 26, 2019 1:30 PM
To: 'cisco-voip at puck.nether.net' <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] looks like we're back to rebooting the cluster

Maybe you won’t be rebooting it if you don’t patch out for this one

https://www.cisco.com/c/en/us/support/docs/field-notices/703/fn70379.html

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190426/5ed1a1c1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1297 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190426/5ed1a1c1/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 6884 bytes
Desc: image002.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190426/5ed1a1c1/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 431 bytes
Desc: image003.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190426/5ed1a1c1/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 561 bytes
Desc: image004.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190426/5ed1a1c1/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 444 bytes
Desc: image005.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190426/5ed1a1c1/attachment-0004.png>