Bug 488246 - Activation of RHN Proxy for second time will fail
Summary: Activation of RHN Proxy for second time will fail
Keywords:
Status: CLOSED DUPLICATE of bug 501508
Alias: None
Product: Red Hat Network
Classification: Retired
Component: RHN/Backend
Version: RHN Devel
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bryan Kearney
QA Contact: Red Hat Network Quality Assurance
URL:
Whiteboard: us=79015
Depends On:
Blocks: 428922
TreeView+ depends on / blocked
 
Reported: 2009-03-03 14:14 UTC by Miroslav Suchý
Modified: 2013-01-10 09:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-07-23 21:00:08 UTC
Embargoed:

Attachments (Terms of Use)

Description Miroslav Suchý 2009-03-03 14:14:30 UTC 
Description of problem:
See steps to reproduce

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


How reproducible:


Steps to Reproduce:
0. rhn_register to hosted (I done against webqa)
1. install pacewalk-proxy-installer from RHN tools channel
2. run configure-proxy.sh
3. Let it fail (e.g. put wrong password to SSL cert)
4. installer will deactivate the proxy
5. run configure-proxy.sh again
And during activation you will get error
  
Actual results:
....
Organization []: RedHat
Organization Unit [vmware127.englab.brq.redhat.com]:
Common Name [vmware127.englab.brq.redhat.com]:
City []: brno
State []: .
Country code []: CZ
Email [msuchy]:
API version: 5.0.9

There was a problem activating the RHN Proxy entitlement:
ERROR: upon entitlement/activation attempt: unknown error - <Fault -2: 'unhandled internal exception: null'>
Proxy activation failed! Installation interrupted.
API version: 5.0.9
RHN Proxy successfully deactivated.

Expected results:
No errors and successfully activate even for second time activation.

Additional info:
Comment 1 Stephen Herr 2009-07-23 21:00:08 UTC 
While it may not look like a duplicate, this issue was resolved by the fix for bug 501508.

*** This bug has been marked as a duplicate of bug 501508 ***
Note You need to log in before you can comment on or make changes to this bug.