Bug 1488380
| Summary: | No visible difference for DC and k8s deployment of same name on overview by default | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Xingxing Xia <xxia> | ||||
| Component: | Management Console | Assignee: | Robb Hamilton <rhamilto> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3.7.0 | CC: | aos-bugs, jforrest, jokerman, mmccomas, rhamilto | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.9.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Previously, you were unable to distinguish between an OpenShift DeploymentConfig and a Kubernetes extensions/v1beta1 Deployment on the web console overview since they used the same "Deployment" label. We've changed the label from "Deployment" to "Deployment Config" for DeploymentConfig resources on the overview so users can tell the difference.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-03-28 14:06:20 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: | |||||||
| Attachments: |
|
||||||
PR to resolve: https://github.com/openshift/origin-web-console/pull/2675 Checked in v3.9.0-0.22.0, now overview page shows DEPLOYMENT CONFIG for DC and DEPLOYMENT for k8s deploy 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-2018:0489 |
Created attachment 1322137 [details] no_visible_difference_for_DC_and_k8s_deployment_of_same_name Description of problem: On overview, no visible difference for DC and k8s deployment if they have same name unless user clicks to choose "Resource Type" in top "List by" drop-down. It is better to make difference by default without that extra click. Version-Release number of selected component (if applicable): v3.7.0-0.123.0 How reproducible: Always Steps to Reproduce: 1. Create DC $ oc run hello-openshift --image openshift/hello-openshift 2. Create k8s deployment $ cat hello-deployment.yaml apiVersion: extensions/v1beta1 kind: Deployment metadata: name: hello-openshift spec: replicas: 1 template: metadata: labels: name: hello-openshift spec: containers: - name: hello-openshift image: openshift/hello-openshift $ oc create -f hello-deployment.yaml 3. On overview, check DC and k8s deployment Actual results: 3. Hard to see which is DC, which is k8s, see screenshot. Unless user clicks to choose "Resource Type" in top "List by" drop-down Expected results: 3. It is better to make difference by default without that extra click Additional info: