Description

When we run juju upgrade-controller to a newer patch version (eg 4.0-beta3 to 4.0-beta9), we expect the version of the controller to be the updated one.juju status works fine and returns 4.0-beta9, but juju controllers and juju show-controller command still show the previous version at 4.0-beta3

Juju version

4.0beta9

Cloud

Kubernetes

Expected behaviour

We should expect to see the controller version to be updated after the controller upgrade.

Reproduce / Test

1. Change const version = "4.0-beta3" in core/version.go
2. Runmake minikube-operator-update && juju bootstrap minikube minikubetest
3. Change const version = "4.0-beta7" in core/version.go
4. Runmake minikube-operator-update
5. Runjuju upgrade-controller --agent-version 4.0-beta9
6. Runjuju status to confirm juju controller model version is upgraded to 4.0-beta9
7. Runjuju controllers andjuju show-controller minikubetest and observe that the controller version is 4.0-beta3

Notes & References

No response