Bug 1649221
| Summary: | Go to RS/RC Pods page when clicking pods selector on Overview | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Yadan Pei <yapei> |
| Component: | Management Console | Assignee: | Jon Jackson <jonjacks> |
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.1.0 | CC: | aos-bugs, jokerman, mmccomas, yapei |
| Target Milestone: | --- | ||
| Target Release: | 4.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: Pods are associated with Deployments and DeploymentConfigs using label selectors which causes a collision for Deployments and DeploymentConfigs with duplicate names.
Consequence: It is possible for pods to be incorrectly listed on Deployment and DeploymentConfig 'Pods' tab. When linking to these resources from the overview page, the user might see extra pods listed.
Fix: Instead of linking to the 'Pods' tab of the DeploymentConfig or Deployment resource, the pod status link on the overview page was updated to point to the 'Pods' tab of the underlying ReplicationController or ReplicaSet, respectively.
Result: User will see correct pods listed when they click on the pod status link from the overview page.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-06-04 10:40:51 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: | |
| Embargoed: | |||
|
Description
Yadan Pei
2018-11-13 07:49:30 UTC
We use label selectors in the query to create the pod list. Since the examples use the same label selector, it will match additional pods. We can fix by filtering the result using owner references, although we have to do this on the client. Yes, that's what I'm thinking about: if we can change the filter I agree we should go to the replica set or replication controller page, not the deployment. Jon, can you take a look? Checked against registry.svc.ci.openshift.org/openshift/origin-v4.0-2018-12-20-221917@sha256 2e5118bf01de4e2ee4285dda0e633357d7012e12c1f08066ce22c9af3d8bb312 43b646f5b084 8 hours ago 268 MB openshift/console commit ID: 967b28133b5e43c4bdcb48b44d30f63d2cadff9e 1.Create 'example' Deployment Config using the example YAML in Deployment Configs page 2.Create 'example' Deployment using the example YAML in Deployments page 3.When all pods are created and running, go to Home -> Overview, it shows 3 of 3 4.Clicking on 3 of 3 for Deployment Config 'example', it redirects to RC page, showing 3 pods 5.Clicking on 3 of 3 for Deployment 'example', it redirects to RS page, showing 3 pods Move to VERIFIED 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-2019:0758 |