| Summary: | value for node's Zone is wrong on administrator console | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Junqi Zhao <juzhao> | ||||
| Component: | Management Console | Assignee: | Rastislav Wagner <rawagner> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 4.5 | CC: | aos-bugs, jokerman, rhamilto | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.5.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | No Doc Update | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-07-13 17:35:55 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
Reassignign to Rastislav since he delivered this functionality. I think this is a labeling issue as https://github.com/openshift/console/blob/master/frontend/packages/console-app/src/components/nodes/node-dashboard/DetailsCard.tsx#L21 explicitly points at `topology.kubernetes.io/region` and not `topology.kubernetes.io/zone`. Tested with 4.5.0-0.nightly-2020-05-12-191228, value for Zone on "Compute -> Node" is the same with node's label "topology.kubernetes.io/zone" Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409 |
Created attachment 1686128 [details] value for node's Zone is wrong on administrator console Description of problem: cluster-admin user, go to "Compute -> Node" on administrator console, take one node as example, the zone is "ap-south-1a", but from the picture, it is "ap-south-1" # oc get node --show-labels | grep "ip-10-0-136-178.ap-south-1.compute.internal" ip-10-0-136-178.ap-south-1.compute.internal Ready worker 10h v1.18.0-rc.1 beta.kubernetes.io/arch=amd64,beta.kubernetes.io/instance-type=m5.xlarge,beta.kubernetes.io/os=linux,failure-domain.beta.kubernetes.io/region=ap-south-1,failure-domain.beta.kubernetes.io/zone=ap-south-1a,kubernetes.io/arch=amd64,kubernetes.io/hostname=ip-10-0-136-178,kubernetes.io/os=linux,node-role.kubernetes.io/worker=,node.kubernetes.io/instance-type=m5.xlarge,node.openshift.io/os_id=rhcos,topology.kubernetes.io/region=ap-south-1,topology.kubernetes.io/zone=ap-south-1a Version-Release number of selected component (if applicable): 4.5.0-0.nightly-2020-05-06-003431 How reproducible: always Steps to Reproduce: 1. See the description 2. 3. Actual results: zone is not right Expected results: no error Additional info: