Bug 114056 - proxy doesn't handle errors gracefully
proxy doesn't handle errors gracefully
Status: CLOSED CURRENTRELEASE
Product: Red Hat Satellite Proxy 5
Classification: Red Hat
Component: Server (Show other bugs)
420
All Linux
medium Severity medium
: ---
: ---
Assigned To: Todd Warner
Red Hat Satellite QA List
:
Depends On:
Blocks: 110950
  Show dependency treegraph
 
Reported: 2004-01-21 18:42 EST by Daniel Wittenberg
Modified: 2007-10-23 21:35 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-09-07 13:19:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Daniel Wittenberg 2004-01-21 18:42:55 EST
Description of problem:
proxy doesn't handle errors gracefully

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


How reproducible:
Errors or announcements posted to RHN site

Steps to Reproduce:
1.Wait for Red Hat to post announcement on RHN site
2.
3.
  
Actual results:
Time: Tue Jan 20 06:27:47 2004Exception type xmlrpclib.FaultException
while handling function ProxyAuth.login (xmlrpclib.Fault)Exception
Handler InformationTraceback (innermost last):  File
"/var/www/rhns/proxy/broker/rhnProxyAuth.py", line 191, in login   
raise eFault: <Fault -1 """IMPORTANT MESSAGE FOLLOWS:Red Hat Network
will be offline for scheduled maintenancefor approximately 1 hour(s),
beginning at 6:30 am EST.Red Hat Network will be brought back online
no later than 8 am EST.We apologize for any inconvenience this outage
may cause.Thank you for using Red Hat Network.--the RHN team""">Local
variables by frameFrame login in
/var/www/rhns/proxy/broker/rhnProxyAuth.py at line 193
.
.
.



Expected results:


Additional info:
Comment 1 Todd Warner 2004-01-22 11:26:54 EST
What precisely did you see on the client side?
Comment 2 Todd Warner 2004-01-22 12:30:36 EST
Adding to 310 proxy tracking bug.
Comment 3 Daniel Wittenberg 2004-01-22 13:52:21 EST
The errors I saw were the ones I posted, though it mundged the spacing
after posting
Comment 4 Todd Warner 2004-01-22 18:52:22 EST
The error you showed be was taken from the RHN Proxy log file. I am
curious as to what an up2date client saw.

I will, of course, duplicate this here when I get a chance to set up
the scenario. Just trying to pump as much info from you as possible.

Comment 5 Daniel Wittenberg 2004-01-23 01:10:40 EST
Unfortunately I was not around when these errors have happened now and
in the past, so not sure what the up2date clients saw.  I will try
next time.
Comment 6 Todd Warner 2004-01-26 16:34:43 EST
I will try to reproduce, regardless. Thanks for the heads up.
Comment 7 Todd Warner 2004-02-24 17:25:11 EST
Fixed. In newer version... coming soon to a channel near you!

RHN Proxy's own login borked during scheduled RHN downtimes. This is
fine if it nicely forwarded the message. It does... but in an ugly way.

I made it a bit better. I.e., the client will see what the client
expects to see. An outage message. The proxy merely proxies.

TEST PLAN (for QA guy):
-----------------------
o point RHN Proxy (new version) at an RHN Satellite.
o outage your RHN Satellite:
  - echo "BOO!" > /etc/rhn/message_to_all.txt
  - add this to /etc/rhn/rhn.conf:
    server.send_message_to_all = 1
o make sure you blow away the rhn_auth_cache:
rm -v /var/up2date/rhn_auth_cache
service rhn_auth_cache restart
o run up2date of some client against that RHN Proxy
  * should see the outage message *


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