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
hammer- allow user to run Verify Content Checksum, on container repositories.
2. What is the nature and description of the request?
Verify Content Checksum on Container repositories can only be performed via satellite GUI.
On yum type repositories, Verify Content Checksum can be performed via GUI as well as using the hammer.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# hammer repository synchronize --validate-contents true --help
Usage:
hammer repository synchronize [OPTIONS]
Options:
--validate-contents BOOLEAN Force a sync and validate the checksums of all content. Only used with yum repositories.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Need the same functionality for the Container repositories.
3. Why does the customer need this? (List the business requirements here)
Easy of use, so that customers can execute Verify Content Checksum using the hammer on Container repositories via CLI without Navigating to each repositories page in the
satellite GUI.
4. Is there already an existing RFE upstream or in Red Hat Bugzilla?
n/a
5. Does the customer have any specific timeline dependencies and which release would they like to target?
Asap
6. Is the sales team involved in this request and do they have any additional input?
n/a
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.14 security and bug fix update), 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:6818
1. Proposed title of this feature request hammer- allow user to run Verify Content Checksum, on container repositories. 2. What is the nature and description of the request? Verify Content Checksum on Container repositories can only be performed via satellite GUI. On yum type repositories, Verify Content Checksum can be performed via GUI as well as using the hammer. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ # hammer repository synchronize --validate-contents true --help Usage: hammer repository synchronize [OPTIONS] Options: --validate-contents BOOLEAN Force a sync and validate the checksums of all content. Only used with yum repositories. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Need the same functionality for the Container repositories. 3. Why does the customer need this? (List the business requirements here) Easy of use, so that customers can execute Verify Content Checksum using the hammer on Container repositories via CLI without Navigating to each repositories page in the satellite GUI. 4. Is there already an existing RFE upstream or in Red Hat Bugzilla? n/a 5. Does the customer have any specific timeline dependencies and which release would they like to target? Asap 6. Is the sales team involved in this request and do they have any additional input? n/a