Upgrade to RabbitMQ server 3.7 is broken about cf-rabbitmq-release HOT 5 CLOSED

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

from cf-rabbitmq-release.

Hi Benjamin. Thank you very much for a detailed report. There are at least two issues here:

1. The link is not set correctly. We'll definitely investigate that. In our testing when upgrading to v240 the link was set as expected but in your situation it clearly was not. We'll try to understand what caused this different behaviour.

2. Canary startup failure. This is most likely caused by RabbitMQ's lack of support for in-place 3.6 to 3.7 upgrade which is the very reason we decided to package both versions in the bosh release. Basically your canary 3.7 node can't join the existing 3.6 cluster. There is a new version property which defaults to 3.6 so that when you upgrade to v240 you should not have had any issues. You ran into that because as I understand you changed the link manually to 3.7. You can read more about the recommended way of migrating to 3.7 here: http://www.rabbitmq.com/blue-green-upgrade.html

We are definitely considering BPM and other ways to simplify this bosh release as it indeed grew more complex than we'd like it to be, especially now with 3.6 and 3.7 packaged together. However we prioritised shipping 3.7 in the bosh release since 3.6 will soon be deprecated

from cf-rabbitmq-release.

Hi Michal,

Indeed, I've blindly set the version: "3.7" property in my deployment manifest. The reason is that there were no warning about that in the v240.0.0 or v239.0.0 release notes. On the contrary, the note about the soon upcoming sunset of version 3.6 led me to upgrading as soon as I could.

Moreover, as I had seen there is some upgrade-related code in the release, I thought the 3.6-to-3.7 in-place upgrade would be supported and smooth. (As I'm no RabbitMQ expert, I wasn't aware of the recommended blue-green way of upgrading a cluster either.)

For my own use-case, the solution is easy. I'm not running a production cluster, so I can wipe it out and rebuild it from scratch. But with one of my clients (relying on the PCF tile), we are not far from going to production. We'll need to think soon and carefully about a proper upgrade path!

Benjamin

from cf-rabbitmq-release.

Hi, I've added a warning to the v239 release notes (this version added 3.7 package).

As for the tile, I sent you a message on Slack to discuss the details. Our immediate plan is for the tile to simply prevent you from doing what you just did manually (if you have 3.6, it should stay on 3.6 but there are new on-demand plans with 3.7 available).

from cf-rabbitmq-release.

#73 has been merged. I've edited the commit message to better reflect the problem (it's not related to upgrading to 3.7 - it's just the same if you remain on 3.6 - the symlink is still not created successfully without this fix). Thank you!

from cf-rabbitmq-release.