Juju upgrade-juju upgrades to a beta release on k8s controllers

[Barry Price]

Running the Juju latest/stable snap (i.e. 2.7.3) on 20.04/amd64

In a local microk8s controller setup, my agents were on 2.7.2

I ran 'juju upgrade-juju -m controller', expecting to get 2.7.3

$ juju upgrade-juju -m controller
best version: 2.8-beta1.3273
started upgrade to 2.8-beta1.3273
$

I'd have expected to be prompted before being upgraded to a beta release.

It also seems like I can't deploy or remove applications under 2.8-beta1.3273, even with --force, but that's one for a separate bug.

[Barry Price (barryprice)]

Oh, and I also can't upgrade existing models once the controller has been upgraded to a beta:

$ juju upgrade-juju
best version:
    2.8-beta1.3284
ERROR model cannot be upgraded to 2.8-beta1.3284 while the controller is 2.8-beta1: upgrade 'controller' model first
$

But if there's anything deployed in the model, LP:1865439 means that I can't destroy it either, without nuking the whole controller (or at least, I haven't yet found a way to do so).

[Ian Booth (wallyworld)]

Initial issue is fix committed (selection of beta version by default).
We need a new bug for the other issue. Reported as bug 1867224

[Barry Price (barryprice)]

Thanks Ian, and apologies - I should have submitted that as a separate bug in the first place.