Red Hat Bugzilla – Bug 847115
Extend scroll bug on content tab, with > 50 subscriptions only the first 50 will populate.
Last modified: 2013-03-27 16:54:00 EDT
Description of problem: With a headpin deployment that has 289 subscriptions, only the first 50 subscriptions can be acquired in the left pane of the tupane view. Version-Release number of selected component (if applicable): katello-1.0.4-1 How reproducible: Occurs in both Firefox (Linux) and IE9 (Windows 7). Steps to Reproduce: 1. Populate your deployment with a hundred or so subscriptions. 2. Navigate to the content tab and scroll down the left pane. Actual results: The first 25 subs will populate, scroll down and a spinner is present waiting for the next 25 to load. Once these 25 subs have loaded you will notice that you have 50 of xxx subs in your view. If you scroll down you will find that the spinner does not appear again nor do any additional subs.
Created attachment 603329 [details] 50 of xxx results with no way to get to the remaining 239
Fixed in fce26f0
Hi Pavel, Eric Could you please share a subscription manifest that includes more than 50 subscriptions to test this defect. thanks
Hi Eric, I tried the same manifest as you sent with name "vmrhsam-manifest.zip". But After importing this manifest, the UI shows only 9 subscriptions in total in left pane. Please see the attachment. Could you please share any dummy manifest that includes more than 50 subscriptions.
Created attachment 619622 [details] looks like "vmrhsam-manifest.zip" has only 9 subscriptions in total
I tried again, but I think to list more than 50 subscriptions, first, few system needs to be registered and some subscriptions needs to be consumed by these systems. I did the same and now I can see the 79 subscriptions. I can scroll down more than 50 subscriptions, spinner is loading with bunch of 25 subscriptions in one go in the left pane of 'subscription' tab.
Created attachment 625899 [details] On scroll, UI loads 79 subscriptions
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. http://rhn.redhat.com/errata/RHSA-2012-1543.html