Bug 1384702 - Service Level and Release Version cannot be changed back to 'blank' once they've been set on an activation key
Summary: Service Level and Release Version cannot be changed back to 'blank' once they...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Activation Keys
Version: 6.2.2
Hardware: Unspecified
OS: Unspecified
high
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-13 23:06 UTC by Paul Dudley
Modified: 2021-03-11 14:44 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-01 20:08:29 UTC
Target Upstream Version:


Attachments (Terms of Use)
screenshot (65.28 KB, image/png)
2018-03-01 19:57 UTC, Justin Sherrill
no flags Details

Description Paul Dudley 2016-10-13 23:06:54 UTC
Description of problem:
Once the Release Version and Service Level fields have been saved a value they cannot change back to a 'blank' value. Meaning, in practice, that an activation key for systems meant for premium subscriptions will never be able to change back to the default 'blank' value that will allow the assignment of any service level subscription available on the key to use.

How reproducible:
100%

Steps to Reproduce:
1. Create activation key
2. Set service level and save
3. Attempt to change service level back to 'blank'

Additional info:
The release version does not cause any immediate problems, it seems. Using a 7Server release version key still works for a rhel 6 system. The system is only given access to rhel 6 repositories (with rhel 6 and 7 being available from the key). Everything seems okay here, only that the rhel 6 system is given a release version of 7Server.

Comment 3 Justin Sherrill 2018-03-01 19:57:02 UTC
This looks like its working fine on Satellite 6.2.14.  I've attached a screenshot.  Notice the 'x' marks beside the release version and activation key.

Comment 4 Justin Sherrill 2018-03-01 19:57:22 UTC
Created attachment 1402772 [details]
screenshot

Comment 5 Paul Dudley 2018-03-01 20:08:29 UTC
Closing bz as the 'x' now marks the release version as blank again in 6.2.14.


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