when managing /etc/hosts, remove existing host entries
Bug #1853578 reported by
Radosław Piliszek
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kolla-ansible |
In Progress
|
Medium
|
Chason Chan | ||
Bug Description
When kolla-ansible is to manage /etc/hosts, it adds its entries but it does not ensure current ones are gone which leads to RabbitMQ issues.
Example /etc/hosts contents after run:
127.0.0.1 localhost
::1 localhost localhost.
172.16.34.10 cloudnode1
172.16.34.11 cloudnode2
172.16.34.12 cloudnode3
172.16.34.240 kolladeploy
# BEGIN ANSIBLE GENERATED HOSTS
172.16.35.10 cloudnode1
172.16.35.11 cloudnode2
172.16.35.12 cloudnode3
# END ANSIBLE GENERATED HOSTS
Revision history for this message
| Mark Goddard (mgoddard) wrote | #1 |
Revision history for this message
| Radosław Piliszek (yoctozepto) wrote | #2 |
Revision history for this message
| Mark Goddard (mgoddard) wrote | #3 |
| Changed in kolla-ansible: | |
| status: | New → Triaged |
Revision history for this message
| Chason Chan (chen-xing) wrote | #4 |
Revision history for this message
| Radosław Piliszek (yoctozepto) wrote | #5 |
Revision history for this message
| Chason Chan (chen-xing) wrote | #6 |
| Changed in kolla-ansible: | |
| assignee: | nobody → Chason Chan (chen-xing) |
Revision history for this message
| Mark Goddard (mgoddard) wrote | #7 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to kolla-ansible (master) | #8 |
| Changed in kolla-ansible: | |
| status: | Triaged → In Progress |
Revision history for this message
| Radosław Piliszek (yoctozepto) wrote | #9 |
Revision history for this message
| Radosław Piliszek (yoctozepto) wrote | #10 |
To post a comment you must log in.
FWIW, it should remove any IPs within the begin/end block.