Bug 1974476

Summary: OCS CI deployment failing because of Ceph health warning for insecure global_id reclaims
Product: [Red Hat Storage] Red Hat OpenShift Container Storage Reporter: Zack Cerza <zcerza>
Component: rookAssignee: Travis Nielsen <tnielsen>
Status: CLOSED ERRATA QA Contact: Elad <ebenahar>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.6CC: madam, mputhenp, muagarwa, nberry, ocs-bugs, owasserm, tnielsen
Target Milestone: ---Keywords: AutomationBackLog, ZStream
Target Release: OCS 4.6.6Flags: tnielsen: needinfo? (nberry)
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.6.6-426.ci Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 1970348 Environment:
Last Closed: 2021-07-07 18:53:00 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: 1970348, 1974477    
Bug Blocks:    

Comment 4 Travis Nielsen 2021-06-21 19:29:57 UTC
Acking since needed with RHCS4.2z2

Comment 8 Travis Nielsen 2021-06-23 18:50:19 UTC
A scenario to watch for is that during upgrade from a previous build (not running RHCS4.2z2). After the upgrade is done, Rook will disable the insecure global IDs, which will deny the pre-upgraded clients from connecting. If there is any client not upgraded yet (e.g. the toolbox), it will be immediately denied access to connect to the cluster after Rook disables the insecure global IDs. I expect the disabling to only happen after the Rook upgrade is fully completed, but please do verify the upgrade scenario if you didn't already. Thanks!

Comment 16 errata-xmlrpc 2021-07-07 18:53:00 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.6.6 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-2021:2669

Comment 17 Mudit Agarwal 2021-07-08 06:00:41 UTC
*** Bug 1980202 has been marked as a duplicate of this bug. ***