Project

General

Profile

Bug #17362

Content view filter cannot distinguish between multiple packages with the same version but different release number

Added by Marcel Gazdík almost 3 years ago. Updated about 1 year ago.

Status:
Ready For Testing
Priority:
Normal
Category:
Content Views
Target version:
Difficulty:
medium
Triaged:
Yes
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

Description of problem:
In case there are multiple packages of the same version but different package release version in a repository and if this repository is included in a content view with "rpm version filter" they are not being properly filtered and all the packages are being included in the cv regardless their release version.

Ex:

List of packages in repo:
  test_rpm-0.0.1-1.el7.noarch.rpm
  test_rpm-0.0.1-10.el7.noarch.rpm
  test_rpm-0.0.1-2.el7.noarch.rpm
  test_rpm-0.0.1-4.el7.noarch.rpm
  test_rpm-0.0.1-5.el7.noarch.rpm

Filters:
content-view filter list --organization-id 1 --content-view-id 4
----------|------------|------|----------
FILTER ID | NAME       | TYPE | INCLUSION
----------|------------|------|----------
1         | includepkg | rpm  | true     
----------|------------|------|----------

content-view filter rule list --organization-id 1 --content-view-id 4 --content-view-filter-id 1
--------|-----------|-----------|--------------|-----------------|-----------------|-----------|------------|---------
RULE ID | FILTER ID | NAME      | VERSION      | MINIMUM VERSION | MAXIMUM VERSION | ERRATA ID | START DATE | END DATE
--------|-----------|-----------|--------------|-----------------|-----------------|-----------|------------|---------
4       | 1         | test_rpm  | 0.0.1-4.el7* |                 |                 |           |            |         
--------|-----------|-----------|--------------|-----------------|-----------------|-----------|------------|---------

With this setup, all the packages listed above will be included in the newly published CV

Version-Release number of selected component (if applicable):
6.2.x (6.1.x as well)

How reproducible:
1) Create product, repository and some fake packages with same version but different release versions (see example above)
2) Create content view, add the repo from step #1 into it and create filter based on the example above
3) Publish the CV and check results

Actual results:
All package packages of the same version but different release are being included

Expected results:
Only specific package version(s) should be included

History

#1 Updated by The Foreman Bot almost 3 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/6456 added

#2 Updated by Justin Sherrill almost 3 years ago

  • Legacy Backlogs Release (now unused) set to 197

#3 Updated by Eric Helms over 2 years ago

  • Legacy Backlogs Release (now unused) changed from 197 to 208

#4 Updated by John Mitsch over 2 years ago

  • Legacy Backlogs Release (now unused) changed from 208 to 214

#5 Updated by Justin Sherrill over 2 years ago

  • Legacy Backlogs Release (now unused) changed from 214 to 222

#6 Updated by Justin Sherrill about 2 years ago

  • Legacy Backlogs Release (now unused) deleted (222)

#7 Updated by Eric Helms about 2 years ago

  • Legacy Backlogs Release (now unused) set to 114

Also available in: Atom PDF