Comment 8 for bug 1737058

2.3.2 will fix this so that upgrading 2.2.X => 2.3.2 in the controller
won't break the existing 2.2 models. But yes, the current workaround is to
upgrade all models to 2.3.1. 2.3.2 should be out this week.

On Tue, Jan 16, 2018 at 2:30 PM, Mario Splivalo <
<email address hidden>> wrote:

> I hit the same issue upgrading my environment from 2.2.5 to 2.3.1.
> I have two models, one with openstack on trusty and one with openstack on
> xenial.
> Upgrading the controller model to 2.3.1 rendered all of the units on
> trusty model to be in error state (xenial model was fine).
> Upgrading both models to 2.3.1 resolved all of the issues (xenial was fine
> before, but trusty one got fixed too).
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1737058
>
> Title:
> network-get fails to find configs on 2.3.0 that worked on 2.2.6
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1737058/+subscriptions
>