Skip to content

Instantly share code, notes, and snippets.

@edsykes
Created May 20, 2016 20:12
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save edsykes/650f8c0a7c2effde97aad20a1713d6fc to your computer and use it in GitHub Desktop.
Save edsykes/650f8c0a7c2effde97aad20a1713d6fc to your computer and use it in GitHub Desktop.
2016/05/20 20:49:28 ui: ==> amazon-instance: Uploading X509 Certificate...
==> amazon-instance: Uploading X509 Certificate...
2016/05/20 20:49:28 packer: 2016/05/20 20:49:28 Uploading file to '/tmp/cert.pem'
2016/05/20 20:49:30 packer: 2016/05/20 20:49:30 Uploading file to '/tmp/key.pem'
2016/05/20 20:49:32 ui: ==> amazon-instance: Bundling the volume...
==> amazon-instance: Bundling the volume...
2016/05/20 20:49:32 packer: 2016/05/20 20:49:32 [INFO] starting remote command: sudo -i -n ec2-bundle-vol -k /tmp/key.pem -u 970493245035 -c /tmp/cert.pem -r x86_64 -e /tmp/* -d /tmp -p image-1463773401 --batch --no-filter
2016/05/20 20:49:32 ui: amazon-instance: 'sudo' is not recognized as an internal or external command,
2016/05/20 20:49:32 packer: 2016/05/20 20:49:32 [INFO] command 'sudo -i -n ec2-bundle-vol -k /tmp/key.pem -u 970493245035 -c /tmp/cert.pem -r x86_64 -e /tmp/* -d /tmp -p image-1463773401 --batch --no-filter' exited with code: 1
amazon-instance: 'sudo' is not recognized as an internal or external command,
2016/05/20 20:49:32 ui: amazon-instance: operable program or batch file.
amazon-instance: operable program or batch file.
2016/05/20 20:49:32 ui error: ==> amazon-instance: Volume bundling failed. Please see the output above for more
==> amazon-instance: details on what went wrong.
==> amazon-instance:
==> amazon-instance: One common cause for this error is ec2-bundle-vol not being
==> amazon-instance: available on the target instance.
==> amazon-instance: Volume bundling failed. Please see the output above for more
==> amazon-instance: details on what went wrong.
==> amazon-instance:
==> amazon-instance: One common cause for this error is ec2-bundle-vol not being
==> amazon-instance: available on the target instance.
2016/05/20 20:49:32 ui: ==> amazon-instance: Terminating the source AWS instance...
==> amazon-instance: Terminating the source AWS instance...
2016/05/20 20:49:33 packer: 2016/05/20 20:49:33 Waiting for state to become: terminated
2016/05/20 20:49:33 packer: 2016/05/20 20:49:33 Allowing 300s to complete (change with AWS_TIMEOUT_SECONDS)
==> amazon-instance: Deleting temporary keypair...
2016/05/20 20:50:04 ui: ==> amazon-instance: Deleting temporary keypair...
2016/05/20 20:50:04 ui error: Build 'amazon-instance' errored: Volume bundling failed. Please see the output above for more
details on what went wrong.
One common cause for this error is ec2-bundle-vol not being
available on the target instance.
2016/05/20 20:50:04 Builds completed. Waiting on interrupt barrier...
Build 'amazon-instance' errored: Volume bundling failed. Please see the output above for more
details on what went wrong.
One common cause for this error is ec2-bundle-vol not being
available on the target instance.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment