Manual juju upgrade
Curtis Hovey-Canonical
curtis at canonical.com
Mon Aug 4 12:01:38 UTC 2014
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
More information about the Juju
mailing list