Red Hat Bugzilla – Bug 802772
Scalability Testing: conductor/deployments shows only 30 rows ... no link or indication that more deployments exist
Last modified: 2012-12-04 09:58:39 EST
Description of problem:
101 applications/instances were deployed to the same mock provider from one Conductor instance. All the instances are still in a 'running' state. If a user clicks on the conductor/deployments tab, the users sees only 30 of these active deployments. There is no indication that there are more to be viewed (like a link to page 2 or a double arrow or a 'viewing 30 of 101 applications' text).
(see attached screenshots)
As an example, in the attached screenshots, the user logged in has launched 2 of the 101 applications - only one is currently visible. Searching for the other application does work though :).
By contrast all 200 active users can be viewed on a single page by accessing conductor/users.
Steps to Reproduce:
1. Launch more than 30 instances from one conductor
2. Click on conductor/deployments
3. See that only 30 are visible
4. No link to further deployments
rpm -qa |grep aeolus
Created attachment 569680 [details]
Top of conductor/deployments screen
Created attachment 569681 [details]
Bottom of conductor/deloyments screen
Another pagination issue. 1.0.z.
Patch has been posted: https://fedorahosted.org/pipermail/aeolus-devel/2012-March/009652.html
This issue has been fixed. Please verify the commits: 5893ff7eac0f5b3fcc3e7769d0f642939570b13f, 81e7d84949d5bd93827272344b2a3f6c82cd96f2 and 13150b173efb856564bda68498cf826339a985c3
This fix also belongs to the series: ed2d9e887df3cb30639417eb0d342a3d7d9d39e6
>> rpm -qa |grep aeolus
conductor/deployments now uses pagination ... all instances are visible to the user through multiple pages ... see attached screenshot.
Marking this BZ verified.
Created attachment 615113 [details]
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.