Megn, "Copy image failed with an internal error" is what I spotted on ec2 console. I have re-run the build with AWS_POLL_DELAY_SECONDS=50 AWS_MAX_ATTEMPTS=500 PACKER_LOG=1 packer build but still not passing and stuck with the same error message.
I wonder what the issue is occurring all of sudden on new jenkins slave machine that the other build machines are working fine with packer v1.2.3 but why not on this new machine which created from the puppetizing it. John. On Thursday, August 30, 2018 at 2:41:59 PM UTC-7, Megan Marsh wrote: > > This is really strange, and I can't reproduce what I'm seeing in your > logs. How old is your 1.3.0-dev version? It may have a bug in it that's > since been resolved. Can you try a more recent build? I can't attach one > to this email because it is too big but I will upload a recent build to > https://github.com/hashicorp/packer/issues/6569. > > Specifically, I can't get this log message when running the above line of > code you're sharing: > >> No AWS timeout and polling overrides have been set. Packer will defalt to >> waiter-specific delays and timeouts. If you would like to customize the >> length of time between retries and max number of retries you may do so by >> setting the environment variables AWS_POLL_DELAY_SECONDS and >> AWS_MAX_ATTEMPTS to your desired values. > > > Instead, I get the correct log message: > >> WARNING: AWS_MAX_ATTEMPTS and AWS_TIMEOUT_SECONDS are both set. Packer >> will be using AWS_MAX_ATTEMPTS and discarding AWS_TIMEOUT_SECONDS. If you >> have not set AWS_POLL_DELAY_SECONDS, Packer will default to a 2 second poll >> delay. > > > On Thu, Aug 30, 2018 at 2:32 PM Megan Marsh <[email protected] > <javascript:>> wrote: > >> This is really strange, and I can't reproduce what I'm seeing in your >> logs. How old is your 1.3.0-dev version? I'm attaching a linux build of >> today's Master branch because it looks like you're running on CentOS; let >> me know if the problem persists with this build. >> >> Specifically, I can't get this log message when running the above line of >> code you're sharing: >> >>> No AWS timeout and polling overrides have been set. Packer will defalt >>> to waiter-specific delays and timeouts. If you would like to customize the >>> length of time between retries and max number of retries you may do so by >>> setting the environment variables AWS_POLL_DELAY_SECONDS and >>> AWS_MAX_ATTEMPTS to your desired values. >> >> >> Instead, I get the correct log message: >> >>> WARNING: AWS_MAX_ATTEMPTS and AWS_TIMEOUT_SECONDS are both set. Packer >>> will be using AWS_MAX_ATTEMPTS and discarding AWS_TIMEOUT_SECONDS. If you >>> have not set AWS_POLL_DELAY_SECONDS, Packer will default to a 2 second poll >>> delay. >> >> -- 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/bf2dabb7-2275-475c-8c67-6c8d40d37ecb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
