Bug 1316688

Summary: Activation keys summary page 'consumed' shows zero after registering content hosts
Product: Red Hat Satellite Reporter: sthirugn <sthirugn>
Component: Content ManagementAssignee: Brad Buckingham <bbuckingham>
Status: CLOSED ERRATA QA Contact: sthirugn <sthirugn>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/14192
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 09:27:01 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 sthirugn@redhat.com 2016-03-10 19:27:35 UTC 
Description of problem:
Activation keys summary page 'consumed' shows zero after registering content hosts

Version-Release number of selected component (if applicable):
Satellite 6.2.0-beta-snap3

How reproducible:
Always

Steps to Reproduce:
1. Create activation key, attach subs and register content host/activation keys
2. Review the Content -> Activation Keys page

Actual results:
Consumed: 0 out of Unlimited

Expected results:
Since I registered 2 content hosts, it should show:
Consumed: 2 out of Unlimited

Additional info:
Comment 2 Brad Buckingham 2016-03-14 17:59:25 UTC 
Created redmine issue http://projects.theforeman.org/issues/14192 from this bug
Comment 3 Brad Buckingham 2016-03-14 18:05:59 UTC 
Katello PR: https://github.com/Katello/katello/pull/5878
Comment 4 Bryan Kearney 2016-03-14 18:09:27 UTC 
Upstream bug component is Content Management
Comment 5 sthirugn@redhat.com 2016-03-24 18:26:53 UTC 
Verified in Satellite-6.2-beta-snap5.1

Navigate to Content -> Activation Keys -> Summary page shows 'Host Limit' = 8 out of Unlimited
Comment 8 errata-xmlrpc 2016-07-27 09:27:01 UTC 
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/RHBA-2016:1501