Mostly AMI creation succeeds. However, the following failure has occasionally been seen.
It seems to be a random occurrence or at least I don't currently know of a way to cause it to occur.
There were no prior errors in the scripts.
amazon-ebs output will be in this color.
==> amazon-ebs: Prevalidating AMI Name: gitlab_runner-06Mar2018
amazon-ebs: Found Image ID: ami-0b541372
==> amazon-ebs: Creating temporary keypair: packer_5a9e7eec-66b7-7836-c6c2-71b28c4387f3
==> amazon-ebs: Creating temporary security group for this instance: packer_5a9e7ef0-f1b4-821a-1c0c-1f39412886da
==> amazon-ebs: Authorizing access to port 22 from 0.0.0.0/0 in the temporary security group...
==> amazon-ebs: Launching a source AWS instance...
==> amazon-ebs: Adding tags to source instance
amazon-ebs: Adding tag: "Name": "Packer Builder"
amazon-ebs: Instance ID: i-057730c18bcf34b36
==> amazon-ebs: Waiting for instance (i-057730c18bcf34b36) to become ready...
==> amazon-ebs: Waiting for SSH to become available...
==> amazon-ebs: Connected to SSH!
==> amazon-ebs: Uploading scripts/init/runner-init.sh => /tmp/runner-init.sh
==> amazon-ebs: Provisioning with shell script: scripts/base/update-system.sh
amazon-ebs: Started running script_3644.sh
amazon-ebs: > Updating package list
amazon-ebs: Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
amazon-ebs: Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease
amazon-ebs: Get:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
amazon-ebs: Get:4 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB]
amazon-ebs: Get:5 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages [461 kB]
amazon-ebs: Get:6 http://security.ubuntu.com/ubuntu xenial-security/main Translation-en [199 kB]
amazon-ebs: Get:7 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages [322 kB]
amazon-ebs: Get:8 http://security.ubuntu.com/ubuntu xenial-security/universe Translation-en [121 kB]
amazon-ebs: Get:9 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 Packages [3,208 B]
amazon-ebs: Get:10 http://security.ubuntu.com/ubuntu xenial-security/multiverse Translation-en [1,408 B]
amazon-ebs: Get:11 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [739 kB]
amazon-ebs: Get:12 http://archive.ubuntu.com/ubuntu xenial-updates/main Translation-en [306 kB]
amazon-ebs: Get:13 http://archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 Packages [7,560 B]
amazon-ebs: Get:14 http://archive.ubuntu.com/ubuntu xenial-updates/restricted Translation-en [2,272 B]
amazon-ebs: Get:15 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [595 kB]
amazon-ebs: Get:16 http://archive.ubuntu.com/ubuntu xenial-updates/universe Translation-en [240 kB]
amazon-ebs: Get:17 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 Packages [16.2 kB]
amazon-ebs: Get:18 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse Translation-en [8,052 B]
amazon-ebs: Get:19 http://archive.ubuntu.com/ubuntu xenial-backports/main amd64 Packages [4,836 B]
amazon-ebs: Get:20 http://archive.ubuntu.com/ubuntu xenial-backports/main Translation-en [3,220 B]
amazon-ebs: Get:21 http://archive.ubuntu.com/ubuntu xenial-backports/universe amd64 Packages [6,624 B]
amazon-ebs: Get:22 http://archive.ubuntu.com/ubuntu xenial-backports/universe Translation-en [3,768 B]
amazon-ebs: Reading package lists...
amazon-ebs: E: can not open /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_xenial_InRelease - fopen (2: No such file or directory)
amazon-ebs: Failed to update package list
==> amazon-ebs: Terminating the source AWS instance...
==> amazon-ebs: Cleaning up any extra volumes...
==> amazon-ebs: No volumes to clean up, skipping
==> amazon-ebs: Deleting temporary security group...
==> amazon-ebs: Deleting temporary keypair...
Build 'amazon-ebs' errored: Script exited with non-zero exit status: 1
==> Some builds didn't complete successfully and had errors:
--> amazon-ebs: Script exited with non-zero exit status: 1
==> Builds finished but no artifacts were created.
Mostly AMI creation succeeds. However, the following failure has occasionally been seen.
It seems to be a random occurrence or at least I don't currently know of a way to cause it to occur.
There were no prior errors in the scripts.