-
Mark Goddard authored
This bug was previously fixed but the fix did not cover all cases. This issue is still present if an IP address other than 127.0.0.1 or the admin IP address (but not the internal API IP address, which is correct) is in /etc/hosts. For example, in CI we often see 127.0.1.1. This change removes all entries from /etc/hosts for the host's current hostname, other than the internal API IP address. It also adds a call to rabbitmqctl status to verify that the change has worked. Related: We ought to improve the kolla ansible prechecks to catch the case when there is more than one IP address mapping for the host's current hostname. Change-Id: I2cb9928e04005c6961f3de7c571c9a06361c4f23 Story: 2003496 Task: 24773
Mark Goddard authoredThis bug was previously fixed but the fix did not cover all cases. This issue is still present if an IP address other than 127.0.0.1 or the admin IP address (but not the internal API IP address, which is correct) is in /etc/hosts. For example, in CI we often see 127.0.1.1. This change removes all entries from /etc/hosts for the host's current hostname, other than the internal API IP address. It also adds a call to rabbitmqctl status to verify that the change has worked. Related: We ought to improve the kolla ansible prechecks to catch the case when there is more than one IP address mapping for the host's current hostname. Change-Id: I2cb9928e04005c6961f3de7c571c9a06361c4f23 Story: 2003496 Task: 24773
templates NaN GiB