Actions
Bug #7511
closed"set noup; set down <n>; unset noup" doesn't bring <n> back up
Status:
Resolved
Priority:
Immediate
Assignee:
-
Category:
OSD
Target version:
-
% Done:
0%
Source:
Development
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Experiment:
ceph osd set noup
ceph osd down 1
<osd 1 is down>
ceph osd unset noup
Expected:
<osd 1 is back up>
Observed:
<osd 1 stays down>
Sage theorizes that the OSD should notice, when it tries to come back, that noup is set, and subscribe an event from the monitor to notice new maps, so that it sees the
"unset noup" and tries to come back again. (or words to that effect)
Actions