TLDR: Setup a Content View filter to include all errata up until the end of 2017 and you still get 2018 errata showing up in the published Content View. There are situations where Red Hat has to ship a package a multiple times in multiple erratas over long periods of time. This means you can find situations where an errata with a specific NVREA shipped in 2017 and is then shipped *again* in 2018 or some other later date. Examples of this are: 1) docker-distribution-2.6.2-1.git48294d9.el7.x86_64.rpm exists in both: RHEA-2018:1063 RHSA-2017:2603 2) driverctl-0.95-1.el7.noarch.rpm exists in both: RHEA-2018:1063 RHEA-2017:2370 This causes includes filters to improperly 'pull in' later errata even thou the date filter may say to limit up to the end of 2017. Steps to reproduce: 1) sync RHEL 7Server x86_64 Extras 2) setup a CV that includes above repo 3) Setup an Includes Filter that has: * NULL start date * End date of DEC-17-2017 4) publish CV 5) note that you will see RHEA-2018:1063 in the published content view even thou your filter said to only include up to DEC of 2017.
WORKAROUND: Switch to an Excludes filter that is the inverse of the includes
Do you have any update about the bug against the errata tool?
Hi Mike, Do you happen to know if the bug for errata tool was created based upon comment 6?
https://bugzilla.redhat.com/1627844
Connecting redmine issue https://projects.theforeman.org/issues/26720 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26720 has been resolved.
Steps to test: Note: driverctl-0.95-1.el7.noarch.rpm has following errata: RHEA-2018:1063 RHEA-2017:2370 1) sync RHEL 7Server x86_64 Extras 2) setup a CV that includes above repo 3) Setup an Includes Filter that has: * NULL start date * End date of DEC-17-2017 4) publish CV 5) Drill into version -> errata 6) Search for RHEA-2018:1063 Expected Result RHEA-2018:1063 not present in list Actual Result: RHEA-2018:1063 not present in list Marking issue as verified. Tested on 6.6.0 snap 12
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-2019:3172
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days