Bug #24172
client: fails to respond cap revoke from non-auth mds
% Done:
0%
Source:
Development
Tags:
Backport:
mimic,luminous
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Client
Labels (FS):
multimds
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Related issues
History
#1 Updated by Zheng Yan almost 6 years ago
#2 Updated by Zheng Yan almost 6 years ago
- Status changed from New to Fix Under Review
#3 Updated by Zheng Yan almost 6 years ago
- Related to Bug #23350: mds: deadlock during unlink and export added
#4 Updated by Zheng Yan almost 6 years ago
this can also explain http://tracker.ceph.com/issues/23350
#5 Updated by Patrick Donnelly almost 6 years ago
- Assignee set to Zheng Yan
- Priority changed from Normal to Urgent
- Target version set to v13.2.0
- Source set to Development
- Backport set to luminous
- Severity changed from 3 - minor to 2 - major
- Component(FS) Client added
#6 Updated by Nathan Cutler almost 6 years ago
- Backport changed from luminous to mimic, luminous
adding mimic backport because the PR targets master
#7 Updated by Patrick Donnelly almost 6 years ago
- Target version changed from v13.2.0 to v14.0.0
#8 Updated by Patrick Donnelly almost 6 years ago
- Subject changed from client fails to respond cap revoke from non-auth mds to client: fails to respond cap revoke from non-auth mds
- Status changed from Fix Under Review to Pending Backport
- Backport changed from mimic, luminous to mimic,luminous
- Labels (FS) multimds added
#9 Updated by Nathan Cutler almost 6 years ago
- Copied to Backport #24201: luminous: client: fails to respond cap revoke from non-auth mds added
#10 Updated by Nathan Cutler almost 6 years ago
- Copied to Backport #24202: mimic: client: fails to respond cap revoke from non-auth mds added
#11 Updated by Nathan Cutler almost 6 years ago
- Status changed from Pending Backport to Resolved