Bug 1449949
| Summary: | Duplicated resources on web confuse user which automatically increase replicas and make pods stuck on Overview page | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | XiaochuanWang <xiaocwan> | ||||||||
| Component: | Management Console | Assignee: | Samuel Padgett <spadgett> | ||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | XiaochuanWang <xiaocwan> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 3.6.0 | CC: | aos-bugs, jforrest, jokerman, mmccomas, smunilla, spadgett, wmeng | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2017-07-25 13:53:42 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: |
|
||||||||||
Created attachment 1277789 [details]
3.6 screenshot - makes user keep waiting
We can't merge the fix for this until the oadm migrate story is complete for ownerRefs Commit pushed to master at https://github.com/openshift/origin-web-console https://github.com/openshift/origin-web-console/commit/269097141e9aa6d5ef9229eaf76f9309477a4b21 Bug 1449949 - Group pods by owner reference Use owner references to group pods owned by replication controllers, replica sets, and stateful sets. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1449949 Created attachment 1284857 [details]
verified_on_v3.6.94
Verified on 3.6.94, attached screenshot "attachment 1284857 [details]"
OpenShift Master: v3.6.94
Kubernetes Master: v1.6.1+5115d708d7
|
Created attachment 1277787 [details] 3.5 is not reproduced. Description of problem: Create resources twice with different names, replicas is increased automatically and pods on app section on overview page is stuck. Version-Release number of selected component (if applicable): openshift v3.6.74 How reproducible: Always Steps to Reproduce: 1. create following resource twice with different names - "hello-openshift1" and "hello-openshift2" apiVersion: extensions/v1beta1 kind: Deployment metadata: name: hello-openshift1 spec: replicas: 4 template: metadata: labels: app: hello-openshift spec: containers: - name: hello-openshift image: openshift/hello-openshift ports: - containerPort: 80 strategy: rollingUpdate: maxSurge: 3 maxUnavailable: 2 type: RollingUpdate 2. Check Overview page Actual results: Application section on Overview page is stuck, user can't scale pods for both deployments. Refer to screenshot "3.6_2deployments.png" Please see the "Additional info", checking from oc, pods for each deployment never be scaled to 8. The display on console will confuse user. Compared with 3.5, this could be fixed. Expected results: Both deployment should keep the replicas, should not increase pod replias automatically Additional info: 1) This is caused by the exactly same labels. Will not reproduced when label is different 2) 3.5.5.10 does not reproduced even when labels are exactly same, refer to screenshot "3.5.5.10_not_reproduced.png" 3) Pods are not actually automatically increased checking by oc. When the 2nd deployment is created, 4 new pods are created, 8 pods in total.