New compute node is not added to /etc/hosts on other nodes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
Undecided
|
Fuel Sustaining |
Bug Description
Detailed bug description:
A customer has added a new compute node to the environment. They noticed, that live-migration works FROM that compute node, but not TO it. The issue appeared to be connected to the new node not being in /etc/hosts of other nodes:
root@mosp-10133:~# grep mosp-10133 /etc/hosts
10.64.253.17 mosp-10133.
10.64.253.17 messaging-
root@mosp-10133:~# cat /etc/hosts
# HEADER: This file was autogenerated at 2017-02-10 10:28:45 +0000
root@mosp-10152:~# grep mosp-10133 /etc/hosts
root@mosp-10152:~#
root@mosp-
# HEADER: This file was autogenerated at 2017-01-30 09:52:06 +0000
However, according to the logs, the hostname was used in attempts to connect for migration:
<179>Feb 10 11:26:56 mosp-10152 nova-compute: 2017-02-10 11:26:56.674 15781 ERROR nova.virt.
Steps to reproduce:
Deploy an environment, add a new compute node, check /etc/hosts on nodes.
Expected results:
/etc/hosts should be updated and have the new hostname listed on all nodes as needed.
Actual result:
/etc/hosts is not updated.
Reproducibility:
-
Workaround:
Manually put the hostname to /etc/hosts on nodes.
Impact:
Live migration to the new compute node does not work.
Description of the environment:
Operation system: Ubuntu 14.04
Versions of components: MOS 9.1
Reference architecture: HA
Network model: Neutron with Provider Network
Related projects installed: -
Additional information:
-
Changed in fuel: | |
status: | New → Incomplete |
Changed in fuel: | |
status: | Incomplete → In Progress |
Changed in fuel: | |
status: | Incomplete → Confirmed |
assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
milestone: | none → 9.x-updates |
We need astute log from master and puppet log from previously deployed node to debug this.