Bug 1278871 - change paginator # of items issue
Summary: change paginator # of items issue
Keywords:
Status: CLOSED DUPLICATE of bug 1277993
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.5.0
Assignee: Martin Hradil
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-06 15:38 UTC by Dave Johnson
Modified: 2015-11-11 20:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-10 16:23:18 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot (61.44 KB, image/png)
2015-11-06 15:38 UTC, Dave Johnson
no flags Details

Description Dave Johnson 2015-11-06 15:38:34 UTC
Created attachment 1090709 [details]
screenshot

Description of problem:
=============================
Test automation hit a issue when trying to navigate to a VM from the provider summary page.  After clicking the VM relationship, the testauto would change the # of items per page but nothing happens but a brief spinner.  If you click next, you'll see something like "(Items 21-4 of 4)".  Also, I was on VMs, after clicking next, the page title shows "provider_name (All Hosts)"


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


How reproducible:
====================
100%


Steps to Reproduce:
=======================
1.  manage a provider with 30+ vms
2.  go to provider summary, click on VMs
3.  paginator defaults to 1-20, change to 50 items per page
4.  see the spinner, nothing changes, still 1-20
5.  click next, more ugliness

Comment 2 Dave Johnson 2015-11-06 15:42:27 UTC
I also meant to mention, if you navigate straight to Virtual Machines sub tab under Infrastructure tab, pagination seems to work fine.  Its only when you navigate from the provider summary relationships that you see this.


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