Re: More juju upgrade-juju failings

I think this UX on the upgrade process has obvious problems. Nobody should have to guess at what to do, in which sequence. Can I suggest that we have a shared Google doc to mock up a nice experience starting with the simple command 'juju upgrade' which then walks people through the process,

Juju 2.3.4 has been released

Juju 2.3.4 has arrived. This is primarily a bug fix release. ## Critical bugs fixed. Among the bugs fixed, one was considered critical. * 1748275 Juju HA fails due to demotion of Machine 0 If you were affected by any of the bugs fixed in

Re: More juju upgrade-juju failings

Hi Daniel, The issue here is that you are upgrading the default model, not the controller model itself. I think we could make the error messaging more clear, and also have the command also check the controller version before showing a lot of baffling output. What you need to do is upgrade the

More juju upgrade-juju failings

I am running on juju 2.3.3-xenial-amd64 and my controllers are running in VMware Vsphere with version 2.3.2.  I thought that it would be a good thing for me to upgrade the controllers. I have a controller, "juju switch" generates: bannercontroller:admin/default and juju status generates: Model