{"action":"created","issue":{"url":"https://api.github.com/repos/mitchellh/packer/issues/1539","labels_url":"https://api.github.com/repos/mitchellh/packer/issues/1539/labels{/name}","comments_url":"https://api.github.com/repos/mitchellh/packer/issues/1539/comments","events_url":"https://api.github.com/repos/mitchellh/packer/issues/1539/events","html_url":"https://github.com/mitchellh/packer/issues/1539","id":44186644,"number":1539,"title":"Failures due to recoverable AWS errors have returned","user":{"login":"patricklucas","id":95053,"avatar_url":"https://avatars.githubusercontent.com/u/95053?v=3","gravatar_id":"","url":"https://api.github.com/users/patricklucas","html_url":"https://github.com/patricklucas","followers_url":"https://api.github.com/users/patricklucas/followers","following_url":"https://api.github.com/users/patricklucas/following{/other_user}","gists_url":"https://api.github.com/users/patricklucas/gists{/gist_id}","starred_url":"https://api.github.com/users/patricklucas/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/patricklucas/subscriptions","organizations_url":"https://api.github.com/users/patricklucas/orgs","repos_url":"https://api.github.com/users/patricklucas/repos","events_url":"https://api.github.com/users/patricklucas/events{/privacy}","received_events_url":"https://api.github.com/users/patricklucas/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/mitchellh/packer/labels/bug","name":"bug","color":"fc2929"},{"url":"https://api.github.com/repos/mitchellh/packer/labels/builder/amazon","name":"builder/amazon","color":"d4c5f9"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":32,"created_at":"2014-09-27T19:09:20Z","updated_at":"2015-03-06T19:19:47Z","closed_at":null,"body":"Most of these were fixed up last fall after I opened #574 and #668, but a number of these transient AWS errors have returned, causing a steady stream of builds to fail.\r\n\r\nFor example, we are again seeing Packer fail after it can't find the instance immediately after launch:\r\n\r\n```\r\n11:59:39 ==> amazon-ebs: Inspecting the source AMI...\r\n11:59:39 ==> amazon-ebs: Creating temporary keypair: packer 5427091b-3a8e-abeb-57d8-2c6d0793a9b6\r\n11:59:40 ==> amazon-ebs: Launching a source AWS instance...\r\n11:59:41 ==> amazon-ebs: Error finding source instance (i-d2dd6518): The instance ID 'i-d2dd6518' does not exist (InvalidInstanceID.NotFound)\r\n11:59:41 ==> amazon-ebs: Deleting temporary keypair...\r\n11:59:41 Build 'amazon-ebs' errored: Error finding source instance (i-d2dd6518): The instance ID 'i-d2dd6518' does not exist (InvalidInstanceID.NotFound)\r\n```\r\n\r\nThat one is the most frequent, but we also occasionally see IO timeouts as well:\r\n\r\n```\r\n10:46:57 ==> amazon-ebs: Stopping the source instance...\r\n10:46:59 ==> amazon-ebs: Waiting for the instance to stop...\r\n10:47:30 ==> amazon-ebs: Creating the AMI: generictrusty-ami_1219\r\n10:47:30     amazon-ebs: AMI: ami-c38f8786\r\n10:47:30 ==> amazon-ebs: Waiting for AMI to become ready...\r\n10:49:13 ==> amazon-ebs: Error waiting for AMI: read tcp 204.246.163.231:443: i/o timeout\r\n10:49:13 ==> amazon-ebs: Terminating the source AWS instance...\r\n10:49:14 ==> amazon-ebs: Deleting temporary keypair...\r\n10:49:14 Build 'amazon-ebs' errored: Error waiting for AMI: read tcp 204.246.163.231:443: i/o timeout\r\n```\r\n\r\nIIRC, these all _used_ to be covered by retries, so perhaps it is a regression."},"comment":{"url":"https://api.github.com/repos/mitchellh/packer/issues/comments/77618620","html_url":"https://github.com/mitchellh/packer/issues/1539#issuecomment-77618620","issue_url":"https://api.github.com/repos/mitchellh/packer/issues/1539","id":77618620,"user":{"login":"jantman","id":273454,"avatar_url":"https://avatars.githubusercontent.com/u/273454?v=3","gravatar_id":"","url":"https://api.github.com/users/jantman","html_url":"https://github.com/jantman","followers_url":"https://api.github.com/users/jantman/followers","following_url":"https://api.github.com/users/jantman/following{/other_user}","gists_url":"https://api.github.com/users/jantman/gists{/gist_id}","starred_url":"https://api.github.com/users/jantman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jantman/subscriptions","organizations_url":"https://api.github.com/users/jantman/orgs","repos_url":"https://api.github.com/users/jantman/repos","events_url":"https://api.github.com/users/jantman/events{/privacy}","received_events_url":"https://api.github.com/users/jantman/received_events","type":"User","site_admin":false},"created_at":"2015-03-06T19:19:47Z","updated_at":"2015-03-06T19:19:47Z","body":"I just got bitten by this too. I'm not sure I'd say this \"isn't a packer problem\" - it's certainly an issue with either Packer or the underlying library it uses. For better or worse, yeah, 503s aren't uncommon from AWS. It's up to the tool to perform a retry (ideally with exponential backoff) before throwing an error."}}