Project

General

Profile

Bug #17486

Content view filter version "Equals To" matching all packages instead of only one.

Added by Swapnil Abnave over 2 years ago. Updated about 1 year ago.

Status:
Duplicate
Priority:
Normal
Assignee:
Category:
Content Views
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

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-1.0-1.el7.x86_64
test-1.0-2.el7.x86_64
test-1.0-14.el7.x86_64
test-1.0-41.el7.x86_64

Filters:
[vagrant@centos7-hammer-devel hammer-cli-katello]$ hammer s localhost:3000 content-view filter list --organization-id 1 --content-view-id 7
----------|------------------|------|---------

FILTER ID | NAME | TYPE | INCLUSION
----------|------------------|------|----------
2 | include-4one-pkg | rpm | true
----------|------------------|------|----------

[vagrant@centos7-hammer-devel hammer-cli-katello]$ hammer s localhost:3000 content-view filter rule list --content-view-id 7 --content-view-filter-id 2
--------|-----------|------|-------------------|-----------------|-----------------|-----------|------------|--------

RULE ID | FILTER ID | NAME | VERSION | MINIMUM VERSION | MAXIMUM VERSION | ERRATA ID | START DATE | END DATE
--------|-----------|------|-------------------|-----------------|-----------------|-----------|------------|---------
2 | 2 | test | 1.0-41.el7.x86_64 | | | | |
--------|-----------|------|-------------------|-----------------|-----------------|-----------|------------|---------

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)

Steps to reproduce:
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 packages are being included

Expected results:
Only specific version(s) should be included. Package matching "Equals To => 1.0-41.el7.x86_64" should only be published in the version.

Content Views-version-4.png View Content Views-version-4.png 119 KB Swapnil Abnave, 11/25/2016 08:00 AM
Content%20views version 4

Related issues

Has duplicate Katello - Bug #17916: Content view filter cannot distinguish between multiple packages with the same version but different release numberClosed2017-01-03

History

#1 Updated by Swapnil Abnave over 2 years ago

  • Bugzilla link set to 1395642

#2 Updated by Eric Helms over 2 years ago

  • Legacy Backlogs Release (now unused) set to 208

#3 Updated by John Mitsch over 2 years ago

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

#4 Updated by Justin Sherrill over 2 years ago

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

#5 Updated by Justin Sherrill about 2 years ago

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

#6 Updated by Eric Helms about 2 years ago

  • Status changed from New to Assigned
  • Assignee set to Partha Aji
  • Legacy Backlogs Release (now unused) set to 267

#7 Updated by Eric Helms about 2 years ago

  • Status changed from Assigned to Duplicate

#8 Updated by Eric Helms about 2 years ago

  • Has duplicate Bug #17916: Content view filter cannot distinguish between multiple packages with the same version but different release number added

#9 Updated by Eric Helms almost 2 years ago

  • Legacy Backlogs Release (now unused) changed from 267 to 281

Also available in: Atom PDF