Description of problem:
Content view include package filter not working as expected while matching the version. When a content view filter is created for a package for e.g "xorg-x11-drv-vmmouse" from RHEL7 Server repository with version equal to "13.0.0-11.el7" it will include all the packages that have the version pattern matching to "13.0.0" in their name . See below
In the issue this the filter for package xorg-x11-drv-vmmouse equals version "13.0.0-11.el7" matches all the above packages when it should only match xorg-x11-drv-vmmouse-13.0.0-11.el7.x86_64.rpm . The issue occurs for other packages too.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a content-view with RHEL7 Server repository.
2. Create an Include filter for package xorg-x11-drv-vmmouse that equals to version "13.0.0-11.el7" . And publish a new version. The published version should only contain a single included package. However it contains extra packages as mentioned in the bug description.
The pattern matching within content view filters for package version does not works and includes redundant packages.
Content View should only contain the included packages.
THe issue seems that version is only matched for string before the "-" in the package name.
Setting the flags.
Confirmed this works correctly in 6.1.11 and fails as described in the bug in 6.2.10. Working to determine if this was recently introduced by testing on 6.2.8
Confirmed this also occurs with 6.2.8.
The issue is that we aren't parsing the Release field when doing the filter.
found a related bugzilla: 1395642
related redmine: http://projects.theforeman.org/issues/17916
err bug 1395642
upstream patch: https://github.com/Katello/katello/commit/bafd8b82c581ef87add58af25b37b1ff9ace07d9
This is actually a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1395642 which is already resolved.
Will be releasing HOTFIX packages on the above mentioned bug and closing this out as a duplicate.
Follow 1395642 for updates.
*** This bug has been marked as a duplicate of bug 1395642 ***