Skip to content
This repository has been archived by the owner on May 31, 2024. It is now read-only.

Some deleted buckets affects as runtime error #3

Open
aibou opened this issue Oct 2, 2018 · 1 comment · May be fixed by #4
Open

Some deleted buckets affects as runtime error #3

aibou opened this issue Oct 2, 2018 · 1 comment · May be fixed by #4

Comments

@aibou
Copy link

aibou commented Oct 2, 2018

AWS S3 adopts Eventual Consistency. So sometimes we face such a situation when we delete a S3 bucket:

$ aws s3 ls | grep [deleted bucket name]
2018-10-02 16:25:04 [deleted bucket name]

$ aws s3 ls s3://[deleted bucket name]
An error occurred (NoSuchBucket) when calling the ListObjects operation: The specified bucket does not exist

In this situation, bukelatta occurs an error not only apply phase but also dry-run phase:

[ERROR] The specified bucket does not exist

We should treat this case.
aibou added a commit to aibou/bukelatta that referenced this issue Oct 29, 2018
@aibou
Check the buckets exists codenize-tools#3
1810b2a
@aibou aibou linked a pull request Oct 29, 2018 that will close this issue
Open
@aibou
Copy link
Author

aibou commented Oct 29, 2018

If you face this problem, you may execute after a while (about 3 ~ 4 hours).
You can execute bukelatta when this command outputs nothing:

$ aws s3 ls | grep [deleted bucket name]

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Check the buckets exists #3 aibou/bukelatta
1 participant
@aibou