-
Bug
-
Resolution: Done-Errata
-
Major
-
4.13
-
None
-
Moderate
-
No
-
False
-
-
* Previously, the Machine API controller could not determine the zone of machines in vSphere clusters that use multiple zones. With this release, the zone lookup logic is based on the host of a VM and, as a result, machine objects indicate proper zones.
This is a clone of issue OCPBUGS-7249. The following is the description of the original issue:
—
Description of problem:
Machine and respective Node should indicate proper zones, but machine doesn’t indicate proper zones on multiple vCenter zones cluster
Version-Release number of selected component (if applicable):
4.13.0-0.nightly-2023-02-07-064924
How reproducible:
always
Steps to Reproduce:
1.Create a multiple vCenter zones cluster sh-4.4$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.13.0-0.nightly-2023-02-07-064924 True False 58m Cluster version is 4.13.0-0.nightly-2023-02-07-064924 sh-4.4$ oc get machine NAME PHASE TYPE REGION ZONE AGE jima15b-x4584-master-0 Running us-east 88m jima15b-x4584-master-1 Running us-east 88m jima15b-x4584-master-2 Running us-west 88m jima15b-x4584-worker-0-26hml Running us-east 81m jima15b-x4584-worker-1-zljp8 Running us-east 81m jima15b-x4584-worker-2-kkdzf Running us-west 81m 2.Check machine labels and node labels sh-4.4$ oc get machine jima15b-x4584-worker-0-26hml -oyaml apiVersion: machine.openshift.io/v1beta1 kind: Machine metadata: annotations: machine.openshift.io/instance-state: poweredOn creationTimestamp: "2023-02-09T02:28:03Z" finalizers: - machine.machine.openshift.io generateName: jima15b-x4584-worker-0- generation: 2 labels: machine.openshift.io/cluster-api-cluster: jima15b-x4584 machine.openshift.io/cluster-api-machine-role: worker machine.openshift.io/cluster-api-machine-type: worker machine.openshift.io/cluster-api-machineset: jima15b-x4584-worker-0 machine.openshift.io/region: us-east machine.openshift.io/zone: "" name: jima15b-x4584-worker-0-26hml namespace: openshift-machine-api sh-4.4$ oc get node jima15b-x4584-worker-0-26hml --show-labels NAME STATUS ROLES AGE VERSION LABELS jima15b-x4584-worker-0-26hml Ready worker 9m4s v1.26.0+9eb81c2 beta.kubernetes.io/arch=amd64,beta.kubernetes.io/instance-type=vsphere-vm.cpu-4.mem-16gb.os-unknown,beta.kubernetes.io/os=linux,failure-domain.beta.kubernetes.io/region=us-east,failure-domain.beta.kubernetes.io/zone=us-east-1a,kubernetes.io/arch=amd64,kubernetes.io/hostname=jima15b-x4584-worker-0-26hml,kubernetes.io/os=linux,node-role.kubernetes.io/worker=,node.kubernetes.io/instance-type=vsphere-vm.cpu-4.mem-16gb.os-unknown,node.openshift.io/os_id=rhcos,topology.csi.vmware.com/openshift-region=us-east,topology.csi.vmware.com/openshift-zone=us-east-1a,topology.kubernetes.io/region=us-east,topology.kubernetes.io/zone=us-east-1a
Actual results:
Machine doesn’t indicate proper zone, it's machine.openshift.io/zone: ""
Expected results:
Machine should indicate proper zone
Additional info:
Discussed here https://redhat-internal.slack.com/archives/GE2HQ9QP4/p1675848293159359
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- links to
-
RHBA-2024:4484
OpenShift Container Platform 4.13.z bug fix update