Backport #22574
closedluminous: Random 500 errors in Swift PutObject
Updated by Nathan Cutler over 6 years ago
- Copied from Bug #22517: Cache never becoming consistent after failed updates added
Updated by Nathan Cutler over 6 years ago
- Description updated (diff)
- Status changed from New to In Progress
- Assignee set to Nathan Cutler
Updated by Adam Emerson over 6 years ago
I have
https://github.com/ceph/ceph/pull/19788
(Sorry for not opening up a backport before writing this, I havn'et done them before and I'm still getting used to the tracker workflow.)
Updated by Nathan Cutler over 6 years ago
- Description updated (diff)
- Assignee changed from Nathan Cutler to Adam Emerson
Updated by Adam Emerson over 6 years ago
- Status changed from In Progress to Fix Under Review
Updated by Nathan Cutler over 6 years ago
@Adam DC949 It's not a big deal, but in the past we have dispensed with the "Need Review" status for backports. The workflow for backport PRs is different than for master PRs. In a nutshell:
1. backport PR opened (backport tracker status changes from "New" to "In Progress")
2. backport PR passes integration testing (noted in PR; lead pinged in PR)
3. lead reviews/approves PR
4. PR merged (backport tracker status changes from "In Progress" to "Resolved" and target version gets set)
5. if all backports are resolved, the master tracker issue status changes from "Pending Backport" to "Resolved"
HTH
Nathan
Updated by Yuri Weinstein over 6 years ago
Updated by Nathan Cutler over 6 years ago
- Status changed from Fix Under Review to Resolved
- Target version set to v12.2.3