I am facing the exact same issue on CentOS 6.5 and RHEL 6.5 on AWS with cloud-init-7.4.2-2.el6.noarch from EPEL.
Before booting:
[root@testcase6 ~]# hostname testcase6 [root@testcase6 ~]# hostname -s testcase6 [root@testcase6 ~]# hostname -f testcase6.deltaforce.io
After booting:
[root@testcase6 ~]# hostname testcase6.deltaforce.io [root@testcase6 ~]# hostname -s testcase6 [root@testcase6 ~]# hostname -f testcase6.deltaforce.io
Note the difference in the first hostname commands.
I will try/merge the submitted patch and see if that works for me.
( IMO hostname consitency before/after booting is important. In my situation this generates issues with tools like puppet/mcollective/etc. )
I am facing the exact same issue on CentOS 6.5 and RHEL 6.5 on AWS with cloud-init- 7.4.2-2. el6.noarch from EPEL.
Before booting:
[root@testcase6 ~]# hostname deltaforce. io
testcase6
[root@testcase6 ~]# hostname -s
testcase6
[root@testcase6 ~]# hostname -f
testcase6.
After booting:
[root@testcase6 ~]# hostname deltaforce. io deltaforce. io
testcase6.
[root@testcase6 ~]# hostname -s
testcase6
[root@testcase6 ~]# hostname -f
testcase6.
Note the difference in the first hostname commands.
I will try/merge the submitted patch and see if that works for me.
( IMO hostname consitency before/after booting is important. In my situation this generates issues with tools like puppet/ mcollective/ etc. )