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:
After Satellite 6.3.1 to 6.3.2 upgrade, all content hosts show conflicting number of errata on errata tab versus details tab.
For example, the content host errata tab shows more errata (18, in one case) than the details tab (only one.). The errata tab is correct, while the details tab is missing most of the errata. This is happening for both RHEL6 and RHEL7 content hosts.
"hammer host errata list --host <HOSTNAME>" from the command line shows the correct number of errata.
Following the steps at https://access.redhat.com/solutions/3013801 for each content host resolves the issue, and after that both errata tab and the details tab show the same number of errata.
Version-Release number of selected component (if applicable):
Upgraded from Satellite 6.3.1 to 6.3.2
Steps to Reproduce:
1. Have Satellite 6.3.1 environment with existing content hosts with pending errata updates.
2. Upgrade to Satellite 6.3.2 following documentation
Actual results:
The content hosts details tab and errata tabs show different number of updates
Expected results:
Both the details tab and errata tabs of the content host show the same number of updates following the Satellite 6.3.1 to 6.3.2 upgrade.
Hi Brian,
I wasn't able to reproduce this problem so I'm looking for more details.
- Did the upgrade actually succeed without any issues?
- Can a database dump be provided from the customer so that I can look into the state of the data?