upgrade step "set AvailZone in instanceData" failed: no instances found
seems suspicious.
What version of MAAS are you running?
It is possible that it would come before MAAS availability zones?

Certainly we couldn't really find 0 instances in MAAS because the machine
this is running on has to be at least one of them.

Unfortunately a few people are on vacation this week in preparation for our
sprint next week, but hopefully we can still get ahold of the people who
were working on this upgrade step.

John
=:->


On Wed, Apr 8, 2015 at 4:49 AM, Joshua Randall <josh.rand...@genomicsltd.com
> wrote:

> I ran `juju upgrade-juju` today to upgrade a MAAS environment to Juju
> version 1.22.0 and now `juju status` says that the upgrade has failed (and
> thus we have limited access to the state server since an upgrade is in
> progress). What can I do to manually complete the upgrade?
>
> `juju status` shows the following error:
> > environment: maas
> > machines:
> >   "0":
> >     agent-state: error
> >     agent-state-info: 'upgrade to 1.22.0 failed (giving up): set
> AvailZone in instanceData:
> >       no instances found'
> >     agent-version: 1.22.0
> > ...
>
> While '/var/log/juju/machine-0.log’ on machine 0 has:
> > 2015-04-08 00:03:16 DEBUG juju.provider.maas environprovider.go:32
> opening environment "maas".
> > 2015-04-08 00:03:16 ERROR juju.upgrade upgrade.go:134 upgrade step "set
> AvailZone in instanceData" failed: no instances found
> > 2015-04-08 00:03:16 ERROR juju.cmd.jujud upgrade.go:360 upgrade from
> 1.21.1 to 1.22.0 for "machine-0" failed (will retry): set AvailZone in
> instanceData: no instances found
> > 2015-04-08 00:03:16 DEBUG juju.apiserver apiserver.go:265 <- [3]
> machine-0
> {"RequestId":22,"Type":"Machiner","Request":"Life","Params":{"Entities":[{"Tag":"machine-0"}]}}
> > 2015-04-08 00:03:16 DEBUG juju.apiserver apiserver.go:272 -> [3]
> machine-0 410.699us
> {"RequestId":22,"Response":{"Results":[{"Life":"alive","Error":null}]}}
> Machiner[""].Life
> > 2015-04-08 00:03:16 DEBUG juju.apiserver apiserver.go:265 <- [3]
> machine-0
> {"RequestId":23,"Type":"Machiner","Request":"SetStatus","Params":{"Entities":[{"Tag":"machine-0","Status":"
> > error","Info":"upgrade to 1.22.0 failed (will retry): set AvailZone in
> instanceData: no instances found","Data":null}]}}
>
> I would very much appreciate any pointers in the right direction on how to
> go about resolving this… any ideas?
>
> Cheers,
>
> Josh.
>
>
> --
> This email is sent on behalf of Genomics Limited, a limited company
> registered in England and Wales with registered number 8839972, VAT
> registered number 189 2635 65 and registered office at 24 Cornhill, London,
> EC3V 3ND, United Kingdom.
> The contents of this e-mail and any attachments are confidential to the
> intended recipient. If you are not the intended recipient please do not use
> or publish its contents, contact Genomics Limited immediately at
> i...@genomicsltd.com then delete. You may not copy, forward, use or
> disclose the contents of this email to anybody else if you are not the
> intended recipient. Emails are not secure and may contain viruses.
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Reply via email to