Comment 14 for bug 1746455

Revision history for this message
Calvin Hartwell (calvinh) wrote : Re: [Bug 1746455] Re: cloud-init vSphere cloud provider DHCP unique hostname issue

Hi David,

I am on-site giving a workshop to a customer this week, but I will put this
into my schedule for next week or the week after when I have spare cycles.

It should be quite easy to replicate in our lab, I just need to setup the
DHCP server and install a test cluster with vSphere.

I'll message you on IRC when I start to work on this again.

Cheers,

- Calvin

On Wed, Feb 7, 2018 at 5:50 PM, David Britton <email address hidden>
wrote:

> On Tue, Feb 06, 2018 at 12:05:27AM -0000, Calvin Hartwell wrote:
> > No problem - if you need help reproducing the issue I am available mid
> > next week, I can reproduce this in the CPE lab if required.
>
> Hi Calvin -- if you have access to a vsphere that repeats this, by all
> means, I would love a reproduction environment.
>
> Currently my vsphere I have access to is blocked on a bootstrap error
> that I'm working with the juju team separately.
>
> --
> David Britton <email address hidden>
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1746455
>
> Title:
> cloud-init vSphere cloud provider DHCP unique hostname issue
>
> Status in cloud-init:
> In Progress
>
> 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
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: product=cloud-init; status=In Progress; importance=High;
> <email address hidden>;
> Launchpad-Bug-Tags: cdo-qa-blocker cloud-init cpe-onsite dhcp juju k8s
> vsphere
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: calvinh davidpbritton jameinel smoser thumper
> Launchpad-Bug-Reporter: Calvin Hartwell (calvinh)
> Launchpad-Bug-Modifier: David Britton (davidpbritton)
> Launchpad-Message-Rationale: Subscriber
> Launchpad-Message-For: calvinh
>

--
E: <email address hidden>
W: http://calvinhartwell.com
T: (+44) 07534801542