Mailing List Archive

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!

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!

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?

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.

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?

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.