Cherry pick fix for gsutil into '17-7-stable'
What does this MR do?
Merge branch '2135-error-when-using-backup-utility-with-gitlab-17-5-4' into 'master'
Resolve "Error when using backup-utility with GitLab 17.5.4"
Closes #2135 (closed)
See merge request !2147 (merged)
Merged-by: Jason Plum jplum@gitlab.com Approved-by: Hossein Pursultani hpursultani@gitlab.com Co-authored-by: João Cunha j.a.cunha@gmail.com
Related issues
Checklist
See Definition of done.
For anything in this list which will not be completed, please provide a reason in the MR discussion
Required
-
Merge Request Title, and Description are up to date, accurate, and descriptive -
MR targeting the appropriate branch -
MR has a green pipeline on GitLab.com -
When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow
Expected (please provide an explanation if not completing)
-
Test plan indicating conditions for success has been posted and passes -
Documentation created/updated -
Integration tests added to GitLab QA -
The impact any change in container size has should be evaluated -
New dependencies are managed with GitLab forked renovatebot
Merge request reports
Activity
assigned to @Alexand
added sectioninfrastructure platforms typebug labels
changed milestone to %17.8
changed milestone to %17.7
requested review from @WarheadsSE
1 Message Please add the workflowready for review label once you think the MR is ready to for an initial review, and assign
a reviewer based on the Reviewer Roulette suggestion below.If from a community member, ask that the Community contribution label be added as well.
Merge requests are handled according to the workflow documented in our handbook and should receive a response within the limit documented in our First-response SLO.
If you don't receive a response, please mention
@gitlab-org/distribution
, or one of our Project MaintainersReviewer roulette
Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category and by a maintainer in all other categories.
To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, mention them as you normally would! Danger does not automatically notify them for you.
Reviewer Maintainer @deriamis
(UTC-8, 8 hours behind author)
@balasankarc
(UTC+5.5, 5.5 hours ahead of author)
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Dangermarked the checklist item When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow as completed
mentioned in commit fc87be34