orchestra team mailing list archive
-
orchestra team
-
Mailing list archive
-
Message #00152
[Bug 846208] Re: Provisioned nodes do not get a FQDN
also i've been told this has been addressed in orchestra (hands out
fqdns now.)
** Changed in: juju
Milestone: None => eureka
** Changed in: juju
Status: New => Triaged
--
You received this bug notification because you are a member of
orchestra, which is subscribed to orchestra in Ubuntu.
https://bugs.launchpad.net/bugs/846208
Title:
Provisioned nodes do not get a FQDN
Status in juju:
Triaged
Status in “orchestra” package in Ubuntu:
New
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.canonical.com has address 10.55.55.6
ubuntu@soncoya:~$ host 10.55.55.6
6.55.55.10.in-addr.arpa domain name pointer soncoya.canonical.com.
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/846208/+subscriptions
References