Open Stack

Hey,

I did exactly the same on my side.
I also have unroutable messages going in my alternate exchange, related
to the same exchanges (q-agent-notifier-security_group-update_fanout,
etc.)

Did you figured out why you have unroutable messages like this?
Are you using a custom neutron driver?

Cheers,

-- 
Arnaud Morin

On 21.08.20 - 10:32, Fabian Zimmermann wrote:
> Hi,
> 
> im currently on the way to analyse some rabbitmq-issues.
> 
> atm im taking a look on "unroutable messages", so I
> 
> * created an Alternative Exchange and Queue: "unroutable"
> * created a policy to send all unroutable msgs to this exchange/queue.
> * wrote a script to show me the msgs placed here.. currently I get
> 
> Seems like my neutron is placing msgs in these exchanges, but there is
> nobody listening/binding to:
> --
>      20 Exchange: q-agent-notifier-network-delete_fanout, RoutingKey:
>     226 Exchange: q-agent-notifier-port-delete_fanout, RoutingKey:
>      88 Exchange: q-agent-notifier-port-update_fanout, RoutingKey:
>     388 Exchange: q-agent-notifier-security_group-update_fanout, RoutingKey:
> --
> 
> Is someone able to give me a hint where to look at / how to debug this?
> 
>  Fabian
>