Juju status output includes a field 'dns-name' or DNS, but doesn't resolve that to a name

Bug #1798709 reported by Xav Paice
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

When using Juju with Maas, the instance-id is an unintelligible string which is not really something folks use as a hostname. When working with hardware issues, we need to determine what applications run on which host, and to do so we have to either get the hostname from maas by feeding it the inst id, or by running 'hostname' on the machine.

The content of 'dns-name' is the IP address of the machine, rather than a name, even if reverse lookup works perfectly.

It would be extremely helpful for operators if the hostname of the machine were displayed in the output of 'juju status', either in the yaml/json output or preferably in the tabular output too.

Changed in juju:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.5.1
Ian Booth (wallyworld)
Changed in juju:
milestone: 2.5.1 → 2.5.2
Changed in juju:
milestone: 2.5.2 → 2.5.3
Changed in juju:
milestone: 2.5.3 → 2.5.4
Changed in juju:
milestone: 2.5.4 → 2.5.5
Changed in juju:
milestone: 2.5.6 → 2.5.8
Changed in juju:
milestone: 2.5.8 → 2.5.9
Revision history for this message
Anastasia (anastasia-macmood) wrote :

Removing from a milestone as this work will not be done in 2.5 series.

Changed in juju:
milestone: 2.5.9 → none
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: High → Low
tags: added: expirebugs-bot
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.