VSphere provider not properly setting unit hostname
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Andrew Wilkins |
Bug Description
When deploying to a vsphere provider we have here on premise it appears that every ubuntu guest VM provisioned by juju gets the hostname "ubuntuguest". This is problematic in deployments that require FQDN to be resolveable.
Even if the units have a DNS entry, the dns server is likely to round robin distribute them, possibly connecting units to the wrong endpoint. For example, kubernetes uses the FQDN hostname to contact for operations like kubectl exec and kubectl logs (both of which are mandatory in conformance testing).
This seems reproduceable enough that we've identified failure modes for our conformance testing, and its indicative that something between juju and vsphere aren't setting things up properly. It would be great if cloud-init could assign the VM the name of the VM itself.
Version:
2.1.1-xenial-amd64
This is with vsphere 6.0:
VMware vCenter Server 6.0.0, 3634794
VMware ESXi 6.0.0, 3620759
tags: | added: oil |
description: | updated |
tags: | added: oil-2.0 vsphere |
tags: | added: cdo-qa-blocker |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Critical |
milestone: | none → 2.2-beta1 |
tags: | added: sprint |
tags: |
added: kubernetes removed: sprint |
Changed in juju: | |
importance: | Critical → High |
assignee: | nobody → Horacio Durán (hduran-8) |
Changed in juju: | |
milestone: | 2.2-alpha1 → 2.2-beta1 |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
assignee: | Horacio Durán (hduran-8) → Andrew Wilkins (axwalk) |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
I was made aware this morning of a NSS plugin for juju that could potentially resolve this behavior.
https:/ /bugs.launchpad .net/juju/ +bug/1590961