Hello all,

I'm running packer as follows:

packer build -on-error=ask -var-file="rancheros-config.json" -var-file=
"vsphere.json" -var-file="vsphere_password.json" rancheros.json

The config files and packer log are available 
here: https://gist.github.com/AndrewSav/c2fa438f82701b9826e3800fad516ec5

Questions:

1) Why am I not asked on failure if I'd like to clean up? Instead packer 
goes ahead and deletes the built VM leaving me with know means to diagnose.

https://www.packer.io/docs/commands/build.html#on-error-cleanup says:

-on-error=cleanup 
<https://www.packer.io/docs/commands/build.html#on-error-cleanup>
 (default), -on-error=abort, -on-error=ask - Selects what to do when the 
build fails. cleanupcleans up after the previous steps, deleting temporary 
files and virtual machines. abort exits without any cleanup, which might 
require the next build to use -force. ask presents a prompt and waits for 
you to decide to clean up, abort, or retry the failed step.

As you can see above I do specify ask, the build fails but there is no 
prompt to cleanup/abort. What am I doing wrong?

2) The reason why the build fails is a error code from ovftool. ovftool 
also writes stderr/stdout output that give more diagnostic information as 
to why it failed. This output cannot be found anywhere. How do I see it?

Andrew

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/c0452937-caca-4650-b1a6-d5a0e34c5aef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to