Bug 1173727

Summary: Activation key product content doesn't remain updated in ui until the key is reselected
Product: Red Hat Satellite Reporter: jcallaha
Component: WebUIAssignee: Christine Fouant <cfouant>
WebUI sub component: Katello QA Contact: Katello QA List <katello-qa-list>
Status: CLOSED DUPLICATE Docs Contact:
Severity: medium    
Priority: unspecified CC: bbuckingham, bkearney, cwelton
Version: NightlyKeywords: Triaged
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-09 17:57:48 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:
Embargoed:

Description jcallaha 2014-12-12 19:09:30 UTC 
Description of problem: 
When updating the product content, you have to go back into the activation key for the change to remain visible.  


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


How reproducible:
Always


Steps to Reproduce:
1. Create and activation key and add subscription(s)
2. Select the Product Content tab and override products to yes and/or no.
3. Click one of the other activation key tabs (Details, Subscriptions, etc..)
4. Click back into the Product Content tab and see if your changes have "stuck"
5. If you have another activation key, select it now, then go back into your testing key.
   If not, select Content -> Activation Keys from the menu, then select your key again.
6. Finally go back into Product Content and your changed values should be shown.

Actual results:
Selected values aren't shown, Previous ones are instead.


Expected results:
Selected values should be shown.
Comment 1 RHEL Program Management 2014-12-12 19:34:37 UTC 
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3 Christine Fouant 2015-01-09 17:57:48 UTC 

*** This bug has been marked as a duplicate of bug 1112747 ***