Public bug reported: Hi all,
Reported first for k8s: https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/480 Juju bug reported here: https://bugs.launchpad.net/juju/+bug/1746358 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. Cheers, - Calvin ** Affects: cloud-init Importance: Undecided Status: New ** Tags: cloud-init cpe-onsite dhcp juju k8s vsphere ** Tags added: cloud-init juju k8s kubernetes ** Tags removed: kubernetes ** Tags added: dhcp vsphere -- 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: New Bug description: Hi all, Reported first for k8s: https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/480 Juju bug reported here: https://bugs.launchpad.net/juju/+bug/1746358 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. Cheers, - Calvin To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1746455/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
