So far, I haven't found out the version it works yet. I'm going to try with v1.3.0 I got from Megan.
https://releases.hashicorp.com/packer/1.2.0/packer_1.2.0_linux_amd64.zip ERROR! the playbook: packer_builder_type=amazon-ebs could not be found ERROR! the playbook: packer_builder_type=amazon-ebs could not be found https://releases.hashicorp.com/packer/1.2.1/packer_1.2.1_linux_amd64.zip ui error: --> aws-ext-il2: Error waiting for AMI Copy: unexpected state 'failed', wanted target 'available' https://releases.hashicorp.com/packer/1.2.2/packer_1.2.2_linux_amd64.zip errored: Error waiting for AMI Copy: unexpected state 'failed', wanted target 'available' thanks, John. On Thursday, August 30, 2018 at 2:39:31 AM UTC-7, Rickard von Essen wrote: > > It would be very helpful if you could try with an older version of Packer, > say 1.2.0. And report if it works there. > > On Wed, Aug 29, 2018, 22:35 John Roh <[email protected] <javascript:>> > wrote: > >> This is so weird that it doesn't make any sense. Recently, I have added a >> new jenkins-slave machine to build AMIs on a different accounts that we >> just aws IAM role permissions so that it much easy to create and to copy >> AMIs on different regions. >> >> Currently I have three other jenkins-slave running/creating/copying AMIs >> with custom KMS encrypted images to any regions I want to successfully. >> However, this new slave machine builds the AMI but it fails to copy so that >> there is image gets created at all. With the closed tickets below, I am >> having the same issues. >> >> https://github.com/hashicorp/packer/issues/6177 >> >> https://github.com/hashicorp/packer/issues/6569 >> >> >> Even though I have increased AWS_MAX_ATTEMPTS values or not, it still >> doesn't work at all (either 150 or 3000, there is no differences). I have >> used packer v1.3.0-dev from the given at the ticket, there is still error >> coming out. >> >> >> "provisioners": [ >> { >> "type": "shell", >> "inline": [ >> "#!/bin/sh -x", >> "export AWS_POLL_DELAY_SECONDS=30", >> "export AWS_MAX_ATTEMPTS=3000", >> "export AWS_TIMEOUT_SECONDS=3000" >> ] >> }, >> >> I have ran pip list that I have confirmed all four jenkin-slave machines >> got configured as below. >> >> ansible (2.4.1.0) >> aws-cfn-bootstrap (1.4) >> awscli (1.16.3) >> Babel (0.9.6) >> backports.ssl-match-hostname (3.5.0.1) >> boto3 (1.7.71) >> botocore (1.10.84) >> certifi (2018.4.16) >> cffi (1.6.0) >> cfn-tools (0.1.6) >> chardet (3.0.4) >> Cheetah (2.4.4) >> click (6.7) >> cloud-init (0.7.9) >> colorama (0.3.9) >> configobj (4.7.2) >> configshell-fb (1.1.23) >> cryptography (1.7.2) >> decorator (3.4.0) >> docutils (0.14) >> ecdsa (0.13) >> enum34 (1.0.4) >> ethtool (0.8) >> futures (3.2.0) >> httplib2 (0.9.2) >> idna (2.7) >> iniparse (0.4) >> iotop (0.6) >> ipaddress (1.0.16) >> IPy (0.75) >> javapackages (1.0.0) >> Jinja2 (2.7.2) >> jmespath (0.9.3) >> jsonpatch (1.2) >> jsonpointer (1.9) >> kitchen (1.1.1) >> kmod (0.1) >> langtable (0.0.31) >> lockfile (0.12.2) >> lxml (3.2.1) >> Markdown (2.4.1) >> MarkupSafe (0.11) >> paramiko (1.16.1) >> passlib (1.6.5) >> pcp (1.2) >> perf (0.1) >> Pillow (2.0.0) >> pip (9.0.1) >> ply (3.4) >> policycoreutils-default-encoding (0.1) >> prettytable (0.7.2) >> pyasn1 (0.4.4) >> pycparser (2.14) >> pycrypto (2.6.1) >> pycurl (7.19.0) >> Pygments (1.4) >> pygobject (3.22.0) >> pygpgme (0.3) >> pyliblzma (0.5.3) >> pyparsing (1.5.6) >> pyserial (2.6) >> pystache (0.5.4) >> python-augeas (0.5.0) >> python-daemon (2.1.2) >> python-dateutil (2.7.3) >> python-dmidecode (3.10.13) >> python-keyczar (0.71rc0) >> python-linux-procfs (0.4.9) >> pyudev (0.21.0) >> pyxattr (0.5.1) >> PyYAML (3.13) >> requests (2.19.1) >> rsa (3.4.2) >> rtslib-fb (2.1.63) >> s3transfer (0.1.13) >> schedutils (0.4) >> seobject (0.1) >> sepolicy (1.1) >> setuptools (40.0.0) >> six (1.11.0) >> slip (0.4.0) >> slip.dbus (0.4.0) >> system-storage-manager (0.4) >> targetcli-fb (2.1.fb46) >> urlgrabber (3.10) >> urllib3 (1.23) >> urwid (1.1.1) >> wheel (0.31.1) >> yum-langpacks (0.4.2) >> yum-metadata-parser (1.1.4) >> Have you ran into this error and know how to make it working? >> >> Thanks, >> >> John. >> >> -- >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/packer-tool/c8aaf5e9-d4ff-4ac7-9cf7-e695954cc694%40googlegroups.com >> >> <https://groups.google.com/d/msgid/packer-tool/c8aaf5e9-d4ff-4ac7-9cf7-e695954cc694%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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/67a9408d-d63a-48d3-8b5a-0d476ce959da%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
