Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
1. Proposed title of this feature request
[RFE] To have "reclaim-space" option introduced for "hammer capsule content" command.
2. What is the nature and description of the request?
Modofication of hammer-cli-katello related code to include a hammer based option and allow running reclaim-space operation on any external capsule server from command line
3. Why does the customer need this? (List the business requirements here)
For Repository, we have a reclaim space option present in UI, API as well as in hammer.
For external capsules, Only UI and API, have the options but hammer still does not have the feature included. As hammer is much easy touse than executing an API call, It is highly recommended to have the "reclaim-space" option introduced in "hammer capsule content" command.
4. How would the customer like to achieve this? (List the functional requirements here)
# hammer capsule content reclaim-space --id X
Executing this command should trigger the Actions::Pulp3::CapsuleContent::ReclaimSpace task as expected for capsule with ID X.
It should be possible to trigger task in both Sync and Async manner.
5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Same as above
6. Is there already an existing RFE upstream or in Red Hat Bugzilla?
No
7. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
As soon as possible
8. Is the sales team involved in this request and do they have any additional input?
No
9. List any affected packages or components.
rubygem-hammer_cli_katello
10. Would the customer be able to assist in testing this functionality if implemented?
Yes and so as the RH support
11. Additional information:
NA
Verified on 6.15 - Snap 5
Steps to Verify:
1. Register a Capsule, and sync some content.
2. Execute the hammer capsule content reclaim-space command
Expected Results:
Hammer allows you to reclaim-space, and has the appropriate options available (--async, --id, --name, --help) and the command successfully runs the reclaim-space task on the Capsule.
Actual Results:
Hammer allows you to reclaim-space, and has the appropriate options available (--async, --id, --name, --help) and the command successfully runs the reclaim-space task on the Capsule.
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.15.0 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-2024:2010