DNS column in juju status has an IP address

Bug #1566014 reported by Casey Marshall
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
High
Richard Harding

Bug Description

The [Machines] section shows IP addresses in the DNS column:

[Machines]
ID STATE DNS INS-ID SERIES AZ
0 started 10.0.3.153 juju-1e7704dd-ddd5-4197-8bd5-9c9c7585a21d-machine-0 trusty
1 started 10.0.3.40 juju-1e7704dd-ddd5-4197-8bd5-9c9c7585a21d-machine-1 trusty
2 started 10.0.3.239 juju-1e7704dd-ddd5-4197-8bd5-9c9c7585a21d-machine-2 trusty
3 started 10.0.3.142 juju-1e7704dd-ddd5-4197-8bd5-9c9c7585a21d-machine-3 trusty
4 started 10.0.3.149 juju-1e7704dd-ddd5-4197-8bd5-9c9c7585a21d-machine-4 trusty
5 started 10.0.3.20 juju-1e7704dd-ddd5-4197-8bd5-9c9c7585a21d-machine-5 trusty

Maybe it should be ADDRESS instead?

Changed in juju-core:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Yeah, compare juju1 with juju2 (different machines, but same maas controller):

juju1:
[Machines]
ID STATE VERSION DNS INS-ID SERIES HARDWARE
0 started 1.25.5 omaha.scapestack /MAAS/api/1.0/nodes/node-2fdcca2c-39eb-11e5-ab72-2c59e54ace74/ trusty arch=amd64 cpu-cores=4 mem=16384M availability-zone=dawn

juju2 beta6:
[Machines]
ID STATE DNS INS-ID SERIES AZ
0 started 10.96.10.1 /MAAS/api/1.0/nodes/node-54a9d17c-f77f-11e5-ad3e-2c59e54ace75/ xenial dawn

That IP is resolvable:
$ dig +short @10.96.0.10 -x 10.96.10.1
elkhart.scapestack.

$ dig +short @10.96.0.10 elkhart.scapestack
10.96.10.1

tags: added: juju-release-support status
tags: added: usability
Revision history for this message
Junaid Ali (junaidali) wrote :

Hi Cheryl, I'm facing the same issue. Juju version that I'm using is 1.25.5

here is the output of $ juju stat --format tabular
http://paste.ubuntu.com/17701137/

attached are logs after setting the logging-config to debug "`juju set-env logging-config="<root>=DEBUG"`"

Changed in juju-core:
status: Triaged → New
Revision history for this message
James Tunnicliffe (dooferlad) wrote :

Verified with Juju 2.0 against MAAS 1.9.

Changed in juju-core:
status: New → Triaged
Changed in juju-core:
milestone: none → 2.0.0
importance: Medium → High
affects: juju-core → juju
Changed in juju:
milestone: 2.0.0 → none
milestone: none → 2.0.0
Changed in juju:
assignee: nobody → Richard Harding (rharding)
Changed in juju:
milestone: 2.0.0 → 2.1.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.