Bug 1462759

Summary: [RFE] Reduce upcalls to to subscription-manager/release with full_refresh_on_yum
Product: Red Hat Enterprise Linux 8 Reporter: Dylan Gross <dgross>
Component: subscription-managerAssignee: Chris Snyder <csnyder>
Status: CLOSED MIGRATED QA Contact: Red Hat subscription-manager QE Team <rhsm-qe>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.2CC: csnyder, khowell, redakkan, wpoteat
Target Milestone: rcKeywords: FutureFeature, MigratedToJIRA, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-22 12:51:55 UTC Type: Story
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1825061    

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.