unable to determine if a model is a controller model

[Jeff Pihach]

Because the controller model is "special" the GUI blocks certain actions in it, like the deletion action.

The issue is that we can no longer determine if a model is a controller model as the model-uuid and the controller-uuid no longer match and the name "controller" can be changed.

There doesn't appear to be any information in the ModelInfo call that can be used to determine if a model is a controller model. An 'is-controller' key would be ideal.

[Tim McNamara (tim-clicks)]

As a workaround, clients can call juju show-controller to figure this manually by inspecting the "models" section.

Here's an example:

$ juju show-controller

google-australia-southeast1:
  details:
    uuid: e7986e4d-a9af-411d-8f0f-21ae59dbe9f2
    controller-uuid: e7986e4d-a9af-411d-8f0f-21ae59dbe9f2
    [...]
  controller-machines:
    "0":
      instance-id: juju-dfc431-0
  models:
    controller:
      uuid: c8e4b143-72af-4e94-8b8c-20b12adfc431
      model-uuid: c8e4b143-72af-4e94-8b8c-20b12adfc431
      machine-count: 1
      core-count: 4
    default:
      uuid: c1e8063e-ca32-4a30-874c-d34e340cc6f4
      model-uuid: c1e8063e-ca32-4a30-874c-d34e340cc6f4
  current-model: admin/default
  account:
    user: admin
    access: superuser

Notice that within "models", the model model-uuid is provided. This could potentially be stored early and then compared against the current model that you're interested in.

[Jeff Pihach (hatch)]

Sorry I wasn't clear in the initial report but we need this exposed via the API for the GUI.

[Tim McNamara (tim-clicks)]

https://github.com/juju/juju/pull/9549

[Richard Harding (rharding)]

If the fix is committed we don't remove the milestone. It goes into the list of bugs addressed in that milestone. Was this landed against 2.5? If so it goes on the 2.5.0 milestone.

[Tim McNamara (tim-clicks)]

Thanks for the prod in the right direction Rick. Should be all cleared up now.