Bug 1269116 - Database indexes and tables pages display only one row per page
Summary: Database indexes and tables pages display only one row per page
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.5.0
Assignee: Greg Piatigorski
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-06 11:44 UTC by Taras Lehinevych
Modified: 2016-08-03 01:33 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-08 13:35:32 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Index tab (30.45 KB, image/png)
2015-10-06 11:44 UTC, Taras Lehinevych
no flags Details
Index tab displaying multiple rows (263.16 KB, image/png)
2015-10-08 21:54 UTC, Greg Piatigorski
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:2551 0 normal SHIPPED_LIVE Moderate: CFME 5.5.0 bug fixes and enhancement update 2015-12-08 17:58:09 UTC

Description Taras Lehinevych 2015-10-06 11:44:25 UTC
Created attachment 1080206 [details]
Index tab

Description of problem:
When you open the tabs Indexes or Tables you are able to see only one row, however the indicator in the bottom of page shows that there are more than 100 items, and option "per page" is set to 20.

Version-Release number of selected component (if applicable):
5.5.0.3

How reproducible: 100%


Steps to Reproduce:
1. Configure -> Configuration -> Database (accordion) -> Indexes (tab) 
   or
   Configure -> Configuration -> Database (accordion) -> Tables (tab)
2. Check the output form 

Actual results:
You are able to see only one row per page

Expected results:
You should see the rows according to the item per page option 

Additional info: In two cases the number of items was higher than set in "per page" option and also changing the option "per page" has influence on output number of rows but set value doesn't correspond to displayed number of rows.

Comment 2 Dave Johnson 2015-10-08 15:57:39 UTC
Taras, can you compare to 5.4 and see if its been there for a bit or is something new to 5.5 please.  Thanks!

Comment 3 Taras Lehinevych 2015-10-08 16:04:43 UTC
5.4.3.0 -> reproduce only the case with Indexes tab.
5.5.0.3 -> reproduce for both Indexes and Table tabs as mentioned in description

Comment 4 Greg Piatigorski 2015-10-08 21:54:40 UTC
Created attachment 1081104 [details]
Index tab displaying multiple rows

Taras, we had prior other ticket fixes related to Rails 4, which then also fixed database settings displays for both Tables ad Indices. I am attaching screen shot from a just rebased trunk (master) showing both tabs displaying more than 1 row, as expected. 

Need more info to see what's going on, can you provide an appliance I log into to understand what the problem may be.

TIA.

Comment 5 Taras Lehinevych 2015-10-26 11:54:16 UTC
Dear Greg, 

I re-checked this bug on 5.5.0.3 and there both Tables and Indexes tabs display more than one row. However on 5.5.0.7 bug is reproduced successfully ( https://10.16.5.128/ops/explorer) I didn't do any manipulations, just created a new appliance and go to Configure -> Configuration -> Database (accordion) -> Indexes (tab). 


P.S. I'm sorry for late response.

Comment 6 Taras Lehinevych 2015-11-03 12:47:57 UTC
Verified fixed in version 5.5.0.8

Current bug was check on 5.5.0.7, 5.5.0.8  and upstream and both Tables and Indices are displayed correctly. Based on comment from Greg Piatigorski 
"Taras, we had prior other ticket fixes related to Rails 4, which then also fixed database settings displays for both Tables ad Indices." I change the status of bug to verified.

Comment 8 errata-xmlrpc 2015-12-08 13:35:32 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/RHSA-2015:2551


Note You need to log in before you can comment on or make changes to this bug.