[Bug 1870619] Re: rabbitmq-server startup does not wait long enough

[Nicolas Bock]

I created another bug LP: #1874075 that tracks changes to the rabbitmq-
server package.

** No longer affects: rabbitmq-server (Ubuntu)

** No longer affects: rabbitmq-server (Ubuntu Bionic)

** No longer affects: rabbitmq-server (Ubuntu Eoan)

** No longer affects: rabbitmq-server (Ubuntu Focal)

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/1870619

Title:
  rabbitmq-server startup does not wait long enough

Status in OpenStack rabbitmq-server charm:
  New

Bug description:
  [Impact]

   * Rabbitmq-server has 2 configuration settings that affect how long it will wait for the mnesia database to become available
   * The default is 30 seconds x 10 retries = 300 seconds
   * The startup wrapper rabbitmq-server-wait will wait only 10 seconds
   * If the database does not come online within 10 seconds the startup script will fail despite the fact that rabbitmq-server is still waiting for another 290 seconds.
   * This behavior leads to falsely identified failures in OpenStack for example when a Rabbitmq cluster is restarted out of order (LP: #1828988)

  [Test Case]

   * Create Rabbitmq cluster and create a queue with "ha-mode: all" policy
   * Shut down nodes one by one
   * Restart the node that was shut down first
   * This node will fail to start because it was not the master of the queue
   * Note that the startup script (SysV or systemd) will fail after 10 seconds while the rabbitmq-server process is still waiting for the database to come online

  [Regression Potential]

   * This change potentially increases the time the rabbitmq-server service takes to start up which might lead to failures down the dependency chain of startup services.
   * This change potentially changes the result of starting the rabbitmq-server service in case the mnesia database takes more than 10 seconds to come online. Without this change, the service will incorrectly fail while it will succeed with this change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1870619/+subscriptions