storage: TestIntegration_RequesterPaysNonOwner failed

[flaky-bot[bot]]

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

---

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

[flaky-bot[bot]]

Looks like this issue is flaky. :worried:

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

A human should fix and close this.

---

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

[tritone]

integration_test.go:3345: delete object: got unexpected error:rpc error: code = PermissionDenied desc = [email protected] does not have storage.objects.delete access to the Google Cloud Storage object. Permission 'storage.objects.delete' denied on resource (or it may not exist)

Looks like this is one case with the secondary project on this test, but only delete failed and all other ops succeeded seemingly.

[BrennaEpp]

So I think one possibility here is that the ACL propagation is uneven; it can take several minutes for ACLs to be fully propagated, so particularly newly created objects may have the old ACLs for a bit or in some areas. Next steps are to change the test to set the ACLs on bucket creation, and/or just add a retry to the operations