Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Issue occurs on all content hosts. Example: Content host has six errata available. Apply single erratum either from Content->Errata or the Errata tab for the Content Host. Single erratum applies successfully, but refreshing either screen results in 0 errata being shown for the content host even though the remaining five errata are not dependencies of the single errata that was installed. Content hosts are registered to a Satellite Capsule. The Satellite Capsules are registered to the Satellite server. goferd is running on the content hosts.
Version-Release number of selected component (if applicable):
How reproducible: Always
Steps to Reproduce:
1. Apply one or more errata from the Satellite web UI. Errata applies successfully.
2. Refresh Satellite web UI.
3. Revisit Content->Errata or the Errata tab for the content host.
Actual results:
Now both screens do not show any errata applicable to the content host even though there are known remaining errata to be applied.
Expected results:
Applicable errata should still be shown.
Additional info:
Package profile update task for content host completes successfully. Manually executing `/usr/sbin/katello-package-upload` completes successfully, but no Package Profile update task is started on Satellite and 0 errata continue to be shown as applicable. Executing `/usr/sbin/katello-package-upload -f` does result in a Package Profile task running on Satellite and then applicable errata are shown once again. However, within a day the applicable/installable errata returns to 0 for the host.