Bug #36635
closed
mds: purge queue corruption from wrong backport
Added by Patrick Donnelly over 5 years ago.
Updated about 4 years ago.
Description
Master version of #36346. We need to add the special handling for the wrong purge queue format in 13.2.2.
- Copied from Bug #36346: mimic: mds: purge queue corruption from wrong backport added
- Target version changed from v14.0.0 to v15.0.0
I think we can just add an upgrade note to Octopus to not upgrade from 13.2.2.
- Assignee changed from Zheng Yan to Patrick Donnelly
- Tracker changed from Bug to Documentation
- Subject changed from mds: purge queue corruption from wrong backport to doc: purge queue corruption from wrong backport
- Status changed from New to In Progress
- Tracker changed from Documentation to Bug
- Subject changed from doc: purge queue corruption from wrong backport to mds: purge queue corruption from wrong backport
- Status changed from In Progress to Fix Under Review
- Backport set to nautilus
- Regression set to No
- Severity set to 3 - minor
- Pull request ID set to 33449
- Component(FS) MDS added
- Status changed from Fix Under Review to Pending Backport
- Copied to Backport #44337: nautilus: mds: purge queue corruption from wrong backport added
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Also available in: Atom
PDF