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

Ubuntu Foundations Team Bug Bot 1870619 at bugs.launchpad.net
Tue Apr 7 04:28:48 UTC 2020


The attachment "rabbitmq-server.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
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
Status in rabbitmq-server package in Ubuntu:
  New
Status in rabbitmq-server source package in Bionic:
  New
Status in rabbitmq-server source package in Disco:
  New
Status in rabbitmq-server source package in Eoan:
  New
Status in rabbitmq-server source package in Focal:
  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]

   * I am not aware of any potential regressions

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



More information about the Ubuntu-openstack-bugs mailing list