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:
Lifecycle Environments does not shows details associated C.V. /Repositories/Errata/packages, ..etc
Version-Release number of selected component (if applicable):
@Satellite 6.6.0 snap 10.0
How reproducible:
Always
Steps to Reproduce:
1. Go to Satellite UI.
2. Create/sync Repos , Add to C.V. and publish it (Library bydefault)
3. Now go to Content => 'Lifecycle Environments' => Click on 'Library' => See Tabs 'Content Views/Yum Repositories/Errata/packages ..etc'
Actual results:
Does not shows any details
Expected results:
It should show the associated C.V. /Repositories/Errata/packages, ..etc details.
Additional info:
Steps to Reproduce:
1. Go to Satellite UI.
2. Create/sync Repos , Add to C.V. and publish it (Library 'Lifecycle Environment' bydefault)
3. Now go to Content => 'Lifecycle Environments' => Click on 'Library' => See Tabs 'Content Views/Yum Repositories/Errata/packages ..etc'
I have a fix opened upstream to fix this problem for the Content Views tab. However, there was a deliberate change made to how the other tabs work as they now require a Content View to be selected from the dropdown before showing any results. Check out my description on the upstream PR linked from the Foreman tracker at the top of the BZ.
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, 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-2019:3172