topic Re: Warning - upgrade from 5.2.2.0.1562 to 6.1.0.0.935 breaks cluster in SmartZone and Virtual SmartZone

Warning - upgrade from 5.2.2.0.1562 to 6.1.0.0.935 breaks cluster

mark_pledl — Thu, 07 Jul 2022 18:22:11 GMT

Dear Ruckus Crowd,

please be careful when you try to upgrade from 5.2.2.0.1562 aka MR2 release to 6.1.0.0.935.

it might break your cluster and you will have a bad day if you do not have a exported cluster backup or snapshot.

Reproduced with vSZ-E. Testing other models tomorrow.

Setup clean vSZ with 5.2.2.0.1562 or upgrade one to 5.2.2.0.1562. Than make a backup and upgrade to 6.1.0.0.935. Upgrade process will fail after migrating database in step preparing system with cluster operation failed.

You will be able to get access to UI but after restart no cluster process will start any more..

More details will follow.

Best regard,

Mark

PS: kudos to my colleague who found that out the hard way.. because APs for project changed to R350s and he needed to upgrade…

Re: Warning - upgrade from 5.2.2.0.1562 to 6.1.0.0.935 breaks cluster

mark_pledl — Fri, 08 Jul 2022 11:08:26 GMT

Attached 2 screenshots.

vSZ-H fails also upgrade

Upgrade 5.2.2.0.1562 to 6.1.0.0.935

After restart…

Re: Warning - upgrade from 5.2.2.0.1562 to 6.1.0.0.935 breaks cluster

mark_pledl — Fri, 08 Jul 2022 11:06:39 GMT

I can confirm the bug for vSZ-H too.

quite possible also SZ104/SZ124/SZ144 und SZ300 might have same issue - as it seems to be some general thing.

Br,

Mark.

Re: Warning - upgrade from 5.2.2.0.1562 to 6.1.0.0.935 breaks cluster

mark_pledl — Mon, 11 Jul 2022 07:43:20 GMT

I just tested in lab rollback when error message above is happening.

Option 1: Node(s) got not restarted and you click the link and get back to gui: You still can rollback last cluster backup succesful.

Option 2: You restarted the node(s) in panic... services do not come up you need to restore each node from cli.

login
-> restore
-> select desired restore point
-> check node after reboot
-> if you have a cluster with more then one node - do it on the other nodes in same way too as the cli is limited to single node (correct me if I am wrong) and GUI will do whole cluster.

Br,

Mark.

Re: Warning - upgrade from 5.2.2.0.1562 to 6.1.0.0.935 breaks cluster

Ankush_Chandan — Fri, 08 Jul 2022 18:52:59 GMT

Thank you Mark for bringing this to our attention. We have one such issue reported during a recent migration from 5.2.2 to 6.1 and yours is the 2nd case. We will work internally on the lab replication and if this issue is confirmed, we will report it to the engineering team.

It will be great if you could log a support ticket if you haven't already for the reference.

Regards,

-Ankush

Re: Warning - upgrade from 5.2.2.0.1562 to 6.1.0.0.935 breaks cluster

mark_pledl — Fri, 08 Jul 2022 19:50:21 GMT

Dear Ankush,

of course I did (Case 01359290). Simon your colleague already got all my logs and the test installation (off dump) where I was able to reproduce

Just wanted to put a warning here to be carful till it is fixed/confirmed/solved.

Br,

Mark.

Re: Warning - upgrade from 5.2.2.0.1562 to 6.1.0.0.935 breaks cluster

Ankush_Chandan — Fri, 08 Jul 2022 21:19:06 GMT

Thank you Mark,

I have replicated this issue in the lab as well and had a quick discussion with the engineering on this issue. As per engineering the 5.2.2.0.1562 to 6.1.0.0.935 is not a supported upgrade path as the release the 5.2.2.0.1562 MR2 was targeted for 6.1.1(Releasing in next couple of months). The 5.2.2.0.1562 MR2 have changes in the database and binaries as per v/SZ 6.1.1. The Supported upgrade path from v/SZ 5.2.2 to 6.1 will be 5.2.2.0.317 >> 6.1.0.0.935 or 5.2.2.0.1161 >> 6.1.0.0.935.

We acknowledge that we need update the 6.1 Release notes with the correct upgrade path limitations and I have notified our Publications Team to make this change at the earliest. Once again, thank you for bringing this to our attention and we sincerely apologize for the inconvenience caused to you.

Regards,

Ankush

Re: Warning - upgrade from 5.2.2.0.1562 to 6.1.0.0.935 breaks cluster

Ankush_Chandan — Sat, 09 Jul 2022 00:35:28 GMT

Hi Mark,

I have replicated this issue in the lab as well and had a quick discussion with the engineering on this issue. As per engineering the 5.2.2.0.1562 to 6.1.0.0.935 is not a supported upgrade path as the release the 5.2.2.0.1562 MR2 was targeted for 6.1.1(Releasing in next couple of months). The 5.2.2.0.1562 MR2 have changes in the database and binaries as per v/SZ 6.1.1, moreover the fixes that were merged in 5.2.2MR2 cannot be ported to 6.1 which was released earlier than the release of 5.2.2MR2. The Supported upgrade path from v/SZ 5.2.2 to 6.1 will be 5.2.2.0.317 >> 6.1.0.0.935 or 5.2.2.0.1161 >> 6.1.0.0.935.

We acknowledge that we need to update the 6.1 Release notes with the correct upgrade path limitations and I have notified our Technical Publications Team to make this change at the earliest. Once again, thank you for bringing this issue to our attention through forums and we sincerely apologize for the inconvenience caused to you.

Regards,

Ankush

Re: Warning - upgrade from 5.2.2.0.1562 to 6.1.0.0.935 breaks cluster

Ankush_Chandan — Sat, 09 Jul 2022 01:05:17 GMT

Hi Mark,

I have replicated this issue in the lab as well and had a quick discussion with the engineering on this issue. As per engineering the 5.2.2.0.1562 to 6.1.0.0.935 is not a supported upgrade path as the release the 5.2.2.0.1562 MR2 was targeted for 6.1.1(Releasing in next couple of months). The 5.2.2.0.1562 MR2 have changes in the database and binaries as per v/SZ 6.1.1, moreover the fixes that were merged in 5.2.2MR2 cannot be ported to 6.1 which was released earlier than the release of 5.2.2MR2. The Supported upgrade path from v/SZ 5.2.2 to 6.1 will be 5.2.2.0.317 >> 6.1.0.0.935 or 5.2.2.0.1161 >> 6.1.0.0.935.

We acknowledge that we need to update the 6.1 Release notes with the correct upgrade path limitations and I have notified our Technical Publications Team to make this change at the earliest. Once again, thank you for bringing this issue to our attention through forums and we sincerely apologize for the inconvenience caused to you.

Regards,

Ankush

Re: Warning - upgrade from 5.2.2.0.1562 to 6.1.0.0.935 breaks cluster

Ankush_Chandan — Sat, 09 Jul 2022 01:16:49 GMT

Hi Mark,

I have replicated this issue in the lab as well and had a quick discussion with the engineering on this issue. As per engineering the 5.2.2.0.1562 to 6.1.0.0.935 is not a supported upgrade path as the release the 5.2.2.0.1562 MR2 was targeted for 6.1.1(Releasing in next couple of months). The 5.2.2.0.1562 MR2 have changes in the database and binaries as per v/SZ 6.1.1, moreover 5.2.2MR2 have major bug fixes which cannot be ported to 6.1 which was released back in Dec 2021. The Supported upgrade path from v/SZ 5.2.2 to 6.1 will be 5.2.2.0.317 >> 6.1.0.0.935 or 5.2.2.0.1161 >> 6.1.0.0.935.

We acknowledge that we need to update the 6.1 Release notes with the correct upgrade path limitations and I have notified our Technical Publications Team to make this change at the earliest. Once again, thank you for bringing this issue to our attention through forums and we sincerely apologize for the inconvenience caused to you.

Regards,

Ankush

Re: Warning - upgrade from 5.2.2.0.1562 to 6.1.0.0.935 breaks cluster

Ankush_Chandan — Sat, 09 Jul 2022 01:21:54 GMT

Regards,
Ankush

Re: Warning - upgrade from 5.2.2.0.1562 to 6.1.0.0.935 breaks cluster

Ankush_Chandan — Sat, 09 Jul 2022 01:23:37 GMT

Regards,
Ankush

Re: Warning - upgrade from 5.2.2.0.1562 to 6.1.0.0.935 breaks cluster

mark_pledl — Mon, 11 Jul 2022 07:35:41 GMT

Dear Ankush,

thanks for the reply. That is fine for me as my post was just there to "warn" other Ruckus users not to drop into the same "trap".

Br,

Mark

Re: Warning - upgrade from 5.2.2.0.1562 to 6.1.0.0.935 breaks cluster

Ankush_Chandan — Mon, 11 Jul 2022 16:43:15 GMT

Thank you Mark and really appreciate your contributions toward the forum. It will indeed help many customers who may encounter similar problem due to the assumption that 5.2.2.0.1562 is lower version than 6.1.0 and must be upgradable. We have finished the Release documents update/review and those will be posted shortly on the support portal.

Regards,

Ankush

Re: Warning - upgrade from 5.2.2.0.1562 to 6.1.0.0.935 breaks cluster

Ankush_Chandan — Mon, 11 Jul 2022 18:37:24 GMT

To close loop on this Topic, we have updated the 6.1.0 Release notes and Upgrade Guide with supported upgraded path. In addition to that, we have also updated the 5.2.2.0.1562 Release Notes with a Warning on "No Support to upgrade to 6.1.0 Release". Here are the reference Documents:

SmartZone 6.1.0 (GA) Upgrade Guide

https://support.ruckuswireless.com/documents/4057

SmartZone 6.1.0.0.935 (GA) Release Notes

https://support.ruckuswireless.com/documents/4058

SmartZone 5.2.2 (LT-GD MR 2) Release Notes

https://support.ruckuswireless.com/documents/4207

Regards,

Ankush

Re: Warning - upgrade from 5.2.2.0.1562 to 6.1.0.0.935 breaks cluster

mark_pledl — Mon, 11 Jul 2022 20:23:39 GMT

Dear Ankush,

thanks again! Now no one should trap in if he read important part of documents first.

Br,

Mark.

Re: Warning - upgrade from 5.2.2.0.1562 to 6.1.0.0.935 breaks cluster

Orlando_Elias — Thu, 29 Jun 2023 20:35:02 GMT

Here is the final solution to this issue:

Community: v/SZ 5.2.2.0.1562 Upgrade Fail