-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reboot(wait) operation crashes #264
Comments
Jeff Forcier (bitprophet) posted: Updated metadata, cleaned up description so the output is in a code block. on 2010-12-08 at 01:17pm EST |
Jeff Forcier (bitprophet) posted: Nothing springs to mind for a cause of your problem, but hopefully it's something simple. If it's an innocent order-of-operations problem where your connections dict is being cleared out beforehand, then we can just update the For a first step, if you could throw some debug print statements in there to introspect the key/values of Otherwise, if you're able to provide your fabfile or a snippet thereof, I can try to replicate. Don't have easy access to Python 2.7 on OS X but I've been meaning to work out a multi-Python setup for a while, may be a good excuse. Are you on OS X 10.5 or 10.6? on 2010-12-08 at 01:22pm EST |
Jason Gerry (jgerry) posted: Happy to help out any way I can. I'm actually on vacation until Monday, I'm trying not to work (too much at least) but when I get back I'll poke around at it some more and get the debugging info. I've been doing my development on Python 2.7 / OS X 10.6, but I'm moving this project to a CentOS 5.5 environment for actual use first thing next week. I'm curious as to whether I'll be able to reproduce the issue in a Linux environment. on 2010-12-08 at 01:32pm EST |
Jeff Forcier (bitprophet) posted: Cool, no rush obviously :) I'm going to be busy myself so I may not even have time to review anything until next week. Definitely interested in whether it is reproducible on other platforms or not, that's always helpful. on 2010-12-08 at 06:30pm EST |
Jason Gerry (jgerry) posted: Migrated to my CentOS 5.5 env today, the error persists. I'll try to get some more debug info to you this week when I have time. on 2010-12-14 at 11:06am EST |
Jason Gerry (jgerry) posted: From my fabfile, I've commented out the reboot() function and added some debug:
Output:
So yes, it looks like that dict is empty. on 2010-12-17 at 02:32pm EST |
Jeff Forcier (bitprophet) posted: Definitely odd, but hopefully not indicative of something bigger. Will try to slap a patch in soon. Should be as simple as wrapping the on 2010-12-29 at 02:57pm EST |
Jeff Forcier (bitprophet) posted: Applied in changeset commit:710d4ae9790deb48ae0067d352fca69695a29504. on 2011-02-27 at 12:05am EST |
Miquel Torres (tobami) posted: I can confirm this bug on Fabric 1.0.0. I see the fix is for the 0.9.x branch, have you patched 1.0.x as well? on 2011-03-23 at 06:09am EDT |
Jeff Forcier (bitprophet) posted: Should have, yes. From now on, higher release numbers will include lower releases' bugfixes unless said bugfixes no longer apply for some reason. In this case, on 2011-03-23 at 03:49pm EDT |
Description
Trying to use the reboot() operation. The reboot occurs, but then the script errors out. No waiting or continuing.
The reboot(180) call is the very first thing in my function, so I don't suspect anything else is causing the issue.
My environment:
Mac OS X, Python 2.7, Fabric 0.9.3
output from my last try:
Originally submitted by Jason Gerry (jgerry) on 2010-12-02 at 02:48pm EST
Closed as Done on 2011-03-23 at 03:49pm EDT
The text was updated successfully, but these errors were encountered: