sts-sponsors team mailing list archive

[Dan Streetman <ddstreet@xxxxxxxxxxxxx>]

** Changed in: rabbitmq-server (Ubuntu Disco)
       Status: Confirmed => Won't Fix

** Changed in: rabbitmq-server (Ubuntu Focal)
     Assignee: (unassigned) => Nicolas Bock (nicolasbock)

** Changed in: rabbitmq-server (Ubuntu Eoan)
     Assignee: (unassigned) => Nicolas Bock (nicolasbock)

** Changed in: rabbitmq-server (Ubuntu Bionic)
     Assignee: (unassigned) => Nicolas Bock (nicolasbock)

** Changed in: rabbitmq-server (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: rabbitmq-server (Ubuntu Eoan)
   Importance: Undecided => Medium

** Changed in: rabbitmq-server (Ubuntu Focal)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
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:
  Confirmed
Status in rabbitmq-server source package in Bionic:
  Confirmed
Status in rabbitmq-server source package in Disco:
  Won't Fix
Status in rabbitmq-server source package in Eoan:
  Confirmed
Status in rabbitmq-server source package in Focal:
  Confirmed

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