Bug #20631
OSD needs restart after upgrade to luminous IF upgraded before a luminous quorum
Status:
Resolved
Priority:
Immediate
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Community (dev)
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
OSD
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
If an OSD is upgraded to luminous before the monmap has the luminous feature, it will require to be restarted before it will boot into a full luminous quorum.
Tested against 9b3c2084799d011e066f7772f5381d772bf2925a.
Reproducing this is fairly straightforward. Starting with a kraken vstart cluster:
- restart osd.0 / upgrade to luminous
- restart all monitors / upgrade to luminous
- wait for osd.0 to finally boot (it really doesn't)
- restart osd.0 and see it boot up
History
#1 Updated by Sage Weil over 6 years ago
- Status changed from New to Fix Under Review
#2 Updated by Joao Eduardo Luis over 6 years ago
- File 2017-07-14-osd.0.log View added
#3 Updated by Sage Weil over 6 years ago
- Status changed from Fix Under Review to 7
#4 Updated by Sage Weil over 6 years ago
- Status changed from 7 to Resolved