Acking since needed with RHCS4.2z2
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!
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
*** Bug 1980202 has been marked as a duplicate of this bug. ***
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days