Summary: | Errata counts aren't similar between the satellite content-hosts view and the export csv | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Anand Agrawal <aagrawal> |
Component: | Hosts - Content | Assignee: | Anand Agrawal <aagrawal> |
Status: | CLOSED ERRATA | QA Contact: | Stephen Wadeley <swadeley> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.4.2 | CC: | aagrawal, aymeric.marchal, mshimura, rcavalca, zhunting |
Target Milestone: | 6.6.0 | 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: | 2019-10-22 19:49:43 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: |
Description
Anand Agrawal
2019-04-25 04:20:23 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26678 has been resolved. Hello Testing on 6.5 to reproduce the problem [root@cloud-qe-21 ~]# rpm -q tfm-rubygem-katello tfm-rubygem-katello-3.10.0.46-1.el7sat.noarch I see column: Installable Updates Security, Bug Fix, Enhancement, Package Updates 2 0 0 2 Click "Export", open CSV file, view columns: Installable Updates - Security 0 <--- Does not match GUI text. Installable Updates - Bug Fixes 0 Installable Updates - Enhancements 0 Installable Updates - Package Count 2 Will test again after upgrade to latest snap. Hello Testing on system updated to latest snap [root@cloud-qe-21 ~]# rpm -q tfm-rubygem-katello tfm-rubygem-katello-3.12.0.rc2-11.master.el7sat.noarch Reloaded web UI, GUI text still as in comment 5 Exported CSV file again I see "Installable Updates - Security" column is now 2 this is the same as the GUI text. Its Correct now. Thank you 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 |