Bug 1965379
| Summary: | Applied Errata Reports Are No Longer Generating Correctly | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | myoder |
| Component: | Reporting | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED DUPLICATE | QA Contact: | Lukáš Hellebrandt <lhellebr> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.8.0 | CC: | dmatoule, mhulan, oprazak, wclark |
| Target Milestone: | Unspecified | Keywords: | 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: | 2021-06-16 15:28:32 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: | |||
*** This bug has been marked as a duplicate of bug 1941096 *** I closed this as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1941096 However please note, it also describes some behavior in https://bugzilla.redhat.com/show_bug.cgi?id=1954409 (date range filters not working correctly) |
Description of problem: Issue was first noticed trying to generate an applied errata report for content hosts between a certain date range (5-12-2021 to 5-19-2021). The report showed applied erratas for only one host, and the date is showing 4-27-2021. This report was working previously, as this has been used for accounting purposes for management to see hosts that have had erratas applied. I saw 2 of the working reports. One of the reports showed 207 erratas applied to different hosts on 5/4/2021. The other report showed 109 applied erratas for different hosts on 5/11/2021. The most recent report that isn't working correctly, shows 26 erratas applied to one host only on 4/27/2021. I have confirmed several hosts have applied erratas successfully via remote execution on 5-13-2021. And these same hosts were showing successfully in reports generated earlier. We have tried with the hammer command to generate reports, and it is doing the same thing. We created an input.json file for all successful erratas applied, with restart yes, and all errata types. Something like this: {"Status": "success", "Include Last Reboot": "yes", "Filter Errata Type": "all", "Since": "5 weeks ago", Up to": "1 day ago"} And any hammer command with the "Since" value as 5 weeks or more (we tried up to 10 weeks), all we see is this: [root@satellite tmp]# hammer report-template generate --id 114 --report-format csv --inputs=/tmp/input.json date,hostname,erratum_id,erratum_type,status 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:3908,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:4072,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:5350,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:4907,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:4011,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:3864,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:4041,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:3996,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:3916,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:4026,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:5009,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:3848,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:3978,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:3952,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2021:0153,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:5002,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:3915,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:4032,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:4076,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:3878,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:3911,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:3901,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:4003,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:5566,security,success 2021-04-27 21:16:29 UTC,host1.example.com,RHSA-2020:4005,security,success It seems we can't see previously applied erratas, or recent erratas. As if something is stuck on this particular host. We have also tried a number of combinations of the "Status", "Include Last Reboot", "Filter Errata Type" and the date ranges from UI to display recent erratas. We are unable to generate any thing other than this one host from 4-27. Version-Release number of selected component (if applicable): Satellite 6.8.4 How reproducible: via customer side, always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: