Closed domibay-hugo closed 5 years ago
I don't think this has anything to do with nova-agent. Look at your logged output.
Sep 23 09:42:18 agent02 systemd-hostnamed: Changed static host name to 'agent02.company.com.localdomain'
Sep 23 09:42:18 agent02 systemd-hostnamed: Changed static host name to agent02.company.com.localdomain'
Sep 23 09:42:18 agent02 NetworkManager[507]: [1569228138.4040] settings: hostname changed from "agent02.company.com" to "agent02.company.com.localdomain"
Sep 23 09:42:18 agent02 NetworkManager[507]: [1569228138.4040] settings: hostname changed from "agent02.company.com" to "agent02.company.com.localdomain"
Sep 23 09:42:18 agent02 systemd-hostnamed: Changed host name to 'agent02.company.com.localdomain'
Sep 23 09:42:18 agent02 systemd-hostnamed: Changed host name to 'agent02.company.com.localdomain'
systemd-hostnamed and NetworkManager seem to be involved. In the Rackspace CentOS 7 server image, systemd-hostnamed is disabled by default, and NetworkManager is disabled and masked to prevent it from running. If you need to run those for some reason, I suggest opening a ticket with Rackspace to look into this.
It turned out that the "cloud-init" scripts were overwriting the system configurations as documented at https://stackoverflow.com/questions/49249375/how-to-disable-cloud-init-networking the necessary configurations in /etc/cloud/cloud.cfg.d/10_rackspace.cfg were not included in the old version of it and this file is copied manually during the installation.
So I could fix this issue manually adding the correct configurations to this file.
I'm sorry for the inconvenience I caused you.
Always happy to help, glad you got it sorted out.
I found that our Server Centos7 that is running the Nova-Agent was unable to communicate:
After investigating this issue I found that the
hostname
was changed from the correct canonical Server Nameagent02.company.com
to the invalid broken Server Nameagent02.company.com.localdomain
by adding.localdomain
Extension to the valid Server Name on Server RebootThis is a worrying issue because it happened in Version 1.39.1 and continues in Version 2.1.20 and it leaves the Server Configuration corrupt and the Server unable to communicate.