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.
1. Proposed title of this feature request
[RFE] Change the color of the remove repository icon when repositories cannot be removed
3. What is the nature and description of the request?
Enabled repositories under Content > Red Hat Repositories show a blue circle with a minus sign. I'd like to suggest that this icon change to a white circle with a black minus sign for repositories that have been added to content views.
4. Why does the customer need this? (List the business requirements here)
Customers often have trouble remembering or determining whether or not a repository has already been added to a content view before they try to remove it. In Satellite 6.10, attempting to disable such a repository creates paused tasks that lock the database, and then create a cascade effect that prevents other related tasks from running (see bz #2032040).
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
- enable a repo
- add that repo to a content view
- see if the icon changed
- remove that repo from the content view
- see if the icon changed back
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
no
8. Does the customer have any specific time-line dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
no
9. Is the sales team involved in this request and do they have any additional input?
no
10. List any affected packages or components.
foreman
11. Would the customer be able to assist in testing this functionality if implemented?
yes
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you.
Based upon feedback during auto-closure, leaving this bugzilla open a while longer for additional investigation; however, it may be closed in a future iteration.
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 (Important: Satellite 6.15.0 release), 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-2024:2010