On May 30, 2025 16:02, Clark Boylan <cboylan@sapwetik.org> wrote:

>

> On Fri, May 30, 2025, at 12:37 AM, Thomas Goirand wrote:

> > Hi,

> >

> > When setting-up Designate with quorum queues, when designate-central

> > starts, I get:

> >

> > Queue.declare: (406) PRECONDITION_FAILED - invalid property

> > 'non-durable' for queue 'central' in vhost '/'

> >

> > Does Designate support quorum queues? If so, how com it's trying to set

> > 'non-durable', which doesn't exist as attribute, at least with RabbitMQ

> > 4.0.5?

>

> I don't have specific answers to your questions, but here are some thoughts on debugging this further. It would be helpful to know what version of designate and oslo.messaging you are running. Was there a traceback? The full content of that traceback is probably helpful to anyone debugging. Was there more logging context? If so that may be useful too. I suspect that your designate config (containing the oslo.messaging config options) is also useful information.

>

> Doing a quick dig around the code it seems that errors like this might occur if you have multiple connections with incompatible configs. I think oslo.messaging may fall back to non durable queues in some circumstances where this occurs. Maybe there was a missed configuration update to set quorum queues?

Looks like my config makes this happen in Nova and Neutron as well. I'll dig further...

Thomas