Bug 2011528

Summary:	Errata changing in the upstream repo is not being reflected in the Katello DB
Product:	Red Hat Satellite	Reporter:	Ian Ballou <iballou>
Component:	Repositories	Assignee:	Ian Ballou <iballou>
Status:	CLOSED ERRATA	QA Contact:	Cole Higgins <chiggins>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.8.0	CC:	myarboro, pcreech, zhunting
Target Milestone:	6.10.1	Keywords:	Reopened, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-katello-4.1.1.37-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-01-05 12:49:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ian Ballou 2021-10-06 18:14:23 UTC

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

Comment 1 Ian Ballou 2021-10-06 18:14:27 UTC

Created from redmine issue https://projects.theforeman.org/issues/33648

Comment 2 Ian Ballou 2021-10-06 18:14:28 UTC

Upstream bug assigned to None

Comment 5 Brad Buckingham 2021-10-12 15:56:28 UTC

Moving to POST as the upstream PR is merged.

Comment 8 mark yarborough 2021-10-14 14:53:20 UTC

Please include in 6.10.1

Comment 19 errata-xmlrpc 2021-11-18 14:38:46 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 (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 20 RHEL 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.