juju model migration resets 'Inst id' display in juju status output

Bug #1954969 reported by Xav Paice
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Committed
Low
Caner Derici

Bug Description

Juju 2.9.22, migrating from a controller running Xenial to one running Focal, both provided by Maas.

On the original model when I run 'juju status' I get the display name of machines in the Inst id column, e.g.

Model Controller Cloud/Region Version SLA Timestamp
bootstack-preparation controller-xenial maas 2.9.22 unsupported 18:42:41Z

App Version Status Scale Charm Store Channel Rev OS Message
nagios unknown 1 nagios charmstore stable 46 ubuntu Waiting for agent initialization to finish
thruk-agent unknown 1 thruk-agent charmstore stable 13 ubuntu Waiting for agent initialization to finish

Unit Workload Agent Machine Public address Ports Message
nagios/2* active idle 43 10.36.2.3 80/tcp ready
  thruk-agent/3* active idle 10.36.2.3 ready

Machine State DNS Inst id Series AZ Message
43 started 10.36.2.3 nagios bionic default Deployed

After the upgrade, the "Inst id" column displays the Maas machine ID.

If I run 'juju show-machine 43' it shows me `hostname: nagios`, `instance-id: xn3qm4`, `dns-name: 10.36.2.3`, but previously there was also a `display-name: nagios` field which seems to have disappeared on migration.

Is there any way to get these back?

Xav Paice (xavpaice)
description: updated
Revision history for this message
Heather Lanigan (hmlanigan) wrote :

Doubled checked the migration export and import code, the DisplayName is not included in the description package, nor part of newCloudInstanceArgs. Migration needs to be updated.

Changed in juju:
status: New → Triaged
importance: Undecided → Medium
tags: added: model-migration
Caner Derici (cderici)
Changed in juju:
assignee: nobody → Caner Derici (cderici)
Caner Derici (cderici)
Changed in juju:
status: Triaged → Fix Committed
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: Medium → Low
tags: added: expirebugs-bot
Revision history for this message
German Mazurenko (german-m) wrote (last edit ):

Faced same problem after migration from 2.8.6 to 2.9.45. And only on our main cluster. I've done 4 migrations before and they were all ok. Except for last one. All new machines(created after migration) in this model have "normal" name, but old ones use maas system_id (instead of hostname) as inst id.

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.