Critical regression on vsphere due to cloud-init

[David Britton]

Hi Merlijn --

We are working on that bug actively.  At its core, this is a mismatch
between how a cloud functions (dhcp/dns is set up in advance and not
mutable by the instance), and how vsphere operates.

If you could put into the bug the reproduction steps you have taken, that
would be very much appreciated.  Especially needed are:

1) vsphere version
2) What dhcp server are you running and how is it configured?
3) How do you deploy CDK and where does the problem trigger?



On Tue, Feb 20, 2018 at 2:53 AM, Merlijn Sebrechts <
merlijn.sebrechts at gmail.com> wrote:

> Hi all
>
>
> I want to bring a critical regression on vsphere to your attention. DNS on
> vsphere recently got broken, probably due to a regression in cloud-init.
> Link to the bug report below. Because of this, we're unable to deploy many
> bundles such as the big data bundles and the Kubernetes bundles.
>
> Is somebody working on a fix? The CDK issue mentions a workaround; does
> anybode know what that workaround is?
>
> - Bug in cloud-init: https://bugs.launchpad.net/cloud-init/+bug/1746455
> - Bug in CDK: https://github.com/juju-solutions/bundle-canonical-
> kubernetes/issues/480
> - Someone on askubuntu having the same issue: https://askubuntu.com/
> questions/994629/dhcp-lease-always-registered-with-
> default-ubuntu-instead-of-actual-hostname-at
>
>
>
> Regards
> Merlijn
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju-dev
>
>


-- 
David Britton <david.britton at canonical.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20180220/49248e4a/attachment.html>