Sitelet https://web.archive.org/web/20200821124735/https://github.com/aws/aws-controllers-k8s/issues/188
Skip to content

/ aws-controllers-k8s

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

Jump to bottom

Handle S3 OperationAborted due to conflicting conditions #188

Open
jaypipes opened this issue Aug 17, 2020 · 1 comment
Open

Handle S3 OperationAborted due to conflicting conditions #188

jaypipes opened this issue Aug 17, 2020 · 1 comment
Labels
S3 bug good first issue

Comments

@jaypipes
Copy link
Contributor

@jaypipes jaypipes commented Aug 17, 2020

If you attempt to create a Bucket with the same name as a Bucket that you recently deleted, you might run into this:

OperationAborted: A conflicting conditional operation is currently in progress against this resource.

This is due to S3 queuing the delete operation and the need to have a unique name of the bucket for the account. Attempting to create the Bucket with the same name violates the uniqueness constraint for the still-being-deleted previous Bucket.

We should properly handle this error and trigger a delay in the Retry operation in the reconciler.
@jaypipes
Copy link
Contributor Author

@jaypipes jaypipes commented Aug 17, 2020

The solution here is twofold:

  • Add some logic into the ExceptionsConfig struct in the generatorConfig to indicate certain error codes should be caught and simply cause a delayed retry of the original request.
  • Change the template in crd_sdk.go.tpl to handle these kinds of exceptions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
S3 bug good first issue
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
@jaypipes
You can’t perform that action at this time.