Bug 496731 - Multi-org - reactivation key created through UI does not include org id
Multi-org - reactivation key created through UI does not include org id
Product: Red Hat Satellite 5
Classification: Red Hat
Component: WebUI (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Shannon Hughes
Red Hat Satellite QA List
Depends On:
Blocks: 462714
  Show dependency treegraph
Reported: 2009-04-20 16:49 EDT by Brad Buckingham
Modified: 2014-05-09 06:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-05-09 06:37:55 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 Brad Buckingham 2009-04-20 16:49:54 EDT
Description of problem:

When a reactivation key is created through the web-UI, the key does not include the org id; however, if it is created using the API, it does.

For example, 

   key created using web-ui might look like : 'asdfjkl'
   key created using api might look like : '1-asdfjkl'

The intent of this BZ is to make the behavior consistent.

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

How reproducible:

Steps to Reproduce:
1. select System->System->Details->Reactivation -> Generate New Key
Actual results:
observe key as something like 'c40dff6a0a87fee1a8cea13fbefdfb1a'

Expected results:
if created in org 1, the expected result would be something like '1-c40dff6a0a87fee1a8cea13fbefdfb1a'

Additional info:

e.g. of key generation using api:

>>> client.system.obtainReactivationKey(key, 1000013430)
Comment 1 Clifford Perry 2014-05-09 06:37:55 EDT
We have not addressed this specific bug in over 5 years years. This does not seem to have an active customer case with the bug report either. Closing out as wontfix to clear from backlog. 

Please re-open if you disagree and wish further review.


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