Hi Thomas, On Wed, Feb 20, 2019 at 5:48 PM Debian Bug Tracking System <ow...@bugs.debian.org> wrote:
> ---------- Forwarded message ---------- > From: Thomas Goirand <z...@debian.org> > To: 922687-d...@bugs.debian.org > Cc: > Bcc: > Date: Wed, 20 Feb 2019 15:46:00 +0100 > Subject: Log for after the upgrade > Today, I tried again, just to be sure. It looks like I had to completely > shutdown the rabbitmq cluster and start it again so that OpenStack > continues to work. This IMO is clearly an issue with rabbitmq. I'm > therefore closing this bug. Sorry for the noise. Good to hear that. I've started to find any difference in +deb9u1 and +deb9u2 behavior and haven't find any yet :-) > > However, I don't understand why upgrading Erlang forces a stop then > start of rabbitmq-server. Heh, it's because it's easier for me to ensure the new Erlang version is in use after the upgrade. In theory there's a possibility of upgrading Erlang code on-the-fly without restarting the virtual machine, but I'm not sure it's worth to try to do it for Debian packages. Also, the Erlang VM is being updated as well in usual package update scenario. Anyway, sorry for inconvenience. If I'll find a better way of upgrading Erlang packages, I'll implement it. Cheers! -- Sergei Golovan
