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 successful sync of satellite tools channels, no packages are associated with errata RHBA-2016:0051 and RHBA-2016:0077.
Also no repository is associated with it.
But can see that the package are listed in content search.
Packages are present at:
https://access.redhat.com/errata/RHBA-2016:0077https://access.redhat.com/errata/RHBA-2016:0051
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Sync satellite tools channel
2. Satellite webui --> Content --> Errata --> All repositories --> Search for errata --> in details page under 'Affected Package' no package is listed.
3. Click on repository tab and it says no repository associated with errata
4. Webui --> Content --> Content Search --> Package --> search for package provided by errata. It is listed in search.
Actual results:
Errata page do not show affected package and not linked with repositories.
Expected results:
Errata page should show the list of affected packages and the repositories providing them.
Additional info:
Duplicate to 1302663 where some progress was made.
Anyway this BZ has better description of the problem.
/me to re-attach customer cases from this BZ to that one.
*** This bug has been marked as a duplicate of bug 1302663 ***