Description of problem (please be detailed as possible and provide log
snippests):
------------------------------------------------------------------
For Arbiter mode install from UI, the UI accepts any or both of the following two labels for participating nodes:

>>failure-domain.beta.kubernetes.io/zone=a  --> deprecated
>>topology.kubernetes.io/zone=c

Hence, when used the new  tolopolgy label instead of the deprecated failure-domain.beta.kubernetes , the nodes were properly selected in the UI.

But on clicking Create, it is seen that even though arbiter is enabled, the install failed and no ceph pods were created. The storagecluster yaml had failureDomain set incorrectly to rack instead of zone

 failureDomain: rack

spec:
  arbiter:
      enable: true
  nodeTopologies:
      arbiterLocation: c


Already Had a discussion with Raghavendra and he confirmed that the fix is still on the way and as of now, ocs-operator might be looking for the old deprecated label for zone. Hence raised a bug to track the effort.

Log from rook operator
-------------------------

2021-01-13 13:06:29.347448 E | ceph-cluster-controller: failed to reconcile. failed to reconcile cluster "ocs-storagecluster-cephcluster": failed to configure local ceph cluster: failed to perform validation before cluster creation: expecting exactly three zones for the stretch cluster, but found 5


Version of all relevant components (if applicable):
=========================================================
$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.7.0-0.nightly-2021-01-12-203716   True        False         5h52m   Cluster version is 4.7.0-0.nightly-2021-01-12-203716
[nberry@localhost jan13-vmw-dr]$ oc get csv -n openshift-storage
NAME                         DISPLAY                       VERSION        REPLACES   PHASE
ocs-operator.v4.7.0-230.ci   OpenShift Container Storage   4.7.0-230.ci              Succeeded



Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
================================================================
Yes arbiter install didnt succeed and all docs and demos suggest to use the topology label.

Is there any workaround available to the best of your knowledge?
==============================================================
Use deprecated failure-domain label

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

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:
==============================================================
New feature

Steps to Reproduce:
=====================
1. Install and OCP cluster on vmware with attached LSO devices. 2 W each on 2 zones and third zone can have only one master.

2. Label all W nodes in zone-a and zone-b with correct topology.kubernetes.io/zone label. label the master node in third rac
2. Follow UI flow to install OCS
3. Check the pods 




Actual results:
=================
The ceph pods failed to get created and storagecluster is stuck in Progressing state. The nodes are added with rack label too.

Expected results:
--------------------
The new "topology.kubernetes.io/zone" should be accepted by ocs-operator and install should succeed.