Bug 1384702

Summary: Service Level and Release Version cannot be changed back to 'blank' once they've been set on an activation key
Product: Red Hat Satellite Reporter: Paul Dudley <pdudley>
Component: Activation KeysAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: high    
Version: 6.2.2CC: bbuckingham, egolov, jcallaha, jsherril, kdixon, ktordeur
Target Milestone: UnspecifiedKeywords: PrioBumpGSS, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-01 20:08:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
screenshot none

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.