Multiple commands depend on constant controller model name

[Harry Pidcock]

Multiple commands in juju depend on `bootstrap.ControllerModelName` for finding the controller model.

Not an exhaustive list:
- restore-backup
- upgrade-controller
- list-controllers
- show-controller

These commands should find the controller model without the default controller model name.

[Anastasia (anastasia-macmood)]

When a controller model name is called something other than 'controller', a few things can go wrong. We need to explore that and ensure that Juju works irrespective of what the controller model name is.

At the movement, it is not straightforward for users to change the 'controller' model name, so the risks associated with this report are fairly low. Triaging as a 'Medium' usability bug.

[John A Meinel (jameinel)]

I agree that commands that depend on the controller name shouldn't need to be passed the controller model. I don't think we have an intent to allow renaming the controller model at this time (either during bootstrap or at any other time). Having it be a field on the model definition might be an option (for things like 'list-controllers').

I'm not aware of any specific user feedback that says "I can't name my own model controller", so I don't think there is social pressure to update this. I can understand a desire to avoid a constant in our code that doesn't seem like it fits, but I would avoid going to great lengths for something that ends up YAGNI.

[Canonical Juju QA Bot (juju-qa-bot)]

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.