This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 1621275 - dnf' rhsm plugin should not make unneccessary upcalls to Satellite on every "dnf" excecution (including --help)
Summary: dnf' rhsm plugin should not make unneccessary upcalls to Satellite on every "...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: subscription-manager
Version: 8.2
Hardware: All
OS: Linux
high
low
Target Milestone: rc
: ---
Assignee: Jiri Hnidek
QA Contact: Red Hat subscription-manager QE Team
URL:
Whiteboard:
Depends On: 1700445
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-23 14:45 UTC by Dylan Gross
Modified: 2024-06-13 21:58 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-22 12:51:59 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github candlepin subscription-manager pull 2051 0 'None' closed 1621275: Less communication with candlepin server from sub-man plugin; ENT-923 2021-01-11 12:31:27 UTC
Github candlepin subscription-manager pull 2155 0 'None' closed 1621275: YUM plugin - less API calls; ENT-923 2021-01-11 12:31:27 UTC
Red Hat Issue Tracker   RHEL-7060 0 None Migrated None 2023-09-22 12:51:53 UTC

Description Dylan Gross 2018-08-23 14:45:09 UTC 
Description of problem:

   When a "yum --help" or other trivial yum calls are executed using the subscription-manager plugin, by default it makes two calls up to the Subscription-Manager source.  Satellite is the main concern, but it could be the Red Hat portal as well.   

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

How reproducible:  Always

Steps to Reproduce:
1.   tail -f /var/log/foreman/production.log on the Satellite
2.   execute "yum --help" on a Content Host.
3.   Observe calls to ...
       GET "/rhsm/" for the Content Host IP
       GET "/rhsm/consumers/<UUID>/content_overrides for IP
       GET "/rhsm/consumers/<UUID>/release for IP

Actual results:

  Even a call like "yum --help" makes multiple upcalls to the subscription-manager source, when likely it is unneccessary.

Expected results:

  yum's subscription-manager plugin should only contact the subscription-manager source when necessary.


Additional info:

  "yum --help" is the most extreme example of uneccesrary upcalls, but ideally the plugin would not upcall to the Satellite if it doesn't need to, like when listing local package, repo, information. 

  One more note, of the three observed calls above, the "GET /content_overrides" *can* be stopped by setting "full_refresh_on_yum = 0" in /etc/rhsm/rhsm.conf, but that may be overkill.   In some use cases you do want yum to do the full refresh when you actually make a change, but it shouldn't necessarily be done for local queries on the client.
Comment 3 Dylan Gross 2018-08-23 14:59:03 UTC 
Non-complete list of other "local" yum functionality that triggers the same upcalls (/rhsm, /rhsm/consumers/#/content_overrides/, and /rhsm/consumers/#/release ) to the satellite which perhaps are uneccessary:

   # yum list

   # yum repolist

   # yum history
Comment 6 Chris Snyder 2019-05-16 11:55:51 UTC 
Moving back to POST as there has not been a build done which includes this patch.
Comment 11 John Sefler 2019-06-06 12:55:56 UTC 
Due to regressions introduced by the initial attempt to fix this bug, the patch has been reverted from the latest el7 subscription-manager build...

[root@dhcp35-120 ~]# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 2.3.17-1
subscription management rules: 5.35
subscription-manager: 1.24.10-1.el7
[root@dhcp35-120 ~]# rpm -qa subscription-manager --changelog | grep 1621275
- Revert "1621275: Less communication with candlepin server from sub-man
- 1621275: Less communication with candlepin server from sub-man plugin;


This bug has been moved back to NEW status with Verified:FailedQA
Also see affected bug 1700445
Comment 21 RHEL Program Management 2023-09-22 12:50:31 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 22 RHEL Program Management 2023-09-22 12:51:59 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 "RHEL-" 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.
Note You need to log in before you can comment on or make changes to this bug.