-
Notifications
You must be signed in to change notification settings - Fork 108
Build fails when there are no additional configuration parameters to process #482
Copy link
Copy link
Closed
Copy link
Description
Overview of the Issue
Build fails when there are no additional configuration parameters to process
This PR seemingly caused the issue: #468
This line would appear to be the culprit: 5e944bc#diff-f81447593c9b389c1718a91e14307807b280b36f7c76f64a150637d6faba312bR1340
Reproduction Steps
Attempt to build using the vsphere-clone builder with none of the optional configuration options. This will result in a failure (see message below)
Packer Version
- 1.10.1
Plugin Version and Builders
- 1.4.1
Please select the builder.
- []
vsphere-iso -
vsphere-clone
VMware vSphere Version
- 7.0.3
Guest Operating System
- Windows Server 2022 21H2
Simplified Packer Buildfile
source "vsphere-clone" "test-agent" {
vcenter_server = "${var.vcenter_server}"
username = "${var.vsphere_username}"
password = "${var.vsphere_password}"
datacenter = "${var.vsphere_datacenter}"
cluster = "${var.vsphere_cluster}"
datastore = "${var.vsphere_datastore}"
folder = "${var.vsphere_folder}"
template = "${var.vsphere_template}"
vm_name = "${var.vm_name_prefix}:provisioning"
create_snapshot = true
linked_clone = false
NestedHV = true
communicator = "ssh"
ssh_username = "${var.admin_username}"
ssh_password = "${var.admin_password}"
}
build {
sources = [
"source.vsphere-clone.test-agent"
]
...
Operating System and Environment Details
Please add any information you can provide about the environment.
- Running packer using the hashicorp/packer image: link
Log Fragments and crash.log Files
error adding configuration parameters: no changes to apply
Step "StepConfigParams" failed, aborting...
Reactions are currently unavailable