Manual juju upgrade

John Meinel john at arbash-meinel.com
Mon Aug 4 12:17:12 UTC 2014


There are ways to do an upgrade manually if you take a lot of care.
However, I think if you did "juju upgrade-juju --version=1.18.4" you'll
provide yourself more of the sanity and safety around the upgrade than
trying to reproduce all of the steps that we recorded inside of juju.

If you really want to work it out for yourself:
https://github.com/juju/juju/blob/master/upgrades/steps118.go
Is the list of steps that need to be done to upgrade something from 1.16 to
1.18, and AFAIK there aren't any explicit steps for upgrading from 1.18 =>
1.20.

As far as "stable only upgrades with 1 hop" that is only true up to 1.18.
>From 1.18 onward the new client should remain compatible with 1.18 for the
foreseeable future. (So 1.20, 1.21, 1.22, etc should all continue to work
with a 1.18 server.)

John
=:->




On Mon, Aug 4, 2014 at 4:01 PM, Curtis Hovey-Canonical <curtis at canonical.com
> wrote:

> On Mon, Aug 4, 2014 at 8:00 AM, Curtis Hovey-Canonical
> <curtis at canonical.com> wrote:
> > On Mon, Aug 4, 2014 at 6:36 AM, Henning Eggers <henning at keeeb.com>
> wrote:
> >> Hi,
> >>
> >> I have a couple of machines running an older juju version (1.16.6 on
> precise)
> >> and I cannot manage them through my current workstation installation
> (1.20.1
> >> on trusty). I get errors like "no such request "FullStatus" on Client"
> and now
> >> even a panic and stackdump (that's new).
> >>
> >> The environment only has 4 units. Since I cannot run (or rather don't
> dare to
> >> run) upgrade-juju right now, can I upgrade them manually through ssh
> somehow?
> >> Does the control bucket or environment file need upgrading, too?
> >
> > I think you need to upgrade in stable minor steps.
> > 1.16.6 > 1.18.4
> > 1.18.4 > 1.20.1
> >
> > The juju client and server APIs evolved rapidly between 1.12.0 and
> > 1.18.0. The client-server combinations only work in single minor
> > version hops. The API used by the client is stable as of 1.18 and
> > future clients can have large hops, but the servers still upgraded in
> > single hops so that the envs are upgraded in the proper order.
>
>
>
> --
> Curtis Hovey
> Canonical Cloud Development and Operations
> http://launchpad.net/~sinzui
>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20140804/b40b1a36/attachment.html>


More information about the Juju mailing list