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
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 m...@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 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
In addition, there's also a `juju retry-provisioning machine-number` 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 nate.fi...@canonical.com 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 m...@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 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
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 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 customization for MAAS
Hi, Sorry for asking here. Got a need to do a simple change in deployed machines on maas (alter the network/ interfaces file). I didn't want to add that to one of my charm hooks as it doesn's seem the appropriate place for it. Anyone done it before and can give me some hints. I use the curtain installer and tried all sorts of things with the curtain preseed files without luck. Thanks, Sameer-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: reviewboard update
Awesome, nice work! On Nov 15, 2014 12:07 AM, Eric Snow eric.s...@canonical.com wrote: FYI, I was able to solve 3 reviewboard-github integration issues today: 1. pull requests for branches other than master now work (e.g. 1.21 backports) 2. no more hitting rate limits (5000 requests/hour limit instead of 60) 3. pull request bodies now get updated with a link to the new review request If you have any trouble with any of these please let me know. Thanks! -eric -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
