machine state stuck at "pending"

Mark Shuttleworth mark at
Sat Nov 15 18:01:42 UTC 2014

On 14/11/14 02:39, Sameer Zeidat wrote:
>  Hello,
> I'm running juju 1.20.1 on a test maas cluster. Every now and then when I run juju add-machine the machine gets stuck at "pending" state (permanently). Maas shows status as "Failed deployment".
> Is there a way to force machine state to error so I can retry-provisioning on it? I don't want to destroy it as I have some service deployment scripts that rely on machine number (using --to # deployment option).
> Appreciating your help.

Hi Sameer

A range of those 'pending' container issues were fixed during the set of
releases from 1.20.1 to 1.20.11. I think it would be worth your updating
to the latest 1.20 release. If you're on Ubuntu, add this to your

   deb trusty main

That should give you 1.20.11.

Let us know if you still see any issues with containers getting stuck on
the way up. Also, it's a great idea to be able to nuke-and-retry in the
event that this does happen, I'll find out if we have a nice way to add
that regardless (a stuck container might happen thanks to cosmic rays,
we should have an escape mechanism). Ideally, Juju should detect the
issue and nuke the container, trying again on your behalf.


More information about the Juju mailing list