Bug 1449949 - Duplicated resources on web confuse user which automatically increase replicas and make pods stuck on Overview page
Summary: Duplicated resources on web confuse user which automatically increase replic...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Samuel Padgett
QA Contact: XiaochuanWang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-11 08:45 UTC by XiaochuanWang
Modified: 2017-08-16 19:51 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-25 13:53:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
3.5 is not reproduced. (60.20 KB, image/png)
2017-05-11 08:45 UTC, XiaochuanWang
no flags Details
3.6 screenshot - makes user keep waiting (76.10 KB, image/png)
2017-05-11 08:46 UTC, XiaochuanWang
no flags Details
verified_on_v3.6.94 (72.77 KB, image/png)
2017-06-05 03:29 UTC, XiaochuanWang
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:1716 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.6 RPM Release Advisory 2017-08-10 09:02:50 UTC

Description XiaochuanWang 2017-05-11 08:45:49 UTC
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.

Comment 1 XiaochuanWang 2017-05-11 08:46:58 UTC
Created attachment 1277789 [details]
3.6 screenshot - makes user keep waiting

Comment 3 Jessica Forrester 2017-05-11 14:24:41 UTC
We can't merge the fix for this until the oadm migrate story is complete for ownerRefs

Comment 4 openshift-github-bot 2017-05-19 13:04:25 UTC
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

Comment 6 XiaochuanWang 2017-06-05 03:29:08 UTC
Created attachment 1284857 [details]
verified_on_v3.6.94

Comment 7 XiaochuanWang 2017-06-05 03:31:07 UTC
Verified on 3.6.94, attached screenshot "attachment 1284857 [details]"
OpenShift Master:    v3.6.94
Kubernetes Master:   v1.6.1+5115d708d7


Note You need to log in before you can comment on or make changes to this bug.