juju machines no longer outputs maas machine id

[Andrew McLeod]

juju 2.5.3 now lists the display name, aka hostname for a maas node in juju status output / juju machines output. This is easier to read and understand, but since the maas API doesn't allow lookups via host name and requires the maas system id, this means extra steps to get the id from the hostname to perform actions against the maas API.

[Ian Booth (wallyworld)]

The instance id is supposed to still be in status via the --format yaml (or json) option.
The machine name replaces instance id in tabular output (which is for humans). However, it appears the yaml/json output is missing the instance id so this will need to be addressed.

[Ian Booth (wallyworld)]

Actually, I just tested on a MAAS setup and the instance id is being shown, eg

machines:
  "0":
    dns-name: 10.0.0.32
    ip-addresses:
    - 10.0.0.32
    instance-id: pybf87

Which allows you to navigate to:

http://<maasip>/MAAS/#/machine/pybf87

What's missing in this deployment is the display name, which isn't always available depending on what the maas reports.

Do you have a sample status --format yaml output we can look at to confirm there really is an issue?

[Ian Booth (wallyworld)]

I just did another test with MAAS where the machine I was deploying to did report a hostname. Both instance id and hostname (aka display name) did show as expected in status --format yaml

machines:
  "0":
    dns-name: 10.0.0.32
    ip-addresses:
    - 10.0.0.32
    instance-id: s88gww
    display-name: nuc5

tabular status shows hostname as expected.

Marking the bug as invalid on that basis.

Note that the reason this change was made was to fix this bug https://bugs.launchpad.net/bugs/1501475