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

Catch blocking bootstrap scripts #64

Open
djesionek opened this issue Aug 7, 2018 · 2 comments
Open

Catch blocking bootstrap scripts #64

djesionek opened this issue Aug 7, 2018 · 2 comments

Comments

@djesionek
Copy link

djesionek commented Aug 7, 2018

What: Setting a bootstrap script that blocks execution of the provisioning process may result in orphaned VMs, that are not shown in the list of deployes VMs and therefore can't be deleted.

Steps to reproduce: Use sudo in a bootstrap script. When sudo asks interactively for a password the execution will be blocked.
Use apt install without the -y flag which blocks until interactive confirmation occurs in a bootstrap script. This is just an example that should block the provisioning. In productions this may occur in a variety of cases with other commands.

Possible Fix: Show VMs in "Still Provisioning" state in the list of VMs and make it possible to open the provisioning log and to cancel provisioning.

@chrisipa
Copy link
Owner

chrisipa commented Aug 8, 2018

The usage of sudo commands should be possible without blocking the script. There must be something else which blocks the execution. Can you add an example script which is not working?

The rollback in such a case could also be quite hard because the Terraform state may be not complete to execute the destroy command.

@djesionek
Copy link
Author

After rechecking it wasn't a sudo command that blocked provisioning. First comment was updated accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants