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 1462759 - [RFE] Reduce upcalls to to subscription-manager/release with full_refresh_on_yum
Summary: [RFE] Reduce upcalls to to subscription-manager/release with full_refresh_on_yum
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: subscription-manager
Version: 8.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Chris Snyder
QA Contact: Red Hat subscription-manager QE Team
URL:
Whiteboard:
Depends On:
Blocks: 1825061
TreeView+ depends on / blocked
 
Reported: 2017-06-19 13:15 UTC by Dylan Gross
Modified: 2023-09-22 12:51 UTC (History)
4 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:55 UTC
Type: Story
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-7061 0 None Migrated None 2023-09-22 12:51:50 UTC

Description Dylan Gross 2017-06-19 13:15:04 UTC
1. Proposed title of this feature request

Allow "full_refresh_on_yum = 0" in /etc/rhsm/rhsm.conf to disable calls by rhsmcertd to https://<satellite>/rhsm/consumers/<UUID>/release



3. What is the nature and description of the request?

The subscription-manager plugin for yum mostly obeys an option in /etc/rhsm/rhsm.conf called "full_refresh_on_yum".   When disabled (i.e. = 0), this will keep the yum plugin from doing a full refresh.

However, yum calls are still reaching out to the satellite to hit the /rhsm/consumers/<UUID>/release every time yum is executed.


4. Why does the customer need this? (List the business requirements here)

Due to the number of clients in the Satellite 6.x environment, every regular call to the satellite can add up to significant load.  This is an attempt to be able to more strictly control the number of calls made to the Satellite.


5. How would the customer like to achieve this? (List the functional requirements here)

Disable the calls to https://<subscription-manager-app>/rshm/consumers/UUID/release in the subscription-manager plugin when full_refresh_on_yum = 0 in /etc/rshm/rhsm.conf


6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

a.) set "full_refresh_on_yum = 0" in /etc/rhsm/rhsm.conf on a client.
b.) tail satellite's /var/log/httpd/foreman-ssl_access_ssl.log 
c.) run a "yum list"


7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

  No



8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

None specified, but as soon as possible within appropriate severity timelines would be appreciated.



9. Is the sales team involved in this request and do they have any additional input?

   Yes


10. List any affected packages or components.

   subscription-manager


11. Would the customer be able to assist in testing this functionality if implemented?

   Yes.

Comment 3 William Poteat 2020-01-29 16:50:00 UTC
Will not fit into the timeframe for RHEL 7.9. Will be pushing this on to RHEL 8.

Comment 15 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 16 RHEL Program Management 2023-09-22 12:51:55 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.