Description of problem (please be detailed as possible and provide log
snippests):

openshift cluster consisting of 17(deployed on vmwareESXi) nodes located in 3 different zones (MN,ME,TH2), customer started with 7 storage nodes (which are labeled by cluster.ocs.openshift.io/openshift-storage="" and for each node we put 2 disks of 2 TB each), among its 7 storage nodes they have an arbitrator node that is deployed on the th2 zone
ODF and the storage system state is healthy
then customer wanted to increase/scale up the size of storage by adding 2 new nodes to the cluster.

2 new nodes are added 1 per zone.

Nodes Labeled correctly and 2 available PVs on each node

storage system => add capacity=>

message "The Arbiter stretch cluster requires a minimum of 4 nodes (2 different zones, 2 nodes per zone). Please choose a different StorageClass or create a new LocalVolumeSet that matches the minimum node requirement."

Version of all relevant components (if applicable):

OCS Version is : 4.14.4

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

Failing to add capacity.

Is there any workaround available to the best of your knowledge?

No

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, in the customer environment.

Can this issue reproduce from the UI?

Yes

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

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info: