Bug 1882739

Description of problem:
----------------------------
IN UI, While restoring a snapshot to a PVC, the dialog page allows you to select StorageClass from the drop-down. Few issues around here:

1. There is no message in the dialog box to ensure/instruct user to select an SC 

  --- a) which is same as the one Parent Volume was created with
  --- b) A different SC but attached to the same pool as the one Parent Volume was created with 

2. There is no enforcement for #1 as well and user is allowed to select any SC from the list(even if it is not the correct one)

Observations due to above
================
1.while restoring SC, in case a user selects a different SC than parent Volume SC(with different pool) , the PVC stays in Pending state 

2. If we select a different SC, yet the attached poolName is same as the parent volume's SC, the snapshot Restore succeeds and PVC is in BOUND state.


Ask: We need to handle this in UI so that user is not able to select an SC for Restore, whose poolName is different than its Parent Volume


>>UI Events

failed to provision volume with StorageClass "sc-rbd2": rpc error: code = Unknown desc = failed to create rbd clone: RBD image not found

>>$ oc describe pvc -n test-pvcs rbd-pvc1-snapshot-restore2

Events:
  Type     Reason                Age                    From                                                                                                                Message
  ----     ------                ----                   ----                                                                                                                -------
  Normal   Provisioning          3m51s (x10 over 8m6s)  openshift-storage.rbd.csi.ceph.com_csi-rbdplugin-provisioner-794cdd474c-cmwqr_6ab56332-b009-4f51-b680-5dbac2418367  External provisioner is provisioning volume for claim "test-pvcs/rbd-pvc1-snapshot-restore2"
  Warning  ProvisioningFailed    3m51s (x10 over 8m6s)  openshift-storage.rbd.csi.ceph.com_csi-rbdplugin-provisioner-794cdd474c-cmwqr_6ab56332-b009-4f51-b680-5dbac2418367  failed to provision volume with StorageClass "sc-rbd2": rpc error: code = Unknown desc = failed to create rbd clone: RBD image not found
  Normal   ExternalProvisioning  2m14s (x26 over 8m6s)  persistentvolume-controller                                                                                         waiting for a volume to be created, either by external provisioner "openshift-storage.rbd.csi.ceph.com" or manually created by system administrator




Version-Release number of selected component (if applicable):
-------------------------------------------------------------
OCP = 4.6.0-0.nightly-2020-09-25-070943
OCS = ocs-operator.v4.6.0-569.ci

How reproducible:
===================
Always


Steps to Reproduce:
-----------------------
1. Create an RBD PVC using default SC = ocs-storagecluster-ceph-rbd. Write some IO after mounting to a pod.
2. Create 1-2 custom SCs from UI:
e.g. : SC = rbd-default-pool , pool :ocs-storagecluster-cephblockpool
       SC = sc-rbd2; pool =  new pool, e.g. sc-pool-2


3. Create Snapshot of the PVC : Persistent Volume Claims->PVC->Actions->Create Snapshot

4. Once snapshot is created, click on the VOlume Snapshot-> 3 dots-> Restore to a new PVC

5. In the new dialog page, Name= rbd-pvc-snap-restore1; select a new SC (e.g. sc-rbd2) and click on Create

6. Check the Restored Snapshot's PVC status. It is in pending state.

7. Restore the snapshot again, say Name= rbd-pvc-snap-restore2, this time selecting rbd-default-pool(different SC but same pool):  PVC gets BOUND

8. Restore the snapshot, say Name = rbd-pvc-snap-restore3; SC = ocs-storagecluster-ceph-rbd(same as parent) : PVC gets BOUND

Actual results:
----------------------

The PVC is in pending state as the pool Name is different and it is unable to find the rbd image name 

Expected results:
--------------------
User should not be allowed to select an SC which has a diffeent pool than the parent colume during Snapshot restore flow.


Additional info:
---------------------
$ for i in $(oc get sc|awk '{print$1}'); do echo $i; echo +++++++++++++; oc get sc $i -o yaml|egrep 'name:|pool:'|grep -v noobaa|grep -v thin; echo "";  done