-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Traceback on salt-run cloud.destroy $host #10947
Comments
This is with the latest 2014.1 packages under Ubuntu. |
This also results in renamed_keys (from destroy) not being removed even though
is set in /etc/salt/cloud . |
Thanks for the report! @techhat ping |
Any update on this? This is happening here as well. Exact same problem.
|
And for completeness:
|
BTW do you also get the traceback-is-shown-twice behaviour? |
@clearclaw , I think you meant to ask @tateeskew if he gets the traceback-is-shown-twice behaviour? Also, do you know for sure which version the error began? Or maybe you don't try to cloud.destroy very often? //here to help via CodeTriage |
Hmm, now I see that destroy was only added to the runner in 2014.01.
|
Things I notice; 2.From the stacktrace, the calling method fails on line 1769 which is the last DocString line abve in my prior message, |
94c3c68 cannot hurt you ... it can only give you less tracebacks as you would have keyerrors more over all the errors you have. |
thank you for your quick reply, @kiorky ! I agree, that commit seems very good, but the users in this thread do not yet have it, right? The errors they see are Key Errors, which in turn appear to be due to the cloud not found, per my research. I'm sorry if my comments were not clear :). I was making notes on the stacktrace, looking at each line and checking for possible failure causes. The item#1 is the summary. |
This is still happening here:
|
Hmm, rats, so I presume the commit we were discussing, being authored a month ago, 94c3c68 1 parent 0d8661b That indicates we definitely need a new fix. Ty @tateeskew for all your details! |
@AnneTheAgile That's actually not true. It appears that 94c3c68 was not cherry-picked into the 2014.1 branch (and so is not in 2014.1.1). Our dot releases are not cut from I have now cherry-picked that commit, and it will be in 2014.1.2. |
@basepi thank you that's great news! |
Can someone test this again? I think since I cherry-picked the commit mentioned above that this is resolved. |
This is still a problem with 2014.1.7 :
|
I am going around to some older issues. Is this still an issue on some newer releases? Has anyone run into this one on 2014.7.x or, even better to test, 2015.5.x releases? The 2014.1 branch has been retired, and we will no longer be releasing from 2014.7, either. Is this still a problem or can this be closed? |
Since I didn't hear back here, and I think this is fixed, I am going to close this. If this remains an issue for anyone, please comment and we will be glad to re-open and address any concerns. |
The text was updated successfully, but these errors were encountered: