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:
A host with firefox versions between 60.6.0-3 and 60.7.0-1 is not showing any applicable errata for firefox, in Satellite. There are multiple errata that could apply (RHSA-2019:1265).
Version-Release number of selected component (if applicable):
6.6 Snap 7
How reproducible:
Always, at least on this host.
Steps to Reproduce:
1. Use a RHEL 7 host that is fully upgraded.
2. Install firefox or downgrade firefox to one of the versions above.
3. Check the applicable errata for the host.
Actual results:
No errata listed for firefox.
Expected results:
At least one errata listed for firefox.
Additional info:
This likely affects other packages and/or versions.
The host (before updates) properly showed many errata, and during this, another package (gzip) properly showed errata.
We worked with Justin on this for a while and can't determine what is causing the issue.