Red Hat Bugzilla – Bug 1326214
Should disable scale up for cancelled deployment on overview page
Last modified: 2016-05-12 12:35:51 EDT
Description of problem: For cancelled deployment on overview page, should disable the scale up to keep consistency with CLI, since oc scale dc/<dc-name> didn't scale cancelled deployments Version-Release number of selected component (if applicable): openshift v3.2.0.14 kubernetes v1.2.0-36-g4a3f9c5 etcd 2.2.5 How reproducible: Always Steps to Reproduce: 1. Create a dc $ oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/deployment/deployment1.json deploymentconfig "hooks" created 2. Wait for 1st deploy completed $ oc deploy hooks hooks deployment #1 deployed 3 minutes ago - 1 pod 3. Deploy then Cancel the deploy $ oc deploy hooks --latest; oc deploy hooks --cancel; oc deploy hooks Started deployment #2 Cancelled deployment #2 hooks deployment #2 failed 5 minutes ago: cancelled by the user hooks deployment #1 deployed 5 mintes ago - 1 pod 4. Check deployment info on web UI overview page Actual results: 4. For cancelled deployment #2, scale up is enabled, when scale up on web UI will generate new pod for cancelled deployment #2 Expected results: 4. For cancelled deployment, should disable the scale up Additional info:
This only happens for deployments without a service. https://github.com/jwforres/origin/pull/45
https://github.com/openshift/origin/pull/8476
checked on 04-18.2 puddle, this is already fixed, please move to ON_QA, then I could verify
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/RHSA-2016:1064