Description of problem:

In Red Hat Satellite 6.16.1-1, the "Host - Applied Errata" report shows all errata that are already applied on a content host irrespective of the date specified when generating the report.

How reproducible:

Always.

Is this issue a regression from an earlier version:

No.

Steps to Reproduce:

1. Generated the "Host - Available Errata" report for a specific content host. 142 errata were listed in the report.

 2. Generated the "Host - Applied Errata" report for the same content host. Zero errata were listed in the report since no errata have been applied to the host yet.

 3. Applied the errata on the host, and generated another "Host - Applied Errata" report.

This time, there are 10,673 errata listed in the report.

 4. Performed a repo sync from the Red Hat CDN to the Satellite 6.16.1-1 server, then generated a new "Host - Available Errata" report for the same host. The report listed 13 additional errata.

 5. Applied the 13 additional errata to the host, and generated a new "Host - Applied Errata" report. The report lists 21,459 errata.

Actual behavior:

Refer to the 'Steps to Reproduce' section above.

Expected behavior:

With the proper dates selected, the "Host - Available Errata" report for a specific content host should list only the errata that have been applied since that date rather than all the errata that have been applied on the host.

Business Impact / Additional info:

Impacts the customer's patching workflow as they generate the "Host - Available Errata" report before patching a specific content host. and after patching the host, they generate the "Host - Applied Errata" report and expect the 2 reports to match.