Bug #37708
openDeb 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 2 months ago
Should be triaged by Debian content maintainers.
Updated by Markus Bucher 2 months ago
- Related to Feature #35959: Replace simple publisher with structured publisher for Debian Repositories added
Updated by Markus Bucher 2 months 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.