I am using packer to make AMIs. I have placed most of my code within Chef and I using the Chef-Solo provisioner to call the required cookbooks. I have configured a reboot within my cookbook for certain software installs. Whenever the reboot happens during the packer build process it will cause the build to fail. I receive a fatal error after the reboot is initiated causing packer to begin a clean-up due to lose of connection. Is there a way to make the chef-solo provisioner expect a reboot or handle a reboot that is happening from chef cookbooks?
Error ==> Some builds didn't complete successfully and had errors: --> amazon-ebs: Error executing Chef: Non-zero exit status: 35 Thanks, Kevin -- 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 packer-tool+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/3743eb80-3730-48e4-ad70-dc9080b767eb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
