Bug 2139438

Description of problem (please be detailed as possible and provide log
snippests):
Unable to create PVs with local storage operator.

Version of all relevant components (if applicable):
4.11.9

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
yes

Is there any workaround available to the best of your knowledge?
Creating Pv's via web console

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?
yes

Can this issue reproduce from the UI?
yes

If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Issue1: Unable to create PVs with local storage operator.

We are trying to create PV's for local-data, metadata, wal, mon-pods. we tried creating local-data and mon-pod PVs via the yaml file. Though there was no error on applying the yaml file, the PVs were not getting created so, we created manually via ‘Create PersistentVolume’ option in web console(yaml view option) and PVs got created using nfs yaml template (https://docs.openshift.com/container-platform/4.11/storage/persistent_storage/persistent-storage-nfs.html)
However local-metadata and local-wal PVs got created by applying the corresponding yaml files.

2. Issue2: Unable to create PV's via local volume option from web console

We have followed this link https://docs.openshift.com/container-platform/4.11/storage/persistent_storage/persistent-storage-local.html to create PV's  using "persistent storage using local volumes" method.
Pv's are not getting created when we tried creating Pv's from the web console create persistent volume option.
we see the local-data listing in the webconsole. But, it is not getting listed under oc get pv -n openshift-storage.

3. Issue3: Unable to mount PV's when created via NFS option from web console

1. We are creating the PV's via webconsole from create persistent volume option.
2. In the default yaml format, we updated the device path, nfs server IP (172.17.0.2) remains the same. 
3. On clicking the create button, the Pv's are created.
4. Installed the odf operator and created the storage cluster via the cli by applying yaml file.
5. Oc get pods list the pods related to the mon-pods are in Init state.
6. Oc describe mon pod shows the below error:
Mounting arguments: -t nfs 172.17.0.2:/dev/disk/by-id/nvme-eui.01000000010000005cd2e4fdd9675351 /var/lib/kubelet/pods/f5096fb4-7225-46bd-8806-6204704ed908/volumes/kubernetes.io~nfs/mon-pods1
Output: mount.nfs: Connection timed out 
7. We are unable to get the ceph health when the pods are in this state.

We already have created support cases for these 3 issues.
Issue-1 : https://access.redhat.com/support/cases/#/case/03347605
Issue-2 : https://access.redhat.com/support/cases/#/case/03351162
Issue-3 : https://access.redhat.com/support/cases/#/case/03351106
Must-gather logs are attached in these support cases.

Actual results:


Expected results:
Issue- 1 : Pv should get created via the command line using yaml file.
Issue- 2 : Pv should get created via the webconsole
Issue- 3 : pods should be in running state after PV creation using nfs option via webconsole.