Project

General

Profile

Actions

Bug #37708

open

Deb Content View Filter bug

Added by TJ Guthrie 4 months ago. Updated 4 months ago.

Status:
New
Priority:
High
Assignee:
-
Category:
Content Views
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

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


Related issues 1 (0 open1 closed)

Related to Katello - Feature #35959: Replace simple publisher with structured publisher for Debian RepositoriesClosedBernhard SuttnerActions
Actions

Also available in: Atom PDF