yahoo-eng-team team mailing list archive

[Chad Smith <1746455@xxxxxxxxxxxxxxxxxx>]

This bug is believed to be fixed in cloud-init in 18.2. If this is still
a problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: cloud-init
       Status: Fix Committed => Fix Released

-- 
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/1746455

Title:
  cloud-init vSphere cloud provider DHCP unique hostname issue

Status in cloud-init:
  Fix Released

Bug description:
  We've had an issue recently when provisioning workloads on vSphere.
  Here is what happens:

  1) Set vSphere as the cloud provider in juju (bootstrap)

  2) Deploy workload on vSphere, in our case, Canonical Kubernetes (CDK)

  3) Machines are deployed using VMDK, but when they boot the initial
  hostname is Ubuntu (for all machines) until juju changes it during
  deployment.

  4) DHCP gives each machine a lease, but the DNS entries are all messed
  up because of identical hostnames.

  5) If the machines are rebooted they will receive the correct DNS
  entries. Note that juju will set the correct hostname eventually, but
  not when the initial DHCP lease is given to the host.

  
  Basically cloud-init is not giving newly provisioned machines on vSphere their correct hostname before the DHCP lease is given, meaning that every instance during DHCP has the hostname 'ubuntu' which messes up the entries on the DNS server.

  Related Bugs:

   * https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1600766
   * https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/480
   * https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/171

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