Bug 2273398 - [GSS][ODF 4.16 backport] Legacy LVM-based OSDs are in crashloop state
Summary: [GSS][ODF 4.16 backport] Legacy LVM-based OSDs are in crashloop state
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: rook
Version: 4.14
Hardware: All
OS: All
urgent
urgent
Target Milestone: ---
: ODF 4.16.0
Assignee: Travis Nielsen
QA Contact: Vishakha Kathole
URL:
Whiteboard:
Depends On:
Blocks: 2260844 2274657 2274757 2276532 2276533 2279928
TreeView+ depends on / blocked
 
Reported: 2024-04-04 15:13 UTC by Manjunatha
Modified: 2024-11-15 04:25 UTC (History)
20 users (show)

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.
Clone Of:
: 2274657 2274757 2276532 2276533 (view as bug list)
Environment:
Last Closed: 2024-07-17 13:18:04 UTC
Embargoed:
ableisch: needinfo-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage rook pull 632 0 None open Bug 2273398: osd: Legacy osds on lvm pvcs crash on resize init container 2024-04-22 21:44:03 UTC
Github rook rook pull 14100 0 None open osd: Legacy LVM-based OSDs on PVCs crash on resize init container 2024-04-19 22:21:58 UTC
Red Hat Bugzilla 2273724 0 urgent CLOSED ceph-volume raw list and activate fail 2024-05-15 04:54:10 UTC
Red Hat Knowledge Base (Solution) 7063703 0 None None None 2024-04-23 16:30:59 UTC
Red Hat Product Errata RHSA-2024:4591 0 None None None 2024-07-17 13:19:04 UTC

Internal Links: 2273724

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
Note You need to log in before you can comment on or make changes to this bug.