Description of problem: We had errata for content host before upgrade and we were able to apply them on host on satellite 6.2.12 . But after upgrade to satellite 6.3 snap 20 content host page showed errata count zero for host. Version-Release number of selected component (if applicable): satellite 6.3 snap 20 How reproducible: always Steps to Reproduce: 1. Install satellite 6.2.12 2. Registered a host and had some errata for host 3. Content host page shows some errata count 4. satellite-installer --scenario satellite --upgrade 5. Navigate to Content host page 6. Navigate to Content -> Errata page Actual results: Content host page shows errata count zero and Content -> Errata page shows applicable errata (see attachments) Expected results: Content host page should show correct errata count. Additional info:
I was able to reproduce the behavior described.
One note, the counts show up as 0 in the Hosts -> Content Host listing; however, selecting the content host and visiting the Errata tab, I did see a list of applicable errata. So, this may be an issue with the API result on the listing/index call.
Additional observations from my configuration: Satellite 6.2.12 (prior to upgrade) - Hosts -> Content Hosts : for host X, shows: 148 bugfix, 27 enhancement, 60 security - Hosts -> Content Hosts -> host X -> Errata shows: 235 errata (148 bugfix, 27 enhancement, 60 security) ...upgrade to 6.3... Satellite 6.3 - Hosts -> Content Hosts : for host X, shows: 0 bugfix, 0 enhancement, 0 security - Hosts -> Content Hosts -> host X -> Errata shows: 434 errata (288 bugfix, 48 enhancement, 98 security) At initial glance, the above indicates a pretty significant difference in how the errata is being shown for the host. Justin, can you assist with investigating this one? In order to re-create, having a single host with applicable errata appears to be sufficient.
Upstream bug assigned to jsherril
Tested the scenario multiple times and unable to reproduce the behavior noted in comment 8. The only behavior that I was able to reproduce was the 0 counts on the Content Hosts listing page; however, that will be solved with the patch currently submitted upstream.
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21403 has been resolved.
VERIFIED Version Tested: Satellite-6.3 Snap 21 steps: 1. Registered a content host and had errata on 6.2.12 2. Performed upgrade to 6.3 snap 21 3. Checked errata count of content host Found content host page showed correct errata count for host.
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-2018:0336