Re: machine state stuck at "pending"
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: https://lists.ubuntu.com/mailman/listinfo/juju
RE: machine state stuck at "pending"
Reporting back. The latest release from the archive fixed it. Thank you. Regards, Sameer -Original Message- From: "Sameer Zeidat" Sent: 16/11/2014 9:55 AM To: "Mark Shuttleworth" ; "Juju email list" Subject: RE: machine state stuck at "pending" Thank you. I will try it. From: Mark Shuttleworth Sent: 16/11/2014 5:01 AM To: Sameer Zeidat; Juju email list Subject: Re: machine state stuck at "pending" 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 /etc/apt/sources.list: deb http://ppa.launchpad.net/juju/stable/ubuntu 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. Mark-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
RE: machine state stuck at "pending"
Thank you. I will try it. -Original Message- From: "Mark Shuttleworth" Sent: 16/11/2014 5:01 AM To: "Sameer Zeidat" ; "Juju email list" Subject: Re: machine state stuck at "pending" 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 /etc/apt/sources.list: deb http://ppa.launchpad.net/juju/stable/ubuntu 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. Mark -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: machine state stuck at "pending"
In addition, there's also a `juju retry-provisioning ` which can be used after you upgrade in the event you encounter provisioning issues in the future. Typical provisioning issues for machines include resource limitations on account and errors downloading required dependencies. Marco On Sun Nov 16 2014 at 2:34:59 PM Nate Finch wrote: > Definitely the low 1.20.x releases had a couple issues especially with > containers. These were all fixed later, as Mark mentioned. Hopefully > that'll solve your problems. > On Nov 15, 2014 1:02 PM, "Mark Shuttleworth" 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 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 >> /etc/apt/sources.list: >> >>deb http://ppa.launchpad.net/juju/stable/ubuntu 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. >> >> Mark >> >> >> -- >> 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 > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: machine state stuck at "pending"
Definitely the low 1.20.x releases had a couple issues especially with containers. These were all fixed later, as Mark mentioned. Hopefully that'll solve your problems. On Nov 15, 2014 1:02 PM, "Mark Shuttleworth" 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 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 > /etc/apt/sources.list: > >deb http://ppa.launchpad.net/juju/stable/ubuntu 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. > > Mark > > > -- > 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
Re: machine state stuck at "pending"
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 /etc/apt/sources.list: deb http://ppa.launchpad.net/juju/stable/ubuntu 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. Mark -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
machine state stuck at "pending"
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. Regards,Sameer-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
