8.3.2 Upgrade Question

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

8.3.2 Upgrade Question

Aaron Lewis

Hi all,

 

Last night, I assisted a customer in upgrading a 4-node cluster from 8.2.1 to 8.3.2.   We had an issue where the last node didn’t reboot correctly, due to the default image not changing, and had to boot into the backup image.  From there, I was able to set the 8.3.2 image as default.  Now everything is running 8.3.2 but “version” displays 8.2.1.  A KB (#2021570) references running “system node upgrade-revert -node <nodename>” to fix this.  Can anyone confirm that the command is non-disruptive?  I feel like it should be, as the node is already running 8.3.2 code, but I wanted to make sure.  Thanks!

 

Regards,

Aaron

 

 


_______________________________________________
Toasters mailing list
[hidden email]
http://www.teaparty.net/mailman/listinfo/toasters
Reply | Threaded
Open this post in threaded view
|

RE: 8.3.2 Upgrade Question

Parisi, Justin

Non disruptive every time I’ve run it…

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Aaron Lewis
Sent: Wednesday, May 04, 2016 4:48 PM
To: <[hidden email]> Lists
Subject: 8.3.2 Upgrade Question

 

Hi all,

 

Last night, I assisted a customer in upgrading a 4-node cluster from 8.2.1 to 8.3.2.   We had an issue where the last node didn’t reboot correctly, due to the default image not changing, and had to boot into the backup image.  From there, I was able to set the 8.3.2 image as default.  Now everything is running 8.3.2 but “version” displays 8.2.1.  A KB (#2021570) references running “system node upgrade-revert -node <nodename>” to fix this.  Can anyone confirm that the command is non-disruptive?  I feel like it should be, as the node is already running 8.3.2 code, but I wanted to make sure.  Thanks!

 

Regards,

Aaron

 

 


_______________________________________________
Toasters mailing list
[hidden email]
http://www.teaparty.net/mailman/listinfo/toasters
Reply | Threaded
Open this post in threaded view
|

RE: 8.3.2 Upgrade Question

Aaron Lewis

Thanks.  So, I ran the command and got the following error:

 

Error: command failed: Upgrade attempt failed.

 

When I run the “system node upgrade-revert show” command, the node that had problems doesn’t even display.  At this point, I’m thinking I may need to go through the process of installing the wonky node again.  Any suggestions?

 

From: Aaron Dunlap [mailto:[hidden email]]
Sent: Wednesday, May 4, 2016 1:58 PM
To: Parisi, Justin <[hidden email]>; Aaron Lewis <[hidden email]>; <[hidden email]> Lists <[hidden email]>
Subject: RE: 8.3.2 Upgrade Question

 

Me too…

 

From: [hidden email] [[hidden email]] On Behalf Of Parisi, Justin
Sent: Wednesday, May 4, 2016 3:51 PM
To: NGC-aaron-ivoxy.com <[hidden email]>; <[hidden email]> Lists <[hidden email]>
Subject: RE: 8.3.2 Upgrade Question

 

Non disruptive every time I’ve run it…

 

From: [hidden email] [[hidden email]] On Behalf Of Aaron Lewis
Sent: Wednesday, May 04, 2016 4:48 PM
To: <[hidden email]> Lists
Subject: 8.3.2 Upgrade Question

 

Hi all,

 

Last night, I assisted a customer in upgrading a 4-node cluster from 8.2.1 to 8.3.2.   We had an issue where the last node didn’t reboot correctly, due to the default image not changing, and had to boot into the backup image.  From there, I was able to set the 8.3.2 image as default.  Now everything is running 8.3.2 but “version” displays 8.2.1.  A KB (#2021570) references running “system node upgrade-revert -node <nodename>” to fix this.  Can anyone confirm that the command is non-disruptive?  I feel like it should be, as the node is already running 8.3.2 code, but I wanted to make sure.  Thanks!

 

Regards,

Aaron

 

 





The information contained in this message and any attachments (collectively, the "Transmission") contains proprietary and/or confidential information of the sender’s employer which is protected from disclosure and intended solely for the named recipient(s). If you are not a named recipient, you are prohibited from copying, distributing or using this Transmission. Please contact the sender immediately by returning the e-mail and deleting the original Transmission.


_______________________________________________
Toasters mailing list
[hidden email]
http://www.teaparty.net/mailman/listinfo/toasters
Reply | Threaded
Open this post in threaded view
|

Re: 8.3.2 Upgrade Question

Parisi, Justin
I’d open a case. This sounds vaguely familiar as a bug.

From: Aaron Lewis <[hidden email]>
Date: Wednesday, May 4, 2016 at 5:26 PM
To: Aaron Dunlap <[hidden email]>, Justin Parisi <[hidden email]>, "[hidden email]" <[hidden email]>
Subject: RE: 8.3.2 Upgrade Question

Thanks.  So, I ran the command and got the following error:

 

Error: command failed: Upgrade attempt failed.

 

When I run the “system node upgrade-revert show” command, the node that had problems doesn’t even display.  At this point, I’m thinking I may need to go through the process of installing the wonky node again.  Any suggestions?

 

From: Aaron Dunlap [[hidden email]]
Sent: Wednesday, May 4, 2016 1:58 PM
To: Parisi, Justin <[hidden email]>; Aaron Lewis <[hidden email]>; <[hidden email]> Lists <[hidden email]>
Subject: RE: 8.3.2 Upgrade Question

 

Me too…

 

From: [hidden email] [[hidden email]] On Behalf Of Parisi, Justin
Sent: Wednesday, May 4, 2016 3:51 PM
To: NGC-aaron-ivoxy.com <[hidden email]>; <[hidden email]> Lists <[hidden email]>
Subject: RE: 8.3.2 Upgrade Question

 

Non disruptive every time I’ve run it…

 

From:[hidden email] [[hidden email]] On Behalf Of Aaron Lewis
Sent: Wednesday, May 04, 2016 4:48 PM
To: <[hidden email]> Lists
Subject: 8.3.2 Upgrade Question

 

Hi all,

 

Last night, I assisted a customer in upgrading a 4-node cluster from 8.2.1 to 8.3.2.   We had an issue where the last node didn’t reboot correctly, due to the default image not changing, and had to boot into the backup image.  From there, I was able to set the 8.3.2 image as default.  Now everything is running 8.3.2 but “version” displays 8.2.1.  A KB (#2021570) references running “system node upgrade-revert -node <nodename>” to fix this.  Can anyone confirm that the command is non-disruptive?  I feel like it should be, as the node is already running 8.3.2 code, but I wanted to make sure.  Thanks!

 

Regards,

Aaron

 

 





The information contained in this message and any attachments (collectively, the "Transmission") contains proprietary and/or confidential information of the sender’s employer which is protected from disclosure and intended solely for the named recipient(s). If you are not a named recipient, you are prohibited from copying, distributing or using this Transmission. Please contact the sender immediately by returning the e-mail and deleting the original Transmission.


_______________________________________________
Toasters mailing list
[hidden email]
http://www.teaparty.net/mailman/listinfo/toasters