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:
Current search for packages within repositories does not allow one to search for all instances of packages in all repos. Specific repos must be specified.
Version-Release number of selected component (if applicable):
All
How reproducible:
Always
Steps to Reproduce:
1.Content>Packages>Select a package
2.Click on the Repositories tab
3. Notice that the first two drop downs require you to specify a Lifecycle and Content View
Actual results:
As is.
Expected results:
Customer (Walmart) would like to be able to search in All Lifecycles and All Content Views.
Additional info:
Quote from Walmart: "with the spectre/meltdown firedrill it has been pretty rough for us to use that to validate which packages are actually available in which locations"
Roxanne,
The API currently supports this, so we just need to update the UI here to accommodate nil content view and lifecycle environment. I propose we simply load the page with both drop downs blank (we'd have to add a blank entry to each, of course). This gives users the flexibility of choosing a specific CV/LE only if they want.
On a side note, I noticed that it is possible to search for repos in a LE without specifying the CV, but you have to first select a different LE, then reselect the LE you want - the CV drop down now shows a blank entry, and the API request doesn't send the CV ID. This seems like a bug to me, and this feature will most likely also 'fix' this because we'll always show the blank option in the drop down selectors.
Please let me know if this proposed solution makes sense from a UX point of view.
Andrew,
Could we have the drop downs say "All Content Views" and "All Lifecycle Environments". My concern is that if we load blank drop downs, then the user wouldn't have a clear indication of where the results are coming from.
Verified:
@Satellite 6.5.0 Snap 5.0
steps:
1.Content>Packages>Select a package
2.Click on the Repositories tab
3. Able see repositories associated individual or all life cycle environment and content view.
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:1222