Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1792122

Summary:	[Container] : bluestore OSD upgraded from 3.x to 4.x : ceph-disk to ceph-volume migrated : flapping after node reboot : unable to activate bluestore OSD
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Vasishta <vashastr>
Component:	Container	Assignee:	Dimitri Savineau <dsavinea>
Status:	CLOSED ERRATA	QA Contact:	Gopi <gpatta>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.0	CC:	aschoen, bniver, ceph-eng-bugs, ceph-qe-bugs, dsavinea, gabrioux, gmeno, kdreyer, nthomas, tchandra
Target Milestone:	rc	Keywords:	Regression
Target Release:	4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhceph:ceph-4.0-rhel-8-containers-candidate-95735-20200121151520	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-01-31 14:44:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1794900
Bug Blocks:

Description Vasishta 2020-01-17 05:32:36 UTC

Description of problem:
After upgrading conainerized cluster from 3.x to 4.x, rebooted a node 
OSD services started flapping saying RuntimeError: Unable to activate bluestore OSD due to missing devices

Version-Release number of selected component (if applicable):
registry-proxy.engineering.redhat.com/rh-osbs/rhceph:ceph-4.0-rhel-8-containers-candidate-29205-20200117023445
ceph-ansible-4.0.10-1.el7cp.noarch

How reproducible:
Always (1/1)

Steps to Reproduce:
1. Configure 3.x cluster with bluestore OSDs
2. Upgrade cluster to 4.x
3. reboot an OSD node

Actual results:
OSDs are not coming up after node reboot


Expected results:
OSDs should be up and running after node reboot

Additional info:
OSD was configure in 3.x - 
magna048 osd_auto_discovery=true osd_objectstore=bluestore dmcrypt=true osd_scenario=collocated

Was confused about the component, please change the component to appropriate one if it is not.

Comment 8 errata-xmlrpc 2020-01-31 14:44:57 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0313