Juju 2.0-rc3 is here!

Matt Rae matt.rae at canonical.com
Fri Oct 7 22:19:36 UTC 2016


Thanks Curtis! following your steps and setting the agent-stream=devel, I
was able to upgrade the controller and default models to rc3

Matt

On Fri, Oct 7, 2016 at 1:59 PM, Curtis Hovey-Canonical <curtis at canonical.com
> wrote:

> Hi Matt,
>
> You, and several of us, are victims of '"upload-tools strikes back"
> cannot upgrade with streams'
> https://bugs.launchpad.net/juju/+bug/1631529
>
> On Fri, Oct 7, 2016 at 1:51 PM, Matt Rae <matt.rae at canonical.com> wrote:
> > Hi, I'm testing an upgrade between juju 2.0 rc2 and rc3.
> >
> > Should 'juju upgrade-juju -m default' upgrade to rc3?
> >
> > So far I'm seeing 'no upgrades available'
> >
> > $ juju model-config agent-version
> > 2.0-rc2
> > $ juju --version
> > 2.0-rc3-xenial-amd64
> > $ juju upgrade-juju
> > no upgrades available
> > $ juju upgrade-juju --agent-version 2.0-rc3
> > ERROR no matching tools available
>
> Do you see this:
> $ juju model-config -m controller agent-stream
> released
>
> ^ No, the juju client selected devel streams without telling the controller
>
> WORK AROUND
>
> Tell the juju controller to use devel streams. Eg, to upgrade my own
> deployment, I I set the streams to devel, then upgrade the controller
> than the hosted model.
>
> $ juju model-config -m controller agent-stream=devel
> $ juju upgrade-juju -m controller
> started upgrade to 2.0-rc3
> $ juju upgrade-juju -m default
> started upgrade to 2.0-rc3
>
> When 2.0.0 is released, switch the streams to released.
> $ juju model-config -m controller agent-stream=released
>
> Then upgrade as normal.
>
> --
> Curtis Hovey
> Canonical Cloud Development and Operations
> http://launchpad.net/~sinzui
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20161007/21ef9cc8/attachment.html>


More information about the Juju mailing list