So, queues are created by services themselves. In case services have failed or not running - this could be the result for absent queues. Another potential reason could be if you accidentally wiped mnesia db, which contains users and access controls. Or it could be an issue in oslo or smth like that, causing services not to reconnect on their own.
So I guess I would also tried to restart services and see if that will trigger queues creation or a failure on startup.

About ensuring presence of rabbitmq users and access rules, you should be able doing so through running

On Tue, 4 Feb 2025, 21:01 Danish Khan, <danish52.jmi@gmail.com> wrote:

Dear All,

I have upgraded one of my cluster from Victoria to wallaby. All playbooks run successfully and the cluster is upgraded to wallaby.

But I don't see any queue in rabbitmq "rabbitmqctl list_queues --vhost /cinder" and "rabbitmqctl list_queues --vhost /nova" returns empty results.

I tried adding these queues manually and the command is running successfully as well but still queues are not getting created.
#rabbitmqctl add_vhost /cinder
#rabbitmqctl set_permissions -p /cinder cinder ".*" ".*" ".*"

I have re-run all playbooks again but nothing is happening.

And I am getting below error in galera which I guess I can ignore for now:
error : Aborted connection 249 to db: 'cinder' user: 'cinder' host: 'infra1' (Got an error reading communication packets)

Regards,
Danish