I have several images in a pipeline being built by Packer, all using the 
same template, more or less.

High-level:

   - AWS EBS Builder
   - Copies resulting AMI to several regions
   - Puppet Masterless Provisioner
   - Several Shell Provisioners

All of the other images run through without any issue, however for some 
reason the Amazon AWS ECS image keeps getting tripped up at copy time.  
Thought maybe it was the poll rate causing some sort of API throttling, but 
when increasing it to 5 seconds, the error still persists.  Here's the log 
with debug entries:


2018/04/14 00:29:50 ui: ==> amazon-ebs: Waiting for AMI to become ready...
==> amazon-ebs: Waiting for AMI to become ready...
2018/04/14 00:29:50 packer: 2018/04/14 00:29:50 Waiting for state to 
become: available
2018/04/14 00:29:50 packer: 2018/04/14 00:29:50 Using 5s as polling delay 
(change with AWS_POLL_DELAY_SECONDS)
2018/04/14 00:29:50 packer: 2018/04/14 00:29:50 Allowing 300s to complete 
(change with AWS_TIMEOUT_SECONDS)
2018/04/14 00:32:01 ui: ==> amazon-ebs: Copying AMI (ami-e1610399) to other 
regions...
==> amazon-ebs: Copying AMI (ami-e1610399) to other regions...
2018/04/14 00:32:01 ui:     amazon-ebs: Copying to: us-east-1
    amazon-ebs: Copying to: us-east-1
2018/04/14 00:32:01 ui:     amazon-ebs: Copying to: us-east-2
    amazon-ebs: Copying to: us-east-2
2018/04/14 00:32:01 ui:     amazon-ebs: Copying to: us-west-1
    amazon-ebs: Copying to: us-west-1
2018/04/14 00:32:01 ui:     amazon-ebs: Copying to: eu-west-1
    amazon-ebs: Copying to: eu-west-1
2018/04/14 00:32:01 ui:     amazon-ebs: Copying to: ap-southeast-1
    amazon-ebs: Copying to: ap-southeast-1
2018/04/14 00:32:01 ui:     amazon-ebs: Copying to: eu-central-1
    amazon-ebs: Copying to: eu-central-1
2018/04/14 00:32:01 ui:     amazon-ebs: Waiting for all copies to 
complete...
    amazon-ebs: Waiting for all copies to complete...
2018/04/14 00:32:01 packer: 2018/04/14 00:32:01 Waiting for state to 
become: available
2018/04/14 00:32:01 packer: 2018/04/14 00:32:01 Using 5s as polling delay 
(change with AWS_POLL_DELAY_SECONDS)
2018/04/14 00:32:01 packer: 2018/04/14 00:32:01 Allowing 300s to complete 
(change with AWS_TIMEOUT_SECONDS)
2018/04/14 00:32:02 packer: 2018/04/14 00:32:02 Waiting for state to 
become: available
2018/04/14 00:32:02 packer: 2018/04/14 00:32:02 Using 5s as polling delay 
(change with AWS_POLL_DELAY_SECONDS)
2018/04/14 00:32:02 packer: 2018/04/14 00:32:02 Allowing 300s to complete 
(change with AWS_TIMEOUT_SECONDS)
2018/04/14 00:32:02 packer: 2018/04/14 00:32:02 Waiting for state to 
become: available
2018/04/14 00:32:02 packer: 2018/04/14 00:32:02 Using 5s as polling delay 
(change with AWS_POLL_DELAY_SECONDS)
2018/04/14 00:32:02 packer: 2018/04/14 00:32:02 Allowing 300s to complete 
(change with AWS_TIMEOUT_SECONDS)
2018/04/14 00:32:02 packer: 2018/04/14 00:32:02 Waiting for state to 
become: available
2018/04/14 00:32:02 packer: 2018/04/14 00:32:02 Using 5s as polling delay 
(change with AWS_POLL_DELAY_SECONDS)
2018/04/14 00:32:02 packer: 2018/04/14 00:32:02 Allowing 300s to complete 
(change with AWS_TIMEOUT_SECONDS)
2018/04/14 00:32:03 packer: 2018/04/14 00:32:03 Waiting for state to 
become: available
2018/04/14 00:32:03 packer: 2018/04/14 00:32:03 Using 5s as polling delay 
(change with AWS_POLL_DELAY_SECONDS)
2018/04/14 00:32:03 packer: 2018/04/14 00:32:03 Allowing 300s to complete 
(change with AWS_TIMEOUT_SECONDS)
2018/04/14 00:32:03 packer: 2018/04/14 00:32:03 Waiting for state to 
become: available
2018/04/14 00:32:03 packer: 2018/04/14 00:32:03 Using 5s as polling delay 
(change with AWS_POLL_DELAY_SECONDS)
2018/04/14 00:32:03 packer: 2018/04/14 00:32:03 Allowing 300s to complete 
(change with AWS_TIMEOUT_SECONDS)
2018/04/14 00:40:22 ui error: ==> amazon-ebs: 6 error(s) occurred:
==> amazon-ebs: 
==> amazon-ebs: * Error waiting for AMI (ami-4c8c9f2c) in region 
(us-west-1): couldn't find resource
==> amazon-ebs: * Error waiting for AMI (ami-0071d47f) in region 
(us-east-1): couldn't find resource
==> amazon-ebs: * Error waiting for AMI (ami-6f5b680a) in region 
(us-east-2): couldn't find resource
==> amazon-ebs: * Error waiting for AMI (ami-1ef5d167) in region 
(eu-west-1): couldn't find resource
==> amazon-ebs: * Error waiting for AMI (ami-85a485f9) in region 
(ap-southeast-1): couldn't find resource
==> amazon-ebs: * Error waiting for AMI (ami-8697cc6d) in region 
(eu-central-1): couldn't find resource
==> amazon-ebs: 6 error(s) occurred:
==> amazon-ebs: 
==> amazon-ebs: * Error waiting for AMI (ami-4c8c9f2c) in region 
(us-west-1): couldn't find resource
2018/04/14 00:40:22 ui: ==> amazon-ebs: Deregistering the AMI because 
cancellation or error...
==> amazon-ebs: * Error waiting for AMI (ami-0071d47f) in region 
(us-east-1): couldn't find resource
==> amazon-ebs: * Error waiting for AMI (ami-6f5b680a) in region 
(us-east-2): couldn't find resource
==> amazon-ebs: * Error waiting for AMI (ami-1ef5d167) in region 
(eu-west-1): couldn't find resource
==> amazon-ebs: * Error waiting for AMI (ami-85a485f9) in region 
(ap-southeast-1): couldn't find resource
==> amazon-ebs: * Error waiting for AMI (ami-8697cc6d) in region 
(eu-central-1): couldn't find resource
==> amazon-ebs: Deregistering the AMI because cancellation or error...
2018/04/14 00:40:22 ui error: ==> amazon-ebs: Error deregistering AMI, may 
still be around: InvalidAMIID.Unavailable: The image ID 'ami-e1610399' is 
no longer available
==> amazon-ebs:     status code: 400, request id: 
79dc72fd-00e4-4529-9569-662cb7230bef
==> amazon-ebs: Error deregistering AMI, may still be around: 
InvalidAMIID.Unavailable: The image ID 'ami-e1610399' is no longer available
2018/04/14 00:40:22 ui: ==> amazon-ebs: Terminating the source AWS 
instance...


I'm at a loss.  Sometimes re-running the build allows it to succeed.  Any 
ideas?


Thanks!

-- 
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/92739363-0e46-4733-bcd4-b430707d1ae3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to