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 1298438 - [RFE] revisit subscription-manager's caching behavior
Summary: [RFE] revisit subscription-manager's caching behavior
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.8
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-14 05:51 UTC by Chris Snyder
Modified: 2017-12-06 11:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 11:49:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Chris Snyder 2016-01-14 05:51:17 UTC
I think it is a good idea to revisit the caching in subman to maybe move to python-rhsm. The caching behavior seems to be on network bound operations. Furthermore it seems to have the most utility when the connection to the server is broken in someway (that is when most of the caches are used). Its almost like we are testing the connection object that is passed into the cache objects and returning the contents of said cache object if the connection object fails the test (the update from/to the server).

The suggestion is to move the caching to be part of python-rhsm. I would also like to add that it would be very nice for these modifications to include a method of determining the source of the returned value for all cached resources (basically it would be neat to have a method that would return the source of the last result).

These improvements could include a separate connection object that caches all interactions with the server but does not necessarily need to.

Comment 2 vritant 2016-08-01 20:33:09 UTC
Increasing the scope of this RFE, in order to not tie us to a specific implementation or purpose. basically, we need to redesign subscription-manager caching.

Comment 3 Jan Kurik 2017-12-06 11:49:35 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


Note You need to log in before you can comment on or make changes to this bug.