Detailed bug description:
Unpredictable order of entries in /etc/hosts. Entries, added by hosts/hosts.pp come in a different (from deployment to deployment) order, normal hostnames and hostname with a prefix for the same IP is messed up:
172.16.6.8 node-4.test.domain.local node-4
172.16.6.9 node-2.test.domain.local node-2
172.16.6.12 messaging-node-5.test.domain.local messaging-node-5
172.16.6.7 node-3.test.domain.local node-3
172.16.6.10 node-6.test.domain.local node-6
172.16.6.7 messaging-node-3.test.domain.local messaging-node-3
172.16.6.6 messaging-node-7.test.domain.local messaging-node-7
172.16.6.5 messaging-node-1.test.domain.local messaging-node-1
172.16.6.10 messaging-node-6.test.domain.local messaging-node-6
172.16.6.9 messaging-node-2.test.domain.local messaging-node-2
172.16.6.5 node-1.test.domain.local node-1
172.16.6.11 node-9.test.domain.local node-9
172.16.6.8 messaging-node-4.test.domain.local messaging-node-4
172.16.6.6 node-7.test.domain.local node-7
172.16.6.12 node-5.test.domain.local node-5
172.16.6.11 messaging-node-9.test.domain.local messaging-node-9
For the IP 172.16.6.8 the hostname 'node-4.test.domain.local' will be the answer while the IP 172.16.6.12 dnsmasq will resolve as 'messaging-node-5.test.domain.local', hostname with a prefix.
The issue was brought with fixing bug #1535383
Steps to reproduce:
Complete a deployment
Expected results:
Hostname come in some order, for example:
1) Existing entries,
2) Hostnames with a prefix
3) Hostname without a prefix.
Or vise versa, 1), then 3), then 2)
Actual result:
We have a mess described above.
Reproducibility:
100%
Workaround:
Unknown
Description of the environment:
Operation system: Ubuntu 14.04
Versions of components: Fuel 9.0
Fix proposed to branch: master
Review: https:/