-
Notifications
You must be signed in to change notification settings - Fork 90
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
post-processor vsphere
: "error destroying builder artifact"
#279
Comments
vsphere-iso
: build fails trying to clean up artifact after running post-processor
vsphere-iso
: build fails trying to clean up artifact after running post-processorpost-processor vsphere
: fails to clean up artifact
This appears to be coming from the Decode function imported from github.com/hashicorp/packer-plugin-sdk/template/config. While this is an upstream issue, this message may be able to be suppressed as it's not impacting the desired results. I'll test my proposed changes and submit a pull request to address this one and link an upstream issue. Update: After a couple hours of down the rabbithole I've not be able to track down the exact cause and either a fix or workaround. Might need to "phone a friend" @lbajolet-hashicorp for later assistance. |
post-processor vsphere
: fails to clean up artifactpost-processor vsphere
: "error destroying builder artifact"
Overview of the Issue
After running the vsphere post-processor, the packer build fails while trying to clean up the artifact:
The OVF is successfully uploaded to vCenter, and the VM files (.ovf, .vmdk, etc) are successfully deleted from the local filesystem where packer runs, but nonetheless the build fails and exits with code 1.
If I set keep_input_artifact to
true
, then the build completes successfully with no errors, but obviously the VM files are kept on the local filesystem.This bug report is perhaps a duplicate (hashicorp/packer#11101).
Reproduction Steps
Configure the vsphere post-processor as per the simplified buildfile provided below. Ensure the keep_input_artifact option is set to false (which is the default setting) in order to reproduce the issue.
Packer Version
1.8.7
Plugin Version and Builders
1.1.2, vsphere-iso
VMware vSphere Version
7.0U3
Simplified Packer Buildfile
Log
The text was updated successfully, but these errors were encountered: