Chapter 4. Known issues

In AWS environment, after a node reboot, the *-mon-* pods are stuck in the init state for an extended period. Should this occur, contact Red Hat support. (BZ#1769322)
It is not possible to uninstall Red Hat OpenShift Container Storage from the user interface. (BZ#1760426)
Persistent Volume Claim (PVC) expansion is not functional. (BZ#1743643)
Noobaa-core-0 does not migrate to other nodes when a node goes down. NooBaa will not work when a node is down as migration of noobaa-core pod is blocked. (BZ#1783961)
When a worker node is down, the operator is blocked from responding to Custom Resource (CR) updates such as upgrades, adding storage, or creating new pools. (BZ#1778488)
To resolve this issue, see Replacing storage nodes for OpenShift Container Storage.
The reported size by OpenShift Container Platform for a node which is slightly less than the actual size (64 GiB free memory) results in a validation failure. For example, AWS M5.4xlarge machine has 16 core and 64 Gib memory of RAM but memory size reported by OpenShift node API is 61.xx GiB. Hence, an unexpected warning message is displayed for the expected configuration. (BZ#1823444)
To resolve this, you are requested to ignore this warning message for OpenShift Container Platform and OpenShift Container Storage 4.3 release as this issue will be fixed in the future releases.