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.
If an erratum changes in the upstream repo, Pulp will create a new advisory. Katello is not detecting this and is keeping the old erratum href, even if it no longer exists.
Steps to reproduce:
1) Use the python simple http server to host the "zoo" repo in the Katello source code's test/fixtures/test_repos
2) Sync that local repo
3) Edit an erratum (the title or description perhaps) in the repo's updateinfo.xml, delete everything in repodata, run ./create, and host again.
4) Sync the repo again using a complete sync. This forces content indexing to run.
5) Look at the erratum in the repository. Note that the erratum has not been updated with what you expect
6) To be extra sure a new erratum was generated, use the pulp cli to check the advisories in the repo's latest version. You should see that your edited erratum/advisory is correct in Pulp
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 (Satellite 6.10.1 Async 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/RHBA-2021:4737
Comment 20RHEL Program Management
2022-01-05 12:49:55 UTC
This bug was previously closed after it was shipped in the Red Hat Errata linked above. Unfortunately our workflow does not support re-opening bugs that have already been shipped. If you are still effected by this bug please open a new bug and reference this pre-existing Bugzilla and indicate that it does not appear to be resolved.