Description of problem: Using the scaling widget is a little flaky. There are times when you ask it to scale up 4 or 5 positions. Let's say from 1 to 5. The widget acknowledges that it is scaling to 5 in the smaller text. But at some point the widget remove the smaller text and decides to only scale to 4 and stops. What's likely happening is the widget is getting the expected value from the server (potentially from an eventually consistent replica) and overriding the request from the client. Version-Release number of selected component (if applicable): How reproducible: 30% of the time I try to recreate it I can get some sort of failure. Steps to Reproduce: 1. Keep requesting scale up operations on a 1 or 2 second interval. Additional info: It would probably make sense to not poll the server for the target value until after a longer period of inactivity on the client.
I can reproduce. It happens if you scale in the window between when we make a scaling request and we get an updated rc.spec.replicas in the watch callback.
https://github.com/openshift/origin/pull/8763
Since target release is 3.2.1, will check when 3.2.1 puddle is ready
Move to MODIFIED and wait for 3.2.1 puddle
Here are steps to check if code are merged to enterprise-3.2 branch Clone openshift/ose repo $ cd ose $ git log --pretty="%h %an %cd - %s" --date=local enterprise-3.2 | grep '0858b1f' $ git log --pretty="%h %an %cd - %s" --date=local master | grep '0858b1f' 0858b1f Samuel Padgett Mon May 9 21:36:20 2016 - Fix timing issue scaling deployments Could see from the result, PR #209 is not merged to enterprise-3.2 branch, could not test now
Checked against oc v3.2.1.1-1-g33fa4ea kubernetes v1.2.0-36-g4a3f9c5 scaling deployments works well
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-2016:1343