Bug 2273398

Summary:	[GSS][ODF 4.16 backport] Legacy LVM-based OSDs are in crashloop state
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Manjunatha <mmanjuna>
Component:	rook	Assignee:	Travis Nielsen <tnielsen>
Status:	CLOSED ERRATA	QA Contact:	Vishakha Kathole <vkathole>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.14	CC:	ableisch, asriram, bkunal, bniver, gabrioux, gsternag, hnallurv, kbg, kelwhite, mcaldeir, muagarwa, nojha, odf-bz-bot, pdhange, rafrojas, roemerso, sostapov, tdesala, tnielsen, vumrao
Target Milestone:	---	Flags:	ableisch: needinfo-
Target Release:	ODF 4.16.0
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	4.16.0-89	Doc Type:	Bug Fix
Doc Text:	.Legacy LVM-based OSDs are in crashloop state Previously, starting from OpenShift Data Foundation 4.14, the legacy OSDs were crashing in the init container that resized the OSD. This was because, the legacy OSDs that were created in OpenShift Container Storage 4.3 and since upgraded to a future version might have failed. With this fix, the crashing resize init container was removed from the OSD pod spec. As a result, the legacy OSD starts, however it is recommended that the legacy OSDs re replaced soon.	Story Points:	---
Clone Of:
Clones:	2274657 2274757 2276532 2276533 (view as bug list)		Environment:
Last Closed:	2024-07-17 13:18:04 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:
Bug Blocks:	2260844, 2274657, 2274757, 2276532, 2276533, 2279928

Description Manjunatha 2024-04-04 15:13:50 UTC

Description of problem (please be detailed as possible and provide log
snippests):

Customer upgraded from 4.12.47 to 4.14.16 we have noticed that all OSDs are in crahs loop with the expand-bluefs container showing errors about devices that can not be found.



Version of all relevant components (if applicable):
ODF 4.14.6

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Yes, all osds are down 

Is there any workaround available to the best of your knowledge?
No


Can this issue reproducible?
yes, at customer environment

Comment 18 kelwhite 2024-04-05 13:52:56 UTC

Hello,

@bkunal found the KCS https://access.redhat.com/solutions/7026462 I'm going to confirm this is the same for this case. Will post findings when I have any.

Comment 46 Vishakha Kathole 2024-06-04 11:47:14 UTC

Moving to the verified state based on the 4.16 CI regression runs.

Comment 48 errata-xmlrpc 2024-07-17 13:18:04 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 (Important: Red Hat OpenShift Data Foundation 4.16.0 security, enhancement & bug fix update), 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/RHSA-2024:4591

Comment 49 Red Hat Bugzilla 2024-11-15 04:25:29 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days