Bug 839101

Summary:	History limiting isn't working correctly
Product:	[Community] PulpDist	Reporter:	Nick Coghlan <ncoghlan>
Component:	Management CLI	Assignee:	Nick Coghlan <ncoghlan>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	unspecified
Target Milestone:	0.1.0
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-09-07 07:08:24 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:

Description Nick Coghlan 2012-07-10 23:53:46 UTC

The current test suite only tests the case of "python -m pulpdist.manage_repos history --num_entries 0".

Any value higher than zero is returning *all* entries instead of just the requested number.

Comment 1 Nick Coghlan 2012-07-12 05:10:46 UTC

Fixed for PulpDist 0.0.18

Comment 2 Nick Coghlan 2012-07-25 05:12:30 UTC

Expected behaviour: on a local mirror with more than 1 sync event in its history, the command "python -m pulpdist.manage_repos history -n 1 --mirror <mirror_id>" should display only the most recent entry, "-n 2" only two entries, etc, until all entries are displayed.

Comment 3 Nick Coghlan 2012-09-07 07:08:24 UTC

Fixed in 0.1.0