Skip to content
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

Make sure that the machine is UP before trying to destroy it in GCP #1002

Merged
merged 1 commit into from Oct 26, 2018

Conversation

benhamad
Copy link
Contributor

This can cause problems since we issue API call without actually checking
if the node is up or not. One easy way to see the manifestation of this
bug is to create a deployment with a machine that has underscore in
it's name (It's not supported in GCP). And without even deploying,
try to destroy it. The expected behavior is nothing! Since the
machine is down. However, an exception is raised because nixops tries
to call the API to get the node.

This can cause problems since we issue API call without actually checking
if the node is up or not. One easy way to see the manifestation of this
bug is to create a deployment with a machine that has underscore in
it's  name (It's not supported in GCP). And without even deploying,
try to destroy it. The expected behavior is nothing! Since the
machine is down. However, an exception is raised because nixops tries
to call the API to get the node.
@AmineChikhaoui AmineChikhaoui merged commit 6da4190 into NixOS:master Oct 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants