-
Notifications
You must be signed in to change notification settings - Fork 922
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
Update CloudStack NodeStates for Stopped/Stopping #246
Conversation
Synchronizing changes
Synchronizing fork
Synchronizing fork
Synchronizing fork
Synchronizing fork
Synchronizing fork
Synchronizing fork
Synchronizing fork
Synchronizing fork
…OPPED as opposed to TERMINATED.
We've discussed this on the IRC with @cderamus yesterday. I think we should also map This means that currently your code might fail if you wait until node.state == stopped because node might actually still be in stopping state. |
I've merged the changes mentioned above and merged this into trunk. Thanks. |
No description provided.