Re: machine state stuck at pending

2014-11-17 Thread Mark Shuttleworth
On 17/11/14 06:35, Sameer Zeidat wrote: Reporting back. The latest release from the archive fixed it. Thank you. Great to hear. We'll SRU 1.20.latest to Trusty and Utopic shortly. Mark -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at:

Re: machine state stuck at pending

2014-11-15 Thread Mark Shuttleworth
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

Re: machine state stuck at pending

2014-11-15 Thread Nate Finch
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

Re: machine state stuck at pending

2014-11-15 Thread Marco Ceppi
...@ubuntu.com wrote: 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

RE: machine state stuck at pending

2014-11-15 Thread Sameer Zeidat
Thank you. I will try it. -Original Message- From: Mark Shuttleworth m...@ubuntu.com Sent: ‎16/‎11/‎2014 5:01 AM To: Sameer Zeidat same...@yahoo.com; Juju email list juju@lists.ubuntu.com Subject: Re: machine state stuck at pending On 14/11/14 02:39, Sameer Zeidat wrote: Hello, I'm

machine state stuck at pending

2014-11-14 Thread Sameer Zeidat
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