Better support for "UPDATE_IN_PROGRESS"

Open mwildehahn opened this issue 9 years ago • 1 comments

i get this when developing if i start and stop empire:

$ ./build/emp deploy remind101/acme-inc:master -s
master: Pulling from remind101/acme-inc

420890c9e918: Already exists
a3ed95caeb02: Already exists
1e14aab0083d: Already exists
4393485f2bb3: Already exists
ecb5197aa37c: Already exists
3d14045f20ce: Already exists
Digest: sha256:657db53195f384625bbd9b729d269c3eb082084825886a0befabdf44e663fc2b
Status: Image is up to date for remind101/acme-inc:master
Status: Created new release v22 for acme-inc
Status: Created cloudformation template: https://empire-0b96756d-templatebucket-fzr5jqii49z4.s3.amazonaws.com/acme-inc/04a75f65-c7c4-4e36-943b-0a09614db1b4/8c0473a6d5316204b03c716ac17b2a3beaa48c1f
error: error updating stack: ValidationError: Stack:arn:aws:cloudformation:us-east-1:935008130000:stack/acme-inc/94bc8530-4882-11e6-8e9c-500c286e1a36 is in UPDATE_IN_PROGRESS state and can not be updated.
    status code: 400, request id: 92253188-4a0d-11e6-b7ce-e77dad8c1b5a

maybe this is just an error on dev because the lock gets cleared when you stop/start empire?

Jul 14 '16 21:07 mwildehahn

Yeah, this will happen if you restart Empire while it's deploying something, since the stack operation lock will be released when the postgres connection drops.

Jul 14 '16 22:07 ejholmes