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
-> Red Hat Satellite v 6 webui should provide an option to set the priority of the repositories subscribed to the system.
2. Who is the customer behind the request?
Account: name and acct #
3. What is the nature and description of the request?
-> The customer would like to set priority for repositories from Satellite WebUI for the subscribed content hosts.
4. Why does the customer need this? (List the business requirements here)
-> Many of the systems are subscribed to multiple repositories via Satellite, and in some cases, they need to setup priorities for these repositories because packages in a low priority repository can not replace packages installed from repositories with higher priority, even if it has an updated version.
5. How would the customer like to achieve this? (List the functional requirements here)
-> To have an option to set priority for repositories from the Satellite v 6 WebUI.
6. Is there already an existing RFE upstream or in Red Hat Bugzilla?
-> No
7. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
-> no
8. Is the sales team involved in this request and do they have any additional input?
-> No
9. Additional Information.
-> Suggested customer to use CLI way to set priority of the repository
# yum-config-manager --enable rhel-server-ost-6-folsom-rpms --setopt="rhel-server-ost-6-folsom-rpms.priority=1"
Comment 1RHEL Program Management
2015-01-02 05:23:55 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Hi,
coming from a redhat case, I'd like to know if there is a way that this issue will be reevaluated?
Right now, satellite user still have to use content filters or configure priorities manually as error-prone workaround.
As it is also considered as redhat insights issue with high prio when packages are installed from epel instead of satellite-tool repo, I'd like to highlight our interest in a sustainable solution.Also with rhel8 and dnf, priorities are now a built-in function instead of being an extension.
Thank you!
Best Regards,
Alexander Lex
Hi,
coming from a redhat case, I'd like to know if there is a way that this issue will be reevaluated?
Right now, satellite user still have to use content filters or configure priorities manually as error-prone workaround.
As it is also considered as redhat insights issue with high prio when packages are installed from epel instead of satellite-tool repo, I'd like to highlight our interest in a sustainable solution.Also with rhel8 and dnf, priorities are now a built-in function instead of being an extension.
Thank you!
Best Regards,
Alexander Lex
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 one month's time. If you have any concerns about this, please contact your Red Hat Account team. Thank you.
We are going to close this RFE out as we have higher impacting bugs and features that our team needs to focus on. While we agree this would be a useful addition to Satellite's functionality, we don't have the capacity to address this in the near term so closing to reflect our priorities.
Comment 24Red Hat Bugzilla
2023-09-14 23:58:05 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days
1. Proposed title of this feature request -> Red Hat Satellite v 6 webui should provide an option to set the priority of the repositories subscribed to the system. 2. Who is the customer behind the request? Account: name and acct # 3. What is the nature and description of the request? -> The customer would like to set priority for repositories from Satellite WebUI for the subscribed content hosts. 4. Why does the customer need this? (List the business requirements here) -> Many of the systems are subscribed to multiple repositories via Satellite, and in some cases, they need to setup priorities for these repositories because packages in a low priority repository can not replace packages installed from repositories with higher priority, even if it has an updated version. 5. How would the customer like to achieve this? (List the functional requirements here) -> To have an option to set priority for repositories from the Satellite v 6 WebUI. 6. Is there already an existing RFE upstream or in Red Hat Bugzilla? -> No 7. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? -> no 8. Is the sales team involved in this request and do they have any additional input? -> No 9. Additional Information. -> Suggested customer to use CLI way to set priority of the repository # yum-config-manager --enable rhel-server-ost-6-folsom-rpms --setopt="rhel-server-ost-6-folsom-rpms.priority=1"