[Bug 1708008] Re: rabbitmq-server 3.5.7-1ubuntu0.16.04.2 security update dumped durable queues for autopkgtest.ubuntu.com

[Iain Lane]

I've since found out about delivery_mode=2 (persistence) and applied
that when we insert messages from autopkgtest. I think it's possible
that this is "not a bug" and we should have used this all along if we
wanted messages to survive restarts?

https://www.rabbitmq.com/tutorials/amqp-concepts.html

"Durability of a queue does not make messages that are routed to that
queue durable. If broker is taken down and then brought back up, durable
queue will be re-declared during broker startup, however, only
persistent messages will be recovered."

If you retry the test with delivery_mode=2, is everything okay?

-- 
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/1708008

Title:
  rabbitmq-server 3.5.7-1ubuntu0.16.04.2 security update dumped durable
  queues for autopkgtest.ubuntu.com

Status in rabbitmq-server package in Ubuntu:
  Triaged

Bug description:
  A rabbitmq-server security update was released today.  This was auto-
  applied to the rabbitmq server that serves autopkgtest.ubuntu.com, and
  as a result, it appears that all the messages that were in the queue
  at the time were dropped.

  According to Iain Lane, we are using durable queues in rabbitmq, so
  this should not have happened.

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