This commit fixes errors like this in the vsphere post-processor when using floppy files in the builder step:
Error: File (/var/folders/zl/57c1vmr532z_ryf1scw53_b9ycmxh7/T/packer964492999) could not be found
The configure VMX step re-adds the floppy files, so we need to configure the VMX and _then_ clean the VMX in that order.
Also fixed the error message to be clear that the image was not found in any of
the projects that we attempted to search, rather than keep the error message
from the last project, which may be confusing to users.
While running through the getting-started examples, I ran into a strange
error:
packer $ packer validate example.json
Failed to parse template: Error in line 16, char 2: invalid character
'"' after object key:value pair
"provisioners": [{
packer $
The error was not immediately obvious, as this is my first time working
with Packer, and like many users this also happens to be my first time
working with JSON.
Solution:
I was missing a comma after the 'builders' configuration. I'm sure this
is a common problem, so let's specifically mention that in the document.
While running through the getting-started examples, I ran into a strange
error:
packer $ packer validate example.json
Failed to parse template: Error in line 16, char 2: invalid character
'"' after object key:value pair
"provisioners": [{
packer $
The error was not immediately obvious, as this is my first time working
with Packer, and like many users this also happens to be my first time
working with JSON.
Solution:
I was missing a comma after the 'builders' configuration. I'm sure this
is a common problem, so let's specifically mention that in the document.
As per https://github.com/mitchellh/packer/issues/1142, it's critical to add openstack_provider: rackspace in order to get anything to work reliably with Rackspace and Packer in 6.0.
Question: should the openstack_provider field now be marked as required?