Bug 1292692

Summary: "Download CSV" when searching for systems with given installed package gives me less rows than whats displayed on webUI
Product: Red Hat Satellite 5 Reporter: Jan Hutař <jhutar>
Component: WebUIAssignee: Grant Gainey <ggainey>
Status: CLOSED DUPLICATE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 570CC: tlestach, tomckay
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-18 20:26:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1358815    

Description Jan Hutař 2015-12-18 05:30:51 UTC
Description of problem:
"Download CSV" link when searching for systems with given installed package gives me less rows than what is displayed on webUI


Version-Release number of selected component (if applicable):
spacewalk-java-2.3.8-120.el6sat.noarch


How reproducible:
always


Steps to Reproduce:
1. Log into Sat5
2. Systems
3. Advanced Search
   1. Search for: curl
   2. Field to search: Installed Packages
   3. Where to Search: Search all systems
4. After some time I get a paginated result that lists "1 - 25 of 2,637"
5. At the bottom of the page there is a "Download CSV" button, when I
   click that I get a file with 138 lines only (header + 137 systems)


Actual results:
webUI indicates it found 2,637 matching systems, csv file contains only 137 systems. There is no traceback/message in the logs.


Expected results:
All systems visible on webUI are in the csv.


Additional info:
Originally reported by Ian Tewksbury <itewksbu> - thanks!

Comment 1 Bryan Kearney 2016-07-26 19:08:02 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 2 Grant Gainey 2017-01-18 20:26:14 UTC

*** This bug has been marked as a duplicate of bug 1098141 ***