vRealize deployment on wrong AZ after Stretch cluster
search cancel

vRealize deployment on wrong AZ after Stretch cluster


Article ID: 343302


Updated On:


VMware Cloud Foundation


To provide a workaround for the VCF environment where this issue is observed.


If Stretch cluster workflow is executed and followed by that, the customer deploys vRealize products the vRealize VMs will not be on the primary AZ.
As part of the Stretch cluster workflow Affinity Rule is created in vCenter to keep the VMs on the correct AZ and add this rule to the current VMs, but in this case, the vRealize VMs are deployed after the cluster is stretched so they are not part of this rule.


VMware Cloud Foundation 4.3
VMware Cloud Foundation 4.2
VMware Cloud Foundation 4.1
VMware Cloud Foundation 4.4
VMware Cloud Foundation 4.0.x


This is a known issue in the SDDC manager.


Recommend to follow the workaround for now

  1. Open the vCenter UI and log in.
  2. Select the Cluster where the the MGMT VMs are deployed
  3. Navigate to: Configure -> VM/Host Rules -> select the "<Cluster-name>_VMs should be on Primary Site" rule.
  4. Add the vRealize VMs