Bug 1582049

Summary: Exclude filter for rpms: updating the filter rule from "Range" to "Greater than" causes no package excluded
Product: Red Hat Satellite Reporter: matt jia <mjia>
Component: Content ViewsAssignee: Justin Sherrill <jsherril>
Status: CLOSED ERRATA QA Contact: Perry Gagne <pgagne>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3.1CC: bbuckingham, mmccune, paji, pcreech, pgagne, syangsao
Target Milestone: 6.4.0Keywords: EasyFix, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 19:05:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
propose a patch none

Description matt jia 2018-05-24 05:34:26 UTC 
Description of problem:

Given a CV that is using an exclude filter for RPMS. The filter has a rule that is using version range on a package. After changing this rule to "Greater than",
no packages got excluded when publishing the CV. 


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


How reproducible:

Easy


Steps to Reproduce:
1. Create a CV with "Red Hat Enterprise Linux 7 Server RPMs x86_64 7Server " repo

2. Create an exclude fitler for kernel pacakge like this

Type: Exclude
RPM: kernel
Version "range": between 3.10.0-327.36.3.el7 and 3.10.0-693.36.3.el7

3. update the filter rule to:

Type: Exclude
RPM: kernel
Version "Greater than": 3.10.0-693.36.3.el7

4. publish the CV

Actual results:

Kernel 3.10.0-862.2.3.el7 is included 


Expected results:

Kernel 3.10.0-862.2.3.el7 should not be included because it is higher than 3.10.0-693.36.3  


Additional info:
Comment 1 matt jia 2018-05-24 07:13:20 UTC 
Created attachment 1440959 [details]
propose a patch

This is built on top of 3.4.5.64.
Comment 3 Partha Aji 2018-06-08 19:22:46 UTC 
Connecting redmine issue http://projects.theforeman.org/issues/23867 from this bug
Comment 4 Partha Aji 2018-06-08 19:28:31 UTC 
Connecting redmine issue http://projects.theforeman.org/issues/20876 from this bug
Comment 5 Satellite Program 2018-06-08 20:18:29 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20876 has been resolved.
Comment 6 Brad Buckingham 2018-06-11 12:22:55 UTC 
Aligning to 6.4, since the fix should already be in the release.
Comment 12 Bryan Kearney 2018-10-16 19:05:46 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2927