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.
+++ This bug was initially created as a clone of Bug #1624479 +++
Description of problem:
Display the repo label on the enabled repos results
Version-Release number of selected component (if applicable):
6.4 Repositories page
How reproducible:
Always
Steps to Reproduce:
1. Ensure a repo is enabled
2. View results
Actual results:
No repo label on the enabled repo entries though they are present in the Available repos column.
Expected results:
Show Repo Label for both Available and Enabled repos.
Additional info:
Hilti
--- Additional comment from pm-rhel on 20180904T17:45:02
Since this issue was entered in Red Hat Bugzilla, the pm_ack has been
set to + automatically for the next planned release
--- Additional comment from tstrachota on 20180905T11:52:34
Hi Roxanne,
I remember we were talking about this one in a meeting but I forgot the details.
Should the repo set label in enabled repos list be displayed instead of architecture and version? For example "rhel-7-server-rhn-tools-rpms" instead of "x86_64 7.1"? See my attached screenshot that demonstrates this alternative.
Or should it be displayed together with arch and version?
Or did I misunderstood it completely and you're proposing something completely different?
--- Additional comment from tstrachota on 20180905T11:52:55
Created attachment 1481083[details]
Proposal for repo labels placement
--- Additional comment from asharvit on 20180905T14:47:48
Created redmine issue https://projects.theforeman.org/issues/24827 from this bug
--- Additional comment from asharvit on 20180905T16:04:31
Upstream bug assigned to asharvit
--- Additional comment from pm-sat on 20180905T16:09:24
Upstream bug assigned to asharvit
--- Additional comment from pm-sat on 20180905T16:09:27
Upstream bug assigned to asharvit
--- Additional comment from pm-sat on 20180905T20:09:23
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/24827 has been resolved.
--- Additional comment from tstrachota on 20180906T07:23:00
My question was answered in a PR, removing needinfo.
--- Additional comment from pcreech on 20180919T13:46:34
Avi,
This failed to cherry-pick downstream, can you take a look?
--- Additional comment from mmccune on 20180925T21:40:40
This does not match the 'DDR' blocker criteria and we are moving this to 6.4.z
--- Additional comment from pcreech on 20180926T15:58:27
I accidentally merged this not realizing it got kicked to 6.4.z. Reopened the PR
Failed QA in Satellite 6.4.2 Snap 1.
While the labels show up in the un-enabled repos, enabled ones are still not showing their labels.
See attached screenshot.
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-2020:1454