Properly detect the master node when running on AWS EC2

alexey-medvedchikov · Dec 8, 2016 · 5f08fbc · 5f08fbc
1 parent 3e3531c
commit 5f08fbc
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/tasks/main.yml b/tasks/main.yml
@@ -15,9 +15,9 @@
 - include: service.yml
 
 - include: cluster.yml
-  when: 'rabbitmq_create_cluster and (ansible_hostname != rabbitmq_cluster_master) and (ansible_fqdn != rabbitmq_cluster_master)'
+  when: 'rabbitmq_create_cluster and (ansible_hostname != rabbitmq_cluster_master) and (ansible_fqdn != rabbitmq_cluster_master) and ((ec2_public_dns_name | default('')) != rabbitmq_cluster_master)'
 
 - include: rabbitmq.yml
-  when: 'not rabbitmq_create_cluster or (ansible_hostname == rabbitmq_cluster_master) or (ansible_fqdn != rabbitmq_cluster_master)'
+  when: 'not rabbitmq_create_cluster or (ansible_hostname == rabbitmq_cluster_master) or (ansible_fqdn == rabbitmq_cluster_master) or ((ec2_public_dns_name | default('')) == rabbitmq_cluster_master)'
 
 - meta: flush_handlers