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.

Description of problem:
When using RHSM provided repos, a subscription-manager refresh can be used to reload the list of provided repos, but it does not expire the local repomd.xml.  This can lead to some frustration with the repo list being updated but not the metadata of those repos.

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


How reproducible:
100%

Steps to Reproduce:
1.Using Sat6, register a client to a repo
2.run yum search *
3.update the repo on Sat6
4.add new repo to the client
5.run subscription-manager refresh on client
6.run yum search *

Actual results:
Even though the repo list changes the cached repomd.xml is not considered 'obsolete'

Expected results:
subscription-manager refresh performs similarly to yum clean expire-cache

Additional info:
I'm not expecting the primary.sqlite or friends to be removed, just the repomd.xml so that content is (optionall) refreshed.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.