Project

General

Profile

Bug #20631

OSD needs restart after upgrade to luminous IF upgraded before a luminous quorum

Added by Joao Eduardo Luis over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Immediate
Assignee:
-
Category:
-
Target version:
-
Start date:
07/14/2017
Due date:
% Done:

0%

Source:
Community (dev)
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
OSD
Pull request ID:

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

2017-07-14-osd.0.log View - osd FAILED assert(m_workers.empty()) (930 KB) Joao Eduardo Luis, 07/14/2017 03:35 PM

History

#1 Updated by Sage Weil over 1 year ago

  • Status changed from New to Need Review

#3 Updated by Sage Weil over 1 year ago

  • Status changed from Need Review to Testing

#4 Updated by Sage Weil over 1 year ago

  • Status changed from Testing to Resolved

Also available in: Atom PDF