Comment 78 for bug 1874075

Performing verification for rabbitmq-server in -proposed for bionic.

I installed 3.6.10-1ubuntu0.3 from -proposed, and followed the instructions I wrote in comment #59.

I sent a message to host 1, checked that host 1 was master, and host 2 was the slave. I shut host 1 down, and then sent a message to host 2. Host 2 became the new master. I shut host 2 down. I then started host 1 up again.

The rabbit service came up in a "activating" state, due to ExecStartPost=/usr/lib/rabbitmq/bin/rabbitmq-server-wait kicking in. I looked at /var/log/rabbitmq/host1.log, and rabbit logged its attempts to sync with host 2 every 30 seconds, for 10 tries. At this point, /usr/lib/rabbitmq/bin/rabbitmq-server-wait exits with an error code since it has timed out, and systemd then restarts the service after a 10 second delay. This is all as expected. The service comes back up in the activating state and continues to wait for host 2. I left it like this for 15 minutes, and the rabbitmq-server-wait timeout, restart and waiting all works correctly.

I then started host 2 up, and host 1 rejoined the cluster. Both hosts have the rabbit service in the active state.

The package is behaving as expected on bionic, and I am happy to mark this as verified.