public-address and dns of nodes are IPs instead of hostnames
José Antonio Rey
jose at ubuntu.com
Thu Jun 30 04:24:02 UTC 2016
This was introduced a while ago, not sure if on 1.25.5, but it also
changed the behavior on AWS, where you used to get
ec2-ip-address-here.country.availabilityzone.amazonaws.com, and now you
get the public IP address. Someone else, maybe from the core team, may
be able to give you a little bit more background.
On 06/29/2016 11:19 PM, Junaid Ali wrote:
> Thanks Antonio for the quick response.
>
> If I connect one network to the node, it shows the hostname as
> public-address but if i connect a second network, it gets the IP from
> second network as public address (and dns). All of my nodes are
> connected to two networks except the juju bootstrap node. So from juju
> status command, DNS and public address of all nodes are IPs except the
> bootstrap node which has the hostname. This is a very random behavior.
> is the feature introduced in 1.25.5? and also can you please share why
> this feature is introduced?
>
> On Thu, Jun 30, 2016 at 9:11 AM, José Antonio Rey <jose at ubuntu.com
> <mailto:jose at ubuntu.com>> wrote:
>
> I believe this is not a bug, but a feature introduced a while ago.
>
>
> On 06/29/2016 11:09 PM, Junaid Ali wrote:
>
> Hi everyone,
> I'm hitting an issue on one of my deployments. $ juju stat shows
> IP of a
> node as its public-address and dns that instead should have the
> hostname.
>
> I'm using juju version 1.25.5 and MAAS version 1.9.3
> If i run
> $ maas <maas cli profile> nodes list
> it outputs the correct hostnames so I'm guessing there's
> something wrong
> on juju side. Also if i ssh into a node and check the hostname, the
> node has the correct hostname.
>
> Here is the output of
> $ juju stat --format tabular
> http://paste.ubuntu.com/18145396/
>
> Can you anyone please help me in debugging this issue?
>
> Thanks,
> - Junaid
>
>
>
>
>
> --
> José Antonio Rey
>
>
--
José Antonio Rey
More information about the Juju
mailing list