Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1333158 - Scaling widget is a little flaky
Scaling widget is a little flaky
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console (Show other bugs)
3.2.0
Unspecified Unspecified
unspecified Severity medium
: ---
: 3.2.1
Assigned To: Samuel Padgett
Yadan Pei
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2016-05-04 15:31 EDT by Dan McPherson
Modified: 2016-06-27 11:06 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
When scaling deployments in the web console, if multiple scaling requests were made in a short amount of time, it was possible for the operation to result with an incorrect number of replicas. This bug fix addresses a timing issue, and as a result the correct number of replicas are now set in this scenario.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-06-27 11:06:35 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1343 normal SHIPPED_LIVE Red Hat OpenShift Enterprise 3.2.1.1 bug fix and enhancement update 2016-06-27 15:04:05 EDT

  None (edit)
Description Dan McPherson 2016-05-04 15:31:42 EDT 
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.
Comment 1 Samuel Padgett 2016-05-05 13:24:39 EDT 
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.
Comment 2 Samuel Padgett 2016-05-05 13:45:24 EDT 
https://github.com/openshift/origin/pull/8763
Comment 4 Yadan Pei 2016-05-25 21:47:53 EDT 
Since target release is 3.2.1, will check when 3.2.1 puddle is ready
Comment 5 Yadan Pei 2016-05-26 05:44:33 EDT 
Move to MODIFIED and wait for 3.2.1 puddle
Comment 6 Yadan Pei 2016-05-26 05:55:41 EDT 
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
Comment 8 Yadan Pei 2016-06-06 04:32:10 EDT 
Checked against 
oc v3.2.1.1-1-g33fa4ea
kubernetes v1.2.0-36-g4a3f9c5

scaling deployments works well
Comment 10 errata-xmlrpc 2016-06-27 11:06:35 EDT 
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
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.