Bug 798610 - Test case failure: Verify CDS Load balancer is balancing the yum client requests
Test case failure: Verify CDS Load balancer is balancing the yum client requests
Status: CLOSED NOTABUG
Product: Red Hat Update Infrastructure for Cloud Providers
Classification: Red Hat
Component: CDS (Show other bugs)
2.0.2
Unspecified Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Jay Dobies
wes hayutin
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-02-29 06:31 EST by mkovacik
Modified: 2012-03-12 15:45 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-02-29 07:45:47 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
screen logs from clients and access logs from CDSes (5.84 KB, application/zip)
2012-02-29 06:31 EST, mkovacik
no flags Details

  None (edit)
Description mkovacik 2012-02-29 06:31:03 EST
Created attachment 566530 [details]
screen logs from clients and access logs from CDSes

Filed from caserun (INSERT URL HERE)

Version-Release number of selected component (if applicable):
unspecified

Steps to Reproduce: 
- RHUI setup should be up and running with two CDS nodes:

 


1. Run rhui-manager

2. Register two CDS nodes. Make sure repos are synched with CDS.

3. Install client config rpms on two different nodes

4. Submit the yum install request from two different clients.



Actual results:
As can be seen in the ssl_access_log from both the CDSes, rpms are always being fetched from the same node for both the clients

Expected results:
Verify the ssl_access_logs on both CDS nodes. CDS nodes should get the yum
client request from on after another from different clients.
Comment 1 mkovacik 2012-02-29 07:45:47 EST
Tester error -- works as can be seen in the logs...
Comment 2 James Slagle 2012-03-12 15:38:53 EDT
Released in RHUI 2.0.2

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