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

storage: TestIntegration_UpdateRetentionPolicy failed #9683

Closed
flaky-bot bot opened this issue Apr 2, 2024 · 3 comments · Fixed by #10515
Closed

storage: TestIntegration_UpdateRetentionPolicy failed #9683

flaky-bot bot opened this issue Apr 2, 2024 · 3 comments · Fixed by #10515
Assignees
Labels
api: storage Issues related to the Cloud Storage API. flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@flaky-bot
Copy link

flaky-bot bot commented Apr 2, 2024

Note: #8137 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.


commit: e7342a3
buildURL: Build Status, Sponge
status: failed

@flaky-bot flaky-bot bot added flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Apr 2, 2024
@product-auto-label product-auto-label bot added the api: storage Issues related to the Cloud Storage API. label Apr 2, 2024
@flaky-bot flaky-bot bot added the flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. label Apr 2, 2024
Copy link
Author

flaky-bot bot commented Apr 2, 2024

Looks like this issue is flaky. 😟

I'm going to leave this open and stop commenting.

A human should fix and close this.


When run at the same commit (e7342a3), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

@BrennaEpp
Copy link
Contributor

=== RUN   TestIntegration_UpdateRetentionExpirationTime/http
    integration_test.go:3839: object delete: googleapi: Error 403: Object 'go-integration-test-1712015437129794831-61/some-obj' is subject to bucket's retention policy or object retention and cannot be deleted or overwritten until 2024-04-01T17:55:34.632831-07:00, retentionPolicyNotMet
    integration_test.go:3839: bucket delete: googleapi: Error 409: The bucket you tried to delete is not empty., conflict

May be a metadata update delay issue.

@BrennaEpp BrennaEpp added priority: p2 Moderately-important priority. Fix may not be included in next release. and removed priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. labels Apr 10, 2024
@BrennaEpp
Copy link
Contributor

BrennaEpp commented Jul 6, 2024

Sorry, that was wrong (those are logs so ultimately that test is passing, but it probably does have that metadata update issue. We may want to think about doing an assessment of tests to determine which are consistently leaving buckets/objects not cleaned up, and how much time we are spending waiting for metadata updates to clean up objects/buckets.

This is the actual failure:

=== RUN   TestIntegration_UpdateRetentionPolicy/http/remove
    integration_test.go:3946: bucket delete: googleapi: Error 404: The specified bucket does not exist., notFound

May be a retry since the operation is idempotent. I'll open a fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: storage Issues related to the Cloud Storage API. flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants