Bug 2137318

Summary:	hammer content-view purge only deletes up to "Entries per page" versions
Product:	Red Hat Satellite	Reporter:	Julio Entrena Perez <jentrena>
Component:	Content Views	Assignee:	Chris Roberts <chrobert>
Status:	CLOSED ERRATA	QA Contact:	Sam Bible <sbible>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.11.3	CC:	apatel, chrobert, kgaikwad, ofedoren, pcreech, rabajaj, sbible
Target Milestone:	6.13.0	Keywords:	Triaged, UserExperience
Target Release:	Unused
Hardware:	All
OS:	Linux
URL:	https://projects.theforeman.org/issues/35750
Whiteboard:
Fixed In Version:	rubygem-hammer_cli_katello-1.7.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-03 13:22:26 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 Julio Entrena Perez 2022-10-24 12:39:35 UTC

Description of problem:
Running "hammer content-view purge --id <id>" on a content view with 1,000 versions only deletes 16 versions.

The output shows that the command only deletes up to one page of versions and ignores the rest.
Customer being forced to re-run the command multiple times and/or increase the number of "Entries per page" at Administer -> Settings -> General, which affects everything else in the Satellite.

Version-Release number of selected component (if applicable):
tfm-rubygem-hammer_cli-3.1.0.1-1.el7sat

How reproducible:
Always

Steps to Reproduce:
1. Create 100 versions of a CV
2. Run "hammer content-view purge --id <id>"
3.

Actual results:
Only 16 versions are deleted (with the default "Entries per page" value of 20).

Expected results:
97 versions are deleted regardless of the value of "Entries per page".


Additional info:
hammer should iterate through the pages and delete all versions as requested in a single execution of the command.
Nowhere in the help of the command or the Satellite documentation states that the command is limited to a single page.

Comment 1 Bryan Kearney 2022-11-21 20:03:30 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35750 has been resolved.

Comment 4 Sam Bible 2023-02-20 23:17:56 UTC

Tested on 6.13 - Snap 11

Steps Tested:
1) Create a content view, and publish 101 versions
2) Run "hammer content-view purge --id <cvid>

Expected Results:
97 versions are purged.

Actual Results:
97 versions were purged. 

Note:
The default per page value was unchanged, at 20.

Comment 7 errata-xmlrpc 2023-05-03 13:22:26 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 (Important: Satellite 6.13 Release), 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-2023:2097