Use correct group name for MQ tasks

There is no 'nova-api' group, and the tasks should run
when targeting the conductor nodes anyway.
Change-Id: I998fb74a800237d1c4fa535b4871d897c30c7c7d
This commit is contained in:
Jesse Pretorius
2018年07月24日 19:03:56 +01:00
parent ff469e2e02
commit 7e588c057e

View File

@@ -101,8 +101,8 @@
- include_tasks:mq_setup.yml
when:
- "nova_services['nova-api']['group'] in group_names"
- "inventory_hostname == ((groups[nova_services['nova-api']['group']]| intersect(ansible_play_hosts)) | list)[0]"
- "nova_services['nova-conductor']['group'] in group_names"
- "inventory_hostname == ((groups[nova_services['nova-conductor']['group']]| intersect(ansible_play_hosts)) | list)[0]"
with_items:
- oslomsg_setup_host:"{{ nova_oslomsg_rpc_setup_host }}"
oslomsg_userid:"{{ nova_oslomsg_rpc_userid }}"
Reference in New Issue
openstack/openstack-ansible-os_nova
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.

The note is not visible to the blocked user.