Bug #37708
closedDeb Content View Filter bug
Description
Hello,
When applying a deb content filter to an Ubuntu repository, the repository is transformed from a structured repository to a simple repository. This causes the smart proxy synchronization to fail.
This can be reproduced by creating a product:
Content => Products => Ubuntu 20.04.6 LTS => Repositories => New Repository
Name = Base
Type = deb
Upstream URL = http://archive.ubuntu.com/ubuntu/
Releases/Distributions = focal
Component = main restricted multiverse universe
Architecture = amd64
Download Policy = On Demand
Mirroring Policy = Additive
Save
Then creating a content view:
Content => Lifecycle => Content Views => Create content view
Name = Test
Solve Dependencies = Checked
Create content view
Adding the repository to the content view:
Content => Lifecycle => Content Views => Test => Repositories => Show Repositories
Select Base from Ubuntu 20.04.6 LTS
Add Repositories
Adding an include filter to the content view:
Content => Lifecycle => Content Views => Test => Filters => Create Filter
Name = Whitelist
Content Type = Deb
Include Filter
Create filter
Then add any rule, the rule I added was name = emacs*, then publish, then promote. The promotion will trigger a sync to smart-proxies and the sync will fail with:
Could not find a Release file at 'https://foreman.domain.com/pulp/deb/ORG/Alpha/Test/custom/Ubuntu_20_04_6_LTS/Base/dists/focal
With no filter, focal exists. With a filter there is only a dists/default path, the filter removes the dists/focal path and the smart-proxy expects it.
Thanks,
TJ
Updated by Ian Ballou over 1 year ago
Should be triaged by Debian content maintainers.
Updated by Markus Bucher over 1 year ago
- Related to Feature #35959: Replace simple publisher with structured publisher for Debian Repositories added
Updated by Markus Bucher over 1 year ago
- Triaged changed from No to Yes
Thanks for the detailed report TJ.
This bug should automatically be fixed with #35959, because it makes structured publishing the default for APT-repositories.
Updated by Chris Roberts over 1 year ago
- Target version changed from Katello 4.15.0 to Katello 4.16.0
Updated by Quinn James about 1 year ago
- Target version changed from Katello 4.16.0 to Katello 4.17.0
Moving to 4.17.0 due to 4.16.0 GA.
Updated by Quirin Pamp about 1 year ago
I think this is a duplicate of https://projects.theforeman.org/issues/38061, which is fixed in Katello 4.16.0.
Updated by Quirin Pamp about 1 year ago
- Is duplicate of Bug #38061: Using deb content filters with structured APT enabled breaks repo publications added
Updated by Quirin Pamp about 1 year ago
ยท Edited
I am pretty much certain this is caused by the same underlying issue we fixed in 4.16.0 under the issue https://projects.theforeman.org/issues/38061
The fix will not fix existing CV versions. But all future CV versions created after the fix is applied should work as expected.
Updated by Pavan Soma Shekar 10 months ago
- Target version changed from Katello 4.17.0 to Katello 4.19.0
Updated by Pavan Soma Shekar 21 days ago
- Status changed from Need more information to Closed
Updated by Pavan Soma Shekar 21 days ago
- Status changed from Closed to Duplicate