Warning - upgrade from 5.2.2.0.1562 to 6.1.0.0.935 breaks cluster

[mark_pledl]

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…

[Ankush_Chandan · Accepted solution]

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

[mark_pledl]

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.

[Ankush_Chandan]

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

[Ankush_Chandan]

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

[Ankush_Chandan · Accepted solution]

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

[mark_pledl]

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