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:
As a user of Satellite 6, it is difficult for me to figure out which repository needs to be synced based upon Red Hat docs.
For example, Red Hat docs say to enable 'rhel-7-server-rpms' in order to enable/update RHEL 7 Server. To synchronize RHEL 7 Server x86_64 in Satellite, which repository (and repository set) does this correspond to?
I can figure out that it is probably the 'Red Hat Enterprise Linux 7 Server (RPMs)' repository set, but for many products, it isn't so straightforward.
Additionally, it is trial and error.
This RFE requests:
* exposing the repository label visually (so on the Red Hat Repositories page, I can see that 'Red Hat Enterprise Linux 7 Server (RPMs)' == rhel-7-server-rpms)
* exposing the repository label via hammer (and by extension the API). This enables me to ideally enable a repository by label alone (as they are unique across products).
An ideal solution would be where they user can run a command similar to
hammer repository-set enable \
--organization "$ORG" \
--basearch='x86_64' \
--releasever='7Server' \
--repository-label=rhel-7-server-rpms
This RFE was inspired by this discussion in the Customer portal. (https://access.redhat.com/discussions/3361601)
As prior-art / an example of what is being requested, the attachment in Comment #1 shows existing capabilities that the Customer Portal offers.