Bug 432339 - Deleting of activation key lead to old perl page
Deleting of activation key lead to old perl page
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Miroslav Suchý
Corey Welton
Depends On:
Blocks: 248640
  Show dependency treegraph
Reported: 2008-02-11 08:26 EST by Miroslav Suchý
Modified: 2008-04-02 16:47 EDT (History)
0 users

See Also:
Fixed In Version: sat510
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-02 16:47:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Miroslav Suchý 2008-02-11 08:26:36 EST
Description of problem:
Deleting of activation key lead to old perl page. If you click from thih page on
"create new activation key" it leads to perl page too. And this page is not
multiorg aware.

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

How reproducible:
done twice

Steps to Reproduce:
1. Create Activation key
2. Delete activation key

Actual results:

Expected results:

Additional info:
Create new activation key lead to:
Comment 1 Miroslav Suchý 2008-02-11 08:36:47 EST
Commited fix in trunk as rev. 136748.
Comment 2 Miroslav Suchý 2008-02-11 09:33:30 EST
I added additional commit 136752, which add correct link to "Create Activation
key" on perl page:
There should be no links to this page, and possibly can be removed. But this is
more safe.
Comment 3 Miroslav Suchý 2008-02-13 03:24:10 EST
Satellite 5.1.0-143 and Proxy 5.1.0-28 Content now available on webqa Channels. 

Moving ON_QA.
Comment 4 Corey Welton 2008-02-13 11:58:00 EST
QA Verified, scenario no longer leads to bad pages, and link to create a new
activation key correctly returns user to multiorg aware activation key page.
Comment 5 Brandon Perkins 2008-04-02 16:47:52 EDT
Multi-Org Satellite for 5.1 Sat GA so Closed for Current Release.

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