Provisioned nodes do not get a FQDN
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pyjuju |
Fix Released
|
Undecided
|
Unassigned | ||
| orchestra (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
When using the Orchestra Ensemble machine provider, deployed nodes do not get their full FQDN, which creates lots of issues for formula relations that depend on resolvable hostnames being exported in either direction.
ubuntu@soncoya:~$ host 10.55.55.6
soncoya.
ubuntu@soncoya:~$ host 10.55.55.6
6.55.55.
ubuntu@soncoya:~$ hostname -f
soncoya.localdomain
I think we either need to make sure DHCP server on the Orchestra server is giving out both hostname and domain correctly (and ensure clients are configured to use it), or handle hostnames via cloud-config to reflect whats been configured in cobbler/dns. The latter is likely only necessary for the Orchestra provider.
| Kapil Thangavelu (hazmat) wrote | #1 |
| Kapil Thangavelu (hazmat) wrote | #2 |
| Changed in juju: | |
| milestone: | none → eureka |
| status: | New → Triaged |
| Andres Rodriguez (andreserl) wrote | #3 |
| Changed in orchestra (Ubuntu): | |
| status: | New → Fix Released |
| Changed in juju: | |
| status: | Triaged → Fix Released |
while this is true, units should be using the unit-get public-address or unit-get private-address as a provider independent mechanism for resolving their address.