Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provision errors #2

Open
beyang opened this issue Aug 4, 2016 · 4 comments
Open

Provision errors #2

beyang opened this issue Aug 4, 2016 · 4 comments

Comments

@beyang
Copy link
Member

beyang commented Aug 4, 2016

I get the following error when going through the install instructions.

$ checkup provision
One sec...
2016/08/04 00:51:50 OperationAborted: A conflicting conditional operation is currently in progress against this resource. Please try again.
        status code: 409, request id: 6AD8BED083CC9A5A

I was trying to use an existing S3 bucket and initially got an error saying that the bucket already existed. I then deleted the bucket and the IAM user that checkup creates, and when I try to re-run provision, I get the above error. (Also, ideally checkup provision would proceed with subsequent steps in the provisioning if the user already exists.)

I can work around this by just manually provisioning the bucket and using the created user, so not super urgent.

@mholt
Copy link
Collaborator

mholt commented Aug 5, 2016

Weird, I deleted the bucket and user multiple times in testing and never encountered that error. Did you wait 1-2 seconds before running it? Maybe their system was still in the process of deleting the bucket or user...

(Also, ideally checkup provision would proceed with subsequent steps in the provisioning if the user already exists.)

Yeah, it probably would be better this way.

@indistinctTalk
Copy link

@beyang I suspect this is just AWS taking time to delete the S3 bucket (as @mholt suggested) and that you tried to recreate the bucket too quickly after deleting it. You can see other people having the issue here. See especially the comments about it taking up to 1 - 1.5 hours before they could recreate the bucket.

@mholt
Copy link
Collaborator

mholt commented Aug 11, 2016

I'm also not sure how to assert that the error is one of "user already exists" as opposed to something else -- at least not without a separate API request.

@indistinctTalk
Copy link

@mholt I think the http error response might work? They have a few different error responses anyway. Below taken from the AWS IAM docs.

EntityAlreadyExists
The request was rejected because it attempted to create a resource that already exists.
HTTP Status Code: 409

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

No branches or pull requests

3 participants