yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1894839@xxxxxxxxxxxxxxxxxx>]

[Expired for cloud-init because there has been no activity for 60 days.]

** Changed in: cloud-init
       Status: Incomplete => Expired

-- 
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:
  Expired

Bug description:
  Environment Details:
  Management Control Plane : OpenStack (Ussuri Release)
  cloud-init version : 19.1 (community)
  Data Source : Config Drive
  OS/platform of deployed VM : RHEL 8.2

  I am using cloud-init v19.1 where the control plane (OpenStack nova
  service) passes information (data source) via configdrive during VM
  deployment.

  I am using set_hostname and update_hostname module under
  cloud_init_modules section in [1] file. As per the documentation, I
  have put preserve_hostname: true  in the cfg file and rebooted the
  system(VM). The hostname is preserved and does not change after
  multiple reboot. This I believe is working as expected.

  When we using preserve_host: false and fqdn: <hostname> in [1], the
  hostname given as input value to fqdn is 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

  Expectation :

  If we give preserve_hostname: false it should set the hostname as per
  the dns what nslookup gives.

  If we use an image where preserve_hostname: false, with no hostname
  specified in the cfg file) and use set_hostname and update_hostname in
  [1] modules in the cfg file, and deploy few VMs (say 5 VMs ) with it -
  how will the hostname get configured to all the deployed VMs ? In this
  use case, we will want the hostname configured on the VM to DNS
  resolvable and aligned with the IP address associated with the VM. How
  can this be achieved ?

  [1] /etc/cloud/cloud.cfg

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