It seems that this issue affects only 1 controller node cases, which is not HA and it is not important which value for the rabbit_ha_queues will be configured for services.
I checked the 1 node deploy:
/etc/heat/heat.conf:rabbit_ha_queues=False
/etc/keystone/keystone.conf:rabbit_ha_queues=True
/etc/hiera/globals.yaml: rabbit_ha_queues: true
/etc/nova/nova.conf:rabbit_ha_queues=True
/etc/neutron/neutron.conf:rabbit_ha_queues=True
/etc/cinder/cinder.conf:rabbit_ha_queues=True
/etc/glance/glance-api.conf:rabbit_ha_queues=True
yes, for heat is seems inconsistent, but can be ignored for 1 controller node case, AFAIK.
It seems that this issue affects only 1 controller node cases, which is not HA and it is not important which value for the rabbit_ha_queues will be configured for services.
I checked the 1 node deploy: heat.conf: rabbit_ ha_queues= False keystone. conf:rabbit_ ha_queues= True globals. yaml: rabbit_ha_queues: true nova.conf: rabbit_ ha_queues= True neutron. conf:rabbit_ ha_queues= True cinder. conf:rabbit_ ha_queues= True glance- api.conf: rabbit_ ha_queues= True
/etc/heat/
/etc/keystone/
/etc/hiera/
/etc/nova/
/etc/neutron/
/etc/cinder/
/etc/glance/
yes, for heat is seems inconsistent, but can be ignored for 1 controller node case, AFAIK.