Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 599858 [details]
showing the rendering of the content tab / subscriptions.

Description of problem:
During testing of loading and subscribing 255 systems it was discovered that after the job's completion the subscriptions on the content tab were rendered incorrectly.

Version-Release number of selected component (if applicable):
katello-all-0.2.45-1.git.35.049d74c.fc16.noarch

How reproducible:
Additional testing to see if this is reproducible

Steps to Reproduce:
1. Provision F16
2. yum install -y katello-all
3. katello-configure --deployment=headpin
4. Load a manifest into ACME_Corporation
5. /usr/share/katello/scripts/test/populate-systems.py --url=https://fqdn/headpin -n 255
  
Actual results:
See screenshot attached

Expected results:
Correct rendering of subscriptions and consumed X of XXX values.

This isn't really load issue, it is just an issue that the Subscriptions page needs better organization when you have lots of systems that each have their own unique subscription.

This should be a RFE/backlog item because the system is acting as designed, although somewhat confusing.

This is working as designed. Some thought is warranted in how to better show related subscriptions. Task added to backlog.