list-models sometimes errors after a migration (before model has been removed)

Bug #1666660 reported by Christopher Lee
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
High
Menno Finlay-Smits

Bug Description

After a migration the test runs 'list-models' a number of times to wait until the migrated model is removed from the model list of the source controller.

Sometimes this command can error with this message:

  09:44:52 ERROR cmd supercommand.go:458 cannot get model details: getting model 7f5f7a08-fadc-4546-86a7-4
8d494dfdb4d ("super-permissions") info: settings not found

This can happen for several seconds before the model is no longer listed (and that error is not displayed).

This can be confusing to a user because as far as they are concerned the model has been migrated away from this controller.

Revision history for this message
Menno Finlay-Smits (menno.smits) wrote :

This is likely to be because documents related to the document are in the process of being removed but the model document (the last thing to go) is still there. The API called by list-models is seeing the model document but then fails because it can't find out more.

Changed in juju:
assignee: nobody → Menno Smits (menno.smits)
milestone: none → 2.2.0
Revision history for this message
Anastasia (anastasia-macmood) wrote :

From IRC, Menno: model listing and lookup should avoid Dead models.

Changed in juju:
status: New → Triaged
Revision history for this message
Anastasia (anastasia-macmood) wrote :

@Chris,
I think that this is fixed by PR (against 2.1): https://github.com/juju/juju/pull/7033.
It has since been forward ported to 2.2.

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.