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.

The message in $Subject can appear incorrectly because it's based on the host's stored errata counts, which are not updated immediately.

One way to reproduce is

1. new host details > Errata > select all > Apply
2. Stay on that screen until the job completes

Expected: You see the 'All errata up-to-date' screen with the green check
Actual: You see 'This host has errata that are applicable, but not installable.' After refreshing the page, the 'All errata up-to-date' screen appears.

Suggestion/brainstorm

1. maybe have a link to recalculate errata from that screen?
2. make sure recalculating errata updates the content facet's stored errata counts

Created from redmine issue https://projects.theforeman.org/issues/35398

Upstream bug assigned to None

Upstream bug assigned to jlenz

Upstream bug assigned to jlenz

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 (Important: Satellite 6.12 Release), 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-2022:8506