| Summary: | [userinterface_public_714] Should disable scale up/down when deployment is in rolling update process | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | OKD | Reporter: | Yadan Pei <yapei> | ||||||
| Component: | Management Console | Assignee: | Samuel Padgett <spadgett> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Yadan Pei <yapei> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 3.x | CC: | aos-bugs, jforrest, mmccomas | ||||||
| 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: | 2016-12-09 21:49:52 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: |
|
||||||||
Created attachment 1208510 [details]
DeploymentInRollingUpdateProcess-ScaleUpDownEnabled
Created attachment 1208511 [details]
DCInDeploymentProcess-BothDisabled
origin bug, this can go straight to ON_QA Checked against latest origin-web-console（latest commit is #746） Scale Up and Scale Down is still enabled when deployment in rolling process I can't reproduce. What are seeing? Do the buttons never disable at all? Hi Samuel, today I checked against 3.4.0.17 and found this has been fixed. Scale up and down are disabled for both old & new deployment during the update process Will move to VERIFIED, sorry about inconvenience. |
Description of problem: When deployment is in rolling update process, the scale up and scale down arrow for new deployment on overview page still enabled Version-Release number of selected component (if applicable): openshift v1.4.0-alpha.0+cc110d2 (latest origin-web-console, the latest commit is 6a784016a2255481933d0c527ad835c9aaa09c14) How reproducible: Always Steps to Reproduce: 1.Create deployment # cat >> hello-deployment-1.yaml << EOF apiVersion: extensions/v1beta1 kind: Deployment metadata: name: hello-openshift 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 EOF # oc create -f hello-deployment-1.yaml deployment "hello-openshift" created 2. Wait all pods(4 pods) are ready 3. Update deployment/hello-openshift,change .spec.template.spec.containers.image to yapei/hello-openshift-fedora # oc edit deployment/hello-openshift deployment "hello-openshift" edited 4. Check deployments on Overview page Actual results: 4. When deployment in Rolling update process, scale up and scale down arrow for new deployment is still enabled Expected results: 4. Should disabled scale up and scale down arrow for new ones when deployment in rolling update process until deployment update finish Additional info: