Closed hc-github-team-packer closed 2 years ago
hi @vmoravec I believe this was fixed in https://github.com/hashicorp/packer-plugin-googlecompute/pull/51. Please upgrade to the latest release of the Google Compute plugin for the fix.
packer {
required_plugins {
googlecompute = {
version = ">= 1.0.6"
source = "github.com/hashicorp/googlecompute"
}
}
}
I am going to close this issue as I believe it has been resolved. But if you are still running into issues with the latest release please leave a comment on this thread and I will gladly reopen. Cheers.
This issue was originally opened by @vmoravec in https://github.com/hashicorp/packer/issues/9960 and has been migrated to this repository. The original issue description is below.
Overview of the Issue
While using the
googlecompute
builder together with the optiondisk_name
, such a disk resource is not deleted when an instance is going to be deleted. Packer ignores the given configuration and creates a VM disk with the name of the instance. However, when deleting the instance, it is looking for the disk set bydisk_name
although it hasn't been created in the first place . In the end the disk named by the instance, must be deleted manually.Reproduction Steps
Set
disk_name
option for thegooglecompute
builderPacker version
Packer version: 1.6.2 [go1.13.15 linux amd64]
Simplified Packer Buildfile
Operating system and Environment details
SUSE Linux Enterprise Server 12 SP5
Log Fragments and crash.log files