storage uniform bucket-level access preserves bucket/file ACL over uniform bucket-level access on/off: should preserve file ACL failed

[flaky-bot]

This test failed!

To configure my behavior, see the Flaky Bot documentation.

If I'm commenting on this issue too often, add the flakybot: quiet label and
I will stop commenting.

---

commit: 91fe5ed
buildURL: Build Status, Sponge
status: failed

Test output

Cannot get legacy ACL for an object when uniform bucket-level access is enabled. Read more at https://cloud.google.com/storage/docs/uniform-bucket-level-access
Error: Cannot get legacy ACL for an object when uniform bucket-level access is enabled. Read more at https://cloud.google.com/storage/docs/uniform-bucket-level-access
    at new ApiError (build/src/nodejs-common/util.js:76:15)
        -> /workspace/src/nodejs-common/util.ts:262:11
    at Util.parseHttpRespBody (build/src/nodejs-common/util.js:211:38)
        -> /workspace/src/nodejs-common/util.ts:463:32
    at Util.handleResp (build/src/nodejs-common/util.js:152:117)
        -> /workspace/src/nodejs-common/util.ts:396:20
    at /workspace/build/src/nodejs-common/util.js:496:22
        -> /workspace/src/nodejs-common/util.ts:826:16
    at onResponse (node_modules/retry-request/index.js:228:7)
    at /workspace/node_modules/teeny-request/build/src/index.js:226:13
        -> /workspace/node_modules/teeny-request/src/index.ts:333:11
    at runMicrotasks ()
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

[flaky-bot]

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

Test output

Cannot get legacy ACL for an object when uniform bucket-level access is enabled. Read more at https://cloud.google.com/storage/docs/uniform-bucket-level-access
Error: Cannot get legacy ACL for an object when uniform bucket-level access is enabled. Read more at https://cloud.google.com/storage/docs/uniform-bucket-level-access
    at new ApiError (build/src/nodejs-common/util.js:76:15)
        -> /workspace/src/nodejs-common/util.ts:262:11
    at Util.parseHttpRespBody (build/src/nodejs-common/util.js:211:38)
        -> /workspace/src/nodejs-common/util.ts:463:32
    at Util.handleResp (build/src/nodejs-common/util.js:152:117)
        -> /workspace/src/nodejs-common/util.ts:396:20
    at /workspace/build/src/nodejs-common/util.js:496:22
        -> /workspace/src/nodejs-common/util.ts:826:16
    at onResponse (node_modules/retry-request/index.js:228:7)
    at /workspace/node_modules/teeny-request/build/src/index.js:226:13
        -> /workspace/node_modules/teeny-request/src/index.ts:333:11
    at runMicrotasks ()
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

[flaky-bot]

Test passed for commit 66d5b57 (Build Status, Sponge)! Closing this issue.

[flaky-bot]

Looks like this issue is flaky. 😟

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

A human should fix and close this.

---

commit: 638a47b
buildURL: Build Status, Sponge
status: failed

Test output

Cannot get legacy ACL for an object when uniform bucket-level access is enabled. Read more at https://cloud.google.com/storage/docs/uniform-bucket-level-access
Error: Cannot get legacy ACL for an object when uniform bucket-level access is enabled. Read more at https://cloud.google.com/storage/docs/uniform-bucket-level-access
    at new ApiError (build/src/nodejs-common/util.js:76:15)
        -> /workspace/src/nodejs-common/util.ts:262:11
    at Util.parseHttpRespBody (build/src/nodejs-common/util.js:211:38)
        -> /workspace/src/nodejs-common/util.ts:463:32
    at Util.handleResp (build/src/nodejs-common/util.js:152:117)
        -> /workspace/src/nodejs-common/util.ts:396:20
    at /workspace/build/src/nodejs-common/util.js:496:22
        -> /workspace/src/nodejs-common/util.ts:826:16
    at onResponse (node_modules/retry-request/index.js:228:7)
    at /workspace/node_modules/teeny-request/build/src/index.js:226:13
        -> /workspace/node_modules/teeny-request/src/index.ts:333:11
    at runMicrotasks ()
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

[ddelgrosso1]

I made a fix that should resolve this issue. The issue appears to be caused by a failed resumable upload that then caches an old URL without the added query params. In order to alleviate the issue I made the file names more unique. I am going to close this issue. If it resurfaces I will add the additional step of manually clearing the cache between tests that utilize resumable uploads.