Fix rabbitmq restart on non-rabbitmq accessible nodes
During the upgrade playbook, rabbitmq is restarted. The deploy
node will try to contact rabbitmq directly, based on its
inventory hostname. If the inventory hostname is unknown to the
deployment node, the playbook will fail.
The rabbitmq playbook now delegates the rabbitmq check to the
physical host having the rabbitmq node, on the IP used for
SSH'ing, instead of the hostname.
Reviewed: https:/ /review. openstack. org/333813 /git.openstack. org/cgit/ openstack/ openstack- ansible/ commit/ ?id=fd272928c57 c8b2dcb73148997 e848a1bfe4e23e
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit fd272928c57c8b2 dcb73148997e848 a1bfe4e23e
Author: Jean-Philippe Evrard <email address hidden>
Date: Fri Jun 24 08:32:38 2016 +0000
Fix rabbitmq restart on non-rabbitmq accessible nodes
During the upgrade playbook, rabbitmq is restarted. The deploy
node will try to contact rabbitmq directly, based on its
inventory hostname. If the inventory hostname is unknown to the
deployment node, the playbook will fail.
The rabbitmq playbook now delegates the rabbitmq check to the
physical host having the rabbitmq node, on the IP used for
SSH'ing, instead of the hostname.
Closes-Bug: 1586148 4142d2a0a5de69d 5ee3d333875
Change-Id: I6b267a1fca8e89