generated from hashicorp/packer-plugin-scaffolding
-
Notifications
You must be signed in to change notification settings - Fork 58
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
Persistent disk images not deleted #246
Labels
Comments
I re-ran the same job with the
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview of the Issue
Root disks are not being cleaned up after image builds. I have found that the VMs which are created are cleaned up, but the root disks are not. I am using c3-highcpu-8 and am attaching 100GB pd-sdd disks. The auto-delete flag does not seem to be set, so builds are just littering the Google project with costly disks.
Reproduction Steps
I used this configuration:
If
image_name
is set to "foo", I end up with lingering persistent disks named like:foo-image-builder-1732137234
Plugin and Packer version
Packer: 1.12.0
googlecompute provider: 1.1.6
Simplified Packer Buildfile
Operating system and Environment details
Debian 24.04 running in GitHub Actions
Log Fragments and crash.log files
Beginning of log
The provisioners all run without error. I cannot share details under NDA with my client. But the shells do simple things like configure logrotation, install custom Python software, and configure systemd services.
The logs end with this.
At the end, I observe that the VM has been deleted, but the 100GB disk is still there.
The text was updated successfully, but these errors were encountered: