"Erratum - Date and Type" inclusion filter seems to be ignoring end date parameter

Problem:
“Erratum - Date and Type” inclusion filter seems to be ignoring end date parameter

Expected outcome:
Erratum included by filter respects the end date specified.

Foreman and Proxy versions:
Foreman 2.5.4

Distribution and version:
CentOS 7

Other relevant data:
I have two filters on a content view:

# hammer content-view filter list --content-view-id 5
----------|-----------------------------|-------------|---------|----------
FILTER ID | NAME                        | DESCRIPTION | TYPE    | INCLUSION
----------|-----------------------------|-------------|---------|----------
11        | All Packages without Errata |             | rpm     | true     
12        | Errata by Date              |             | erratum | true     
----------|-----------------------------|-------------|---------|----------

Here’s the info on the filters themselves:

# hammer content-view filter info --content-view-id 5 --id 11
Filter ID:    11
Name:         All Packages without Errata
Type:         rpm
Inclusion:    true
Description:  
Repositories: 

Rules:

# hammer content-view filter info --content-view-id 5 --id 12
Filter ID:    12
Name:         Errata by Date
Type:         erratum
Inclusion:    true
Description:  
Repositories: 

Rules:        
 1) Id:         9706
    Start Date: 2010-01-01T00:00:00.000Z
    End Date:   2021-01-01T00:00:00.000Z
    Types:      security, enhancement, bugfix
    Created:    2021/11/24 22:50:28
    Updated:    2021/11/24 22:50:56

Based on filter ID 12, I would expect only errata updated before 2021-01-01 to be included in the content view. However, that is not what I am seeing. Instead, I see all errata being included.

# hammer content-view version list --content-view-id 5
---|---------------|---------|------------------------------------|-----------------------
ID | NAME          | VERSION | DESCRIPTION                        | LIFECYCLE ENVIRONMENTS
---|---------------|---------|------------------------------------|-----------------------
21 | Date Test 2.0 | 2.0     | Up to 2021-01-01.                  | Library               
20 | Date Test 1.0 | 1.0     | Added all packages without errata. |                       
---|---------------|---------|------------------------------------|-----------------------
# hammer erratum list --content-view-id 5 --content-view-version-id 21
-----|----------------|-------------|----------------------------------------------------------------------------------|------------|-----------
ID   | ERRATA ID      | TYPE        | TITLE                                                                            | ISSUED     | UPDATED   
-----|----------------|-------------|----------------------------------------------------------------------------------|------------|-----------
7904 | RHSA-2021:4798 | security    | Important: kpatch-patch security update                                          | 2021-11-23 | 2021-11-23
7900 | RHBA-2021:4775 | bugfix      | mdadm bug fix and enhancement update                                             | 2021-11-23 | 2021-11-23
7898 | RHBA-2021:4776 | bugfix      | ksh bug fix and enhancement update                                               | 2021-11-23 | 2021-11-23
7897 | RHBA-2021:4797 | bugfix      | qemu-kvm bug fix and enhancement update                                          | 2021-11-23 | 2021-11-23
7895 | RHBA-2021:4789 | bugfix      | kbd bug fix and enhancement update                                               | 2021-11-23 | 2021-11-23
[...]

Am I not setting up the erratum filter correctly? I feel like I’m missing something simple here.

Thank you for your time!

Tested Foreman 3.01 and these errata filters work as expected there. So, at least in my experience, this issue seems to be limited to Foreman 2.5.4.

2 Likes