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

salt-cloud: Make automatic destruction of VM after create failure optional #46151

Open
mark-hyde opened this issue Feb 22, 2018 · 6 comments
Open
Labels
Feature new functionality including changes to functionality and code refactors, etc. Salt-Cloud
Milestone

Comments

@mark-hyde
Copy link
Contributor

Description of Issue/Question

If you use salt-cloud -p name_of_vm to create a VM, and during the process of building that VM the salt-cloud is unable to connect to the device, then an exception is raised which deletes the VM.

e.g.
https://github.com/saltstack/salt/blob/develop/salt/cloud/clouds/openstack.py#L689-L696
https://github.com/saltstack/salt/blob/develop/salt/cloud/clouds/nova.py#L998-L1005

The failure may be a consequence of the specific image you are using to build the device, or perhaps an intermittent failure with the underlying infrastructure which needs further investigation.

Given that the device is automatically deleted in these circumstances makes it difficult to investigate the source of the underlying issue, or perform network troubleshooting against the instance since it no longer exists.

It should be possible in these circumstances to disable the automatic destruction of the device

e.g.
Have an option in salt-cloud:
destroy_vm_on_create_failure: (with a default value of True, but which could be set to False when troubleshooting issues)

Regards
Mark

@garethgreenaway garethgreenaway added this to the Approved milestone Feb 22, 2018
@garethgreenaway garethgreenaway added Feature new functionality including changes to functionality and code refactors, etc. Salt-Cloud labels Feb 22, 2018
@stale
Copy link

stale bot commented Jun 7, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

@stale stale bot added the stale label Jun 7, 2019
@mark-hyde
Copy link
Contributor Author

I still think this may be a useful feature.

@stale
Copy link

stale bot commented Jun 10, 2019

Thank you for updating this issue. It is no longer marked as stale.

@stale stale bot removed the stale label Jun 10, 2019
@stale
Copy link

stale bot commented Jan 8, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

@stale stale bot added the stale label Jan 8, 2020
@mark-hyde
Copy link
Contributor Author

bump

@stale
Copy link

stale bot commented Jan 8, 2020

Thank you for updating this issue. It is no longer marked as stale.

@stale stale bot removed the stale label Jan 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature new functionality including changes to functionality and code refactors, etc. Salt-Cloud
2 participants