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

Fri Apr 26 15:58:41 EDT 2019

Is that a hidden command? ‘Cause this is all I get:

admin:utils vmtools
      utils vmtools refresh

admin:utils vmtools

---
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: Bill Talley <btalley at gmail.com>
Sent: Friday, April 26, 2019 3:41 PM
To: Lelio Fulgenzi <lelio at uoguelph.ca>
Cc: Matthew Loraditch <MLoraditch at heliontechnologies.com>; Brian Meade <bmeade90 at vt.edu>; cisco-voip at puck.nether.net; Pawlowski, Adam <ajp26 at buffalo.edu>
Subject: Re: [cisco-voip] looks like we're back to rebooting the cluster

does ‘utils vmtools status’ tell you what you’re looking for (i.e. ‘out of date’ or current)? Or are you looking for more info than is generated by that command?

Sent from an iOS device with very tiny touchscreen input keys.  Please excude my typtos.

On Apr 26, 2019, at 2:32 PM, Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:

My colleague helped me confirm that the initramfs timestamp changes when VMtools is upgraded. I’m going to see if TAC can help by logging in as root and getting a timestamp on the file.

We’ll still plan for a possible issue, but at least this will give us a sense of how possible the problem is.

Lelio

---
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

<image001.png>

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 2:24 PM
To: Matthew Loraditch <MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>>; Brian Meade <bmeade90 at vt.edu<mailto:bmeade90 at vt.edu>>
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>; Pawlowski, Adam <ajp26 at buffalo.edu<mailto:ajp26 at buffalo.edu>>
Subject: Re: [cisco-voip] looks like we're back to rebooting the cluster

Can I see when the last VM tools upgrade happened? We’re on an isolated VM infrastructure, but had partner work done and I wasn’t involved.

---
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

<image001.png>

From: Matthew Loraditch <MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>>
Sent: Friday, April 26, 2019 2:14 PM
To: Brian Meade <bmeade90 at vt.edu<mailto:bmeade90 at vt.edu>>
Cc: Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>; Pawlowski, Adam <ajp26 at buffalo.edu<mailto:ajp26 at buffalo.edu>>; 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

Am I missing something? I mean the way I’m reading it plus the bugs is that if you are on that version and do a vmtools upgrade automatically it can happen?

To me that means every system is vulnerable to the issue. But a second workaround is just disable the auto vmtools upgrade option. As long as one hasn’t happened you are fine.

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>

<image002.png><http://www.heliontechnologies.com/>

<image003.png><https://facebook.com/heliontech>

<image004.png><https://twitter.com/heliontech>

<image005.png><https://www.linkedin.com/company/helion-technologies>

From: Brian Meade <bmeade90 at vt.edu<mailto:bmeade90 at vt.edu>>
Sent: Friday, April 26, 2019 2:04 PM
To: Matthew Loraditch <MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>>
Cc: Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>; Pawlowski, Adam <ajp26 at buffalo.edu<mailto:ajp26 at buffalo.edu>>; 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

Not every system on those affected versions is vulnerable.

On Fri, Apr 26, 2019 at 1:56 PM Matthew Loraditch <MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>> wrote:
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>

<image002.png><http://www.heliontechnologies.com/>

<image003.png><https://facebook.com/heliontech>

<image004.png><https://twitter.com/heliontech>

<image005.png><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<mailto: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

<image001.png>

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<mailto: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

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190426/7c5d6a68/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/7c5d6a68/attachment.png>