Red Hat Bugzilla – Bug 1112747
Activation key product content changes aren't reflected in the UI
Last modified: 2017-02-23 16:14:38 EST
Description of problem: Currently updating the product content of an activation key does update the activation key, but does not reflect in the UI. How reproducible: always Steps to Reproduce: 1. Create an activation key 2. Add a subscription to the activation key 3. under the product content tab, change the default of a content Actual results: You'll see the item change, but navigating away and back reverts what it displays. (eg. if you disable a content, it will show as disabled, but refreshing the page shows it as enabled again). Expected results: refreshing should still show the selection Additional info: This seems to be a display issue, as using the activation key shows what was actually set.
candlepin-tomcat6-0.9.19-1.el6.noarch candlepin-0.9.19-1.el6.noarch
Notes from debug: The content_overrides in the json is attached to the activation key, not returned in the products call. The results of the update should be attached to the existing act key javascript object. To reproduce: 1. set an override on "Product Content" 2. switch to "Subscriptions" tab 3. return to "Product Content" and note that the override is not changed ^-- this is the bug 4. close the act key details 5. open the act key details 6. go to "Product Content" tab and note that the override is changed ^-- this means it is just a presentation UI bug but the feature is actually working
Created redmine issue http://projects.theforeman.org/issues/8040 from this bug
*** Bug 1173727 has been marked as a duplicate of this bug. ***
Moving to POST since upstream bug http://projects.theforeman.org/issues/8040 has been closed ------------- Christine Fouant Applied in changeset commit:katello|1fa3e12d129809f0583eec54037e8877c237b19a.
Verified in Satellite 6.1.0 snap 5. Version tested: RHEL 66 RHEL 7
This bug is slated to be released with Satellite 6.1.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2015:1592