-
Bug
-
Resolution: Done
-
Critical
-
None
-
openshift-4.17
-
None
Currently there is an issue in the ipi-conf-vsphere-check-vcm-commands.sh that for multi vcenter the wrong datacenters are being put in the vcenters section of the install config.
platform:
vsphere:
vcenters:
- server: vcenter-1.ci.ibmc.devcluster.openshift.com
user: ci-user-1@ci.ibmc.devcluster.openshift.com
datacenters:
- cidatacenter-2
- server: vcenter.ci.ibmc.devcluster.openshift.com
user: ci-user-2@ci.ibmc.devcluster.openshift.com
datacenters:
- cidatacenter-2
- cidatacenter
failureDomains:
- server: vcenter-1.ci.ibmc.devcluster.openshift.com
name: vcenter-1.ci.ibmc.devcluster.openshift.com-cidatacenter-2-cicluster-3
zone: us-central-1a
region: us-central
topology:
resourcePool: /cidatacenter-2/host/cicluster-3/Resources/ipi-ci-clusters
computeCluster: /cidatacenter-2/host/cicluster-3
datacenter: cidatacenter-2
datastore: /cidatacenter-2/datastore/vsanDatastore
networks:
- ci-vlan-918
- server: vcenter.ci.ibmc.devcluster.openshift.com
name: vcenter.ci.ibmc.devcluster.openshift.com-cidatacenter-cicluster
zone: us-east-1a
region: us-east
topology:
resourcePool: /cidatacenter/host/cicluster/Resources/ipi-ci-clusters
computeCluster: /cidatacenter/host/cicluster
datacenter: cidatacenter
datastore: /cidatacenter/datastore/vsanDatastore
networks:
- ci-vlan-1279
datacenter-2 is not in both vCenters. In fact, it should only be in one of the vcenters based on the failure domain config.