We use Mirantis OpenStack with the upstream puppet manifests for Heat deployment and we can see that in HA deployments we have the following parameter in Heat configuration file:
rabbit_ha_queues=False
In the result, if we will shutdown primary controller Heat will lost some queues and will doesn't work, we need to restart all Heat services to fix the issue. We investigated the issue and looks like all other services have correct configuration with
rabbit_ha_queues=True, but heat has rabbit_ha_queues=False.
We tested Heat with rabbit_ha_queues=True, which we applied manually, it works well.
We compared puppet manifests for Keystone and Heat and found the differences:
We use Mirantis OpenStack with the upstream puppet manifests for Heat deployment and we can see that in HA deployments we have the following parameter in Heat configuration file:
rabbit_ ha_queues= False
In the result, if we will shutdown primary controller Heat will lost some queues and will doesn't work, we need to restart all Heat services to fix the issue. We investigated the issue and looks like all other services have correct configuration with ha_queues= True, but heat has rabbit_ ha_queues= False.
rabbit_
We tested Heat with rabbit_ ha_queues= True, which we applied manually, it works well.
We compared puppet manifests for Keystone and Heat and found the differences:
Keystone: /github. com/openstack/ puppet- keystone/ blob/bca04a399e 6de63bd6d3d3d98 5aeaf3134802ac1 /manifests/ init.pp# L764-772
https:/
Heat: /github. com/openstack/ puppet- keystone/ blob/bca04a399e 6de63bd6d3d3d98 5aeaf3134802ac1 /manifests/ init.pp# L764-772
https:/