Bug 234676 – Attempting to generate re-activation key in stage results in 500 ISE - for RHN Proxy's

Bug 234676 - Attempting to generate re-activation key in stage results in 500 ISE - for RHN Proxy's

Summary:	Attempting to generate re-activation key in stage results in 500 ISE - for RH...

Status:	CLOSED DUPLICATE of bug 231618

Aliases:	None

Product:	Red Hat Network
Classification:	Red Hat
Component:	RHN/Web Site (Show other bugs)
Sub Component:
Version:	rhn500
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Mike McCune
QA Contact:	Red Hat Satellite QA List
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2007-03-30 22:54 EDT by David Robinson
Modified:	2007-04-17 14:36 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-04-17 14:36:37 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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description David Robinson 2007-03-30 22:54:41 EDT

Description of problem:
Similar to BZ 231618. I take a RHN Proxy system registered to stage. I then go
to Details -> Reactivation and click 'Generate new Key' button. This results in
an "500 Error - Internal Server Error".

https://rhn.redhat.com/network/systems/details/activation.pxt?sid=1007104580

Version-Release number of selected component (if applicable):
Red Hat Network release 5.0.0

How reproducible:
100%.

Steps to Reproduce:
1. Take a RHN proxy registered to RHN.
2. From Details -> Reactivation -> Click "Generate new Key" button
3. Internal Server Error
  
Actual results:
Internal Server Error

Expected results:
A new key is generated.

Additional info:
I was unable to test whether the fix for 231618 resolves this issue (I don't
have access to webqa).

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