Bug 2034359

Summary: [4.8.z clone] After a node restart, the RGW pod is stuck in a CrashLoopBackOff state
Product: [Red Hat Storage] Red Hat OpenShift Container Storage Reporter: Blaine Gardner <brgardne>
Component: rookAssignee: Blaine Gardner <brgardne>
Status: CLOSED ERRATA QA Contact: Elad <ebenahar>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.8CC: belimele, bniver, brgardne, ebenahar, jthottan, kramdoss, madam, mbenjamin, mkogan, muagarwa, ocs-bugs, sheggodu, sostapov, tnielsen
Target Milestone: ---Keywords: Regression, ZStream
Target Release: OCS 4.8.7   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 2032404 Environment:
Last Closed: 2022-01-17 15:07:11 UTC Type: ---
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: 2032404    
Bug Blocks:    

Comment 1 Blaine Gardner 2021-12-20 18:53:33 UTC 
Backport to 4.8.z: https://github.com/red-hat-storage/rook/pull/319
Comment 15 errata-xmlrpc 2022-01-17 15:07:11 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 (Red Hat OpenShift Container Storage 4.8.7 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/RHBA-2022:0148