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

Choosing "abort without cleanup" after a cancelled build deletes the VM anyways #94

Open
nagypeterjob opened this issue Oct 26, 2021 · 1 comment

Comments

@nagypeterjob
Copy link

👋🏻 Hey, we've found an interesting issue

Description

When a build is cancelled for some reason (manual interrupt, or the build fails), the dialog offers CA / R actions to perform with the cancelled VM.
A = abort without cleanup
In case A is selected, the VM should be kept for inspection. Instead, choosing A results in the deletion of the VM.

Proof

veertu-anka-vm-clone: [c] Clean up and exit, [a] abort without cleanup, or [r] retry step (build may fail even if retry succeeds)? a
2021-10-26T13:26:43Z:     veertu-anka-vm-clone:  [ERROR]: User interrupted execution
2021-10-26T13:26:43Z: ==> veertu-anka-vm-clone: Deleting VM baseAndroid-13.1-1635247832

Steps to reproduce

  1. start a build
  2. cancel the build
  3. choose option (a)
  4. check if the build VM was deleted

Misc

plugin version: 2.1.0
anka cli version: 2.5.3

@NorseGaud
Copy link
Member

Seems like this is a packer prompt. I'll need to take a look as I don't remember it being an option, but haven't checked since packer's latest changes.

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

No branches or pull requests

2 participants