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.

Bug 2016759

Summary:	[RFE] Make repository's (compare_providers_)priority yum option configurable in Satellite
Product:	Red Hat Satellite	Reporter:	Pavel Moravec <pmoravec>
Component:	Repositories	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.9.0	CC:	ahumbe, dsinglet, dwoodruf, iballou, thadzhie
Target Milestone:	Unspecified	Keywords:	FutureFeature, MigratedToJIRA, Reopened, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 01:05:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pavel Moravec 2021-10-23 12:30:17 UTC

Description of problem:
TL;DR: Have centralised setting for yum/dnf repository option compare_providers_priority (yum) / priority (dnf), for each repo.

User story: a customer wants to prefer installing packages (as dependency ones) from some repositories rather than from others. Say if package abc is available in EPEL and depends on python3-blah library both in EPEL and RHEL, they want the python3-blah package to be installed from RHEL repo due to the priority.

That is achieved by compare_providers_priority (yum) / priority (dnf) repository option (see "man 5 yum.conf") - but that is on client basis, where one has to manually modify /etc/yum.repos.d/redhat.repo for each repo on each system. Manual, error prone.

Due to the repetitive+manual change on each host of supposedly *same* priorities for the same repo, it is requested to configure this centrally from Satellite.


Version-Release number of selected component (if applicable):
Sat6.9


How reproducible:
100%


Steps to Reproduce:
1. No way to centrally define repo variables compare_providers_priority (yum) / priority (dnf) to /etc/yum.repos.d/redhat.repo .


Actual results:
No such feature.


Expected results:
- a repository object to have configurable option "repo priority", configurable via WebUI or hammer or API, acceptable values are Int from range 1-99.
- (only!) when the value is set, sub-man refresh (or similar operation that modifies redhat.repo file) on a client will set to this repository compare_providers_priority (rhel7) or priority (rhel8+) to this value
- the setting of a root repo will be applied to all its clones in any CV
- unsetting the value for some repo means "sub-man refresh" removes the setting for any (cloned) repo on that client in yum.repos.d/redhat.repo


Additional info:

Comment 5 Brad Buckingham 2023-05-08 12:49:27 UTC

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.

Comment 6 Brad Buckingham 2023-06-13 00:20:02 UTC

Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.

Comment 8 Brad Buckingham 2023-07-21 21:06:39 UTC

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.

Comment 10 Brad Buckingham 2023-09-01 19:45:24 UTC

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.

Comment 12 Eric Helms 2024-06-06 01:05:53 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.