Bug #35457
closed
Investigation: does Katello properly remove content units when they are removed from a Pulp repository during syncing?
Added by Ian Ballou over 1 year ago.
Updated over 1 year ago.
Description
Custom repositories don't always keep every old content unit, so content units can be removed during syncs. An upstream user is hitting an issue where filtered CV publishing is failing due to content units in the DB that don't exist in Pulp. I think it's likely that Pulp removed the units during a sync but Katello failed to remove them from its DB.
We should test that, if a repo removes content units, Katello also removes them from the DB. We should also test this for package groups because they were the target content unit type in the issue.
Perhaps we could improve filtered content view publishing so that 404s are handled. That might require Pulp changes, but it's worth investigating.
- Triaged changed from No to Yes
This issue seems to be more specific to package groups than we originally thought.
The user has reported that, at sync time of EPEL-next, a package group got updated. In Pulp, a new package group content unit was created and it was indexed by Katello into the repository. Eventually, some weeks later, it seems the duplicate disappears from Pulp and causes filtered CV publishing issues due to the orphan left in the Katello repo.
I'm guessing that orphan cleanup may be deleting the repository version that held the old package group. I propose that we should try to reproduce it and update the existing package group rather than keeping around the old duplicate if the package group receives an update. That is what we do for errata.
- Status changed from New to Duplicate
- Is duplicate of Bug #35120: Retain packages on Repository removes RPMs from Pulp but not from Katello added
- Target version changed from Katello 4.5.1 to Katello Recycle Bin
Also available in: Atom
PDF
Updated by