On Wed, Apr 8, 2015 at 2:22 AM, Andrew Wilkins <[email protected]> wrote: > I'd want to hear from others on this matter, as my experience with repairing > upgrades is limited. > I recommend you don't take any action on the following immediately, until > others have weighed in. > > John figured that the error you've got could be related to having containers > in the environment. > Unfortunately it appears that the upgrade step doesn't work if there are any > containers, as it > mistakenly thinks they're MAAS machines (and is rightly told that they don't > exist in MAAS). It'd > be great to get confirmation that you do have containers in your > environment. > > Now, this could be repaired without *too* much trouble I think. That upgrade > step is the last one > to upgrade to 1.22 completely. So, options are: > 1. Hand-edit the agent's config file so it thinks it's finished upgrading. > 2. Fix Mongo so the upgrade step thinks it has nothing to do. > 3. Wait for a fix to Juju. I'm not sure how long that'll take, as we're all > about to travel. I've just filed: > https://bugs.launchpad.net/juju-core/+bug/1441478 > > #1 will work, but will mean that you'll have no availability-zone > information in your instances. > I'm not sure if that'd cause any immediate problems (Eric?), but it will > mean that charms won't > be able to take advantage of that information.
That is correct. The availability zone is recorded for the sake of unit-get. -eric > > #2 would be preferable; this would involve opening the Juju state database > with the mongo > shell, and updating all documents in the "instancedata" collection so that > they have "availzone" > fields. > > Cheers, > Andrew > > -- > Juju mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > -- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
