Bug #49157
mon/MDSMonitor.cc: fix join fscid not applied with pending fsmap at boot
% Done:
0%
Source:
Community (dev)
Tags:
Backport:
pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
MDSMonitor
Labels (FS):
multifs
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
At boot stage, mds new_info.join_fscid is set after new_info is added to pending fsmap. Hence join_fscid will be updated at next beacon.
Related issues
History
#1 Updated by Zhi Zhang almost 3 years ago
- Pull request ID set to 39287
#2 Updated by Douglas Fuller almost 3 years ago
- Assignee set to Venky Shankar
#3 Updated by Venky Shankar almost 3 years ago
- Status changed from New to Resolved
- Backport set to pacific
#4 Updated by Patrick Donnelly over 2 years ago
- Status changed from Resolved to Pending Backport
#5 Updated by Backport Bot over 2 years ago
- Copied to Backport #52036: pacific: mon/MDSMonitor.cc: fix join fscid not applied with pending fsmap at boot added
#6 Updated by Loïc Dachary over 2 years ago
- 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".