Project

Profile

Help

Issue #6151

closed

associate-with-filter sometimes ends up with filtered-rpms in the destination

Added by ggainey about 4 years ago. Updated about 4 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
2.21.0
Platform Release:
2.21.1
OS:
Triaged:
Yes
Groomed:
Yes
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Sprint 66
Quarter:

Description

Description of problem: Creating a filter to exclude a package with a higher version that has multiple versions doesn't work properly on conservative dep-solving.

Version-Release number of selected component (if applicable): 2-master

How reproducible: 100%

Steps to Reproduce:

  1. Turn dependency solving to conservative.
  2. Create and sync custom repo.
  3. Create cv with depsolving on and add custom repo.
  4. Create exclusion filter and exclude a package (walrus) with a higher version
  5. Publish CV
  6. Check rpm package list for that version

Actual results: walrus 0.71 and 5.21 are present in rpm packages list.

Expected results: walrus 0.71 is the only package present in rpm packages list.

Additional info: Without depsolving, the filtering function works as expected.

Works as expected in 2.19


Files

reproducer (2.12 KB) reproducer Reproducer scripts - shows both walrus versions end up in repo ggainey, 02/12/2020 09:13 PM

Also available in: Atom PDF