Failed to upgrade Juju controller

[Sophie Pagès]

Hi,

While following the tutorial https://juju.is/docs/juju/tutorial, I encountered this error:

ubuntu@my-juju-vm:~$ juju upgrade-controller
ERROR cannot get architecture for jujud-operator:3.1.0: can not get manifests for jujud-operator:3.1.0: manifest response version "application/vnd.oci.image.index.v1+json" not supported (not supported)

My controller version was 3.1.8, and juju cli version 3.4.2 (rev 26968). It was on a cloud microk8s.

Running "juju upgrade-controller --agent-version 3.1.8" didn't return an error.

Thank you

[Andrei Polukhin (andrew-polukhin)]

Hello,

This bug also affects me when following the official Juju tutorial (https://juju.is/docs/juju/tutorial), the "Upgrade" part. I would appreciate it if you took a look.

Thanks,
Andrei

[Andrei Polukhin (andrew-polukhin)]

Addition to the comment above: the Juju version is 3.5.0 now on my machine, but the cloud is MicroK8S.

[Ian Booth (wallyworld)]

It is recommended that you use a more recent version of Juju to bootstrap your controller. Looking at the tutorial, doesn't seem to say directly you should use Juju 3.1 but I can see how it might be implied since the example output shows 3.1.8. Juju 3.1 is in maintenance mode only and is almost at EOL. I am not sure off hand why it's complaining about an oci image tagged 3.1.0 if the controller version is 3.1.8.

Unfortunately, Juju 3.5.0 has a bug which results in some k8s charms breaking. A fix is coming, but for now I would try the tutorial with Juju 3.4 - snap install from the 3.4 track and bootstrap.

[Teodora Mihoc (tmihoc)]

Looking at the tutorial:

```
ubuntu@my-juju-vm:~$ juju upgrade-controller
ubuntu@my-juju-vm:~$ juju upgrade-controller --agent-version 3.1.8
# No change because 3.1.8 is already the latest patch version of 3.1:
no upgrades available
```

I think the first line there is by mistake (the intention there is to upgrade to 3.1.8). I'll remove it. Still, I've seen that error message too and it's interesting. Based on the command help, my expectation would be that not using any flag should simply default to something. My guess is there is currently no default, probably because we want the users to be deliberate about what they want to upgrade to. The command help + the error message should still be updated.

[John A Meinel (jameinel)]

`juju upgrade-controller` should definitely report something, but should be reporting that it is checking for what versions are available, and then likely reporting "you're already up-to-date" (if you just did a bootstrap, then you're unlikely to be running anything but the latest version, and thus not have anything to upgrade to).

If you aren't seeing that, then I'd consider it a bug.

[Launchpad Janitor (janitor)]

[Expired for Canonical Juju because there has been no activity for 60 days.]