Closed Bug 1254422 Opened 4 years ago Closed 4 years ago

beetmover can't use set_canned_acl on candidate artifacts

Categories

(Release Engineering :: Release Automation: Other, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jlund, Unassigned)

References

Details

Attachments

(1 file)

this is because we have limited permissions in what we can do: https://bugzilla.mozilla.org/show_bug.cgi?id=1190309#c4

and we can't do things like: http://hg.mozilla.org/mozilla-central/file/be593a64d7c6/testing/mozharness/scripts/release/beet_mover.py#l286

this worked before with the testing beetmover buckets but not with net-mozaws-stage-delivery-firefox cloudops owned bucket.

example of failure: https://public-artifacts.taskcluster.net/Mu7BkAMkRpKDQC47DF_USQ/1/public/logs/live_backing.log
See Also: → 1253766
Comment on attachment 8727715 [details]
MozReview Request: Bug 1254422 - Do not try to set S3 ACLs r=jlund a=release

https://reviewboard.mozilla.org/r/38617/#review35271
Attachment #8727715 - Flags: review?(jlund) → review+
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.