Skip to content
This repository was archived by the owner on Nov 25, 2024. It is now read-only.

Failure to copy an AMI causes Builderator to wait forever #70

Open
fmitchell-r7 opened this issue Apr 22, 2016 · 0 comments
Open

Failure to copy an AMI causes Builderator to wait forever #70

fmitchell-r7 opened this issue Apr 22, 2016 · 0 comments

Comments

@fmitchell-r7
Copy link
Contributor

If the AMI copy process fails, you see logs that look like this

16:57:43 Waiting for ami-XXXXXXXX in eu-central-1 to become Available
16:57:43 my-ami is still in the pending state, sleeping...
16:58:44 my-ami is still in the pending state, sleeping...
16:59:45 my-ami is still in the failed state, sleeping...
17:00:46 my-ami is still in the failed state, sleeping...

The "in the failed state" lines continue forever until the process is killed. It looks like the waiting state is true if the state returned from AWS is not "available".

The :wait task should exit (maybe throw an exception?) if the state returned from AWS is "failing".

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant