yahoo-eng-team team mailing list archive

[Aman Kumar Sinha <1894839@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

I am using cloud-init v19.1 where I am passing config drive from nova
layer while VM deployment.

I am using set_hostname and update_hostname module under cloud_init_modules section in [1] file
As per the documentation I put preserve_hostname: true and rebooted the system and the hostname is preserve and not getting impacted even after multiple reboot.

When we using preserve_host: false and fqdn: <hostname> in [1]  . the
mentioned hostname get assigned as the hostname of the VM.

But when we just give preserve_hostname: false in [1], and deploy the
VM, the deployed VM name comes as a hostname.

[root@host cloudinit]# hostname
host

Expected:
Basically if we just give preserve_hostname: false it should set the hostname as per the dns what nslookup gives.


[1] /etc/cloud/cloud.cfg

** Affects: cloud-init
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1894839

Title:
  hostname not getting set as per the dns

Status in cloud-init:
  New

Bug description:
  I am using cloud-init v19.1 where I am passing config drive from nova
  layer while VM deployment.

  I am using set_hostname and update_hostname module under cloud_init_modules section in [1] file
  As per the documentation I put preserve_hostname: true and rebooted the system and the hostname is preserve and not getting impacted even after multiple reboot.

  When we using preserve_host: false and fqdn: <hostname> in [1]  . the
  mentioned hostname get assigned as the hostname of the VM.

  But when we just give preserve_hostname: false in [1], and deploy the
  VM, the deployed VM name comes as a hostname.

  [root@host cloudinit]# hostname
  host

  Expected:
  Basically if we just give preserve_hostname: false it should set the hostname as per the dns what nslookup gives.

  
  [1] /etc/cloud/cloud.cfg

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1894839/+subscriptions