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.
As part of https://projects.theforeman.org/issues/25400, we removed the flag force_yum_metadata_regeneration. We need to modify the behavior of the same in CV publish to force metadata generate every time.
Steps to retest:
1. Add a repository and sync
2. Verify the checksum type on the repo.
3. Check the environment on capsule you intend to test with.
4. Add the repository to content view and publish, promote to an env tied to a capsule.
5. Sync the capsule.
6. Verify the checksum type is correct on synced cv repo on capsule.
7. Update the checksum type on the repo and sync the repo.
8. Re-publish/ re-promote to cv tied to capsule's environment.
8. Sync capsule
9. Verify that the checksum type is correctly updated for the cv repo on the capsule.
Started off with sha256 and verified that it's both on satellite and capsule. After updating the checksum to sha1, I verified that the satellite and capsule has sha1 on it.
Marking issue as verified. Tested on 6.5.0_24
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, 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-2019:1222