juju beta upgrade woes

[Rick Harding]

Daniel, sorry for the trouble there. As we work on things in the beta there
are times when the upgrade from one beta to another might cause issues like
this. You're hitting an incompatibility between the beta you were on and
the latest. The only fix is to tear down and redeploy with the latest beta.

As we get closer to feature complete and RC that will change and things
will stabilize and upgrades between releases will not have this side
drawback but we're not there yet.

Please beat on and abuse 2.0 betas as much as you can as it helps provide
great feedback from users that are getting into all the exciting
improvements to the Juju experience we've made. However, if it's something
that's mission critical please do use 1.25 until we can get to our RC
status on 2.0.

On Fri, Jul 15, 2016 at 1:00 PM Daniel Bidwell <drbidwell at gmail.com> wrote:

> using juju-2.0 beta 9 or 10 I bootstrapped a local/lxd instance and
> installed wordpress on it.  The containers are running.  Now juju has
> upgraded to 2.0 beta 11 and "juju status" returns:
>
> ERERROR connecting with bootstrap config: getting API info: model is
> not bootstrapped
>
> juju controllers returns:
>
> CONCONTROLLER  MODEL    USER         CLOUD/REGION
> local.wp*   default  admin at local
>
> Is there a way for me to "get it back" or do I just need to blow it
> away and start again?
>
> Should I be dropping back to juju 1.25.x for this?
>
> --
> Daniel Bidwell <drbidwell at gmail.com>
>
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20160715/04107665/attachment.html>