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:
subscription-manager refresh does not update redhat.repo ; subscription-manager repos will.

Version-Release number of selected component (if applicable):
subscription-manager-1.8.22-1.el6_4.x86_64

How reproducible:
all the time

Steps to Reproduce:
1. update subscription-manager and install subscription-manager-migrate onto a satellite-installed machine
2. register that machine against rhn classic
3. migrate the machine to rhsm using rhn-migrate-classic-to-rhsm --force
4. on the portal associate subscriptions to have access to the rhel6 server repos
5. use subscription-manager refresh

Actual results:
redhat.repo remains empty

Expected results:
redhat.repo is also updated as information are refreshed. instead, they only are refreshed if using subscrition-manager repos

Additional info:
internal ticket - no customer case attached at time of opening.

I don't think this has anything to do with refresh.  If you run "yum repolist" to generate a yum transaction, the subscription-manager yum plugin will be invoked and generate a correct redhat.repo.

In newer versions of subscription-manager, if new certificates are pulled down, the redhat.repos file will be updated.

Please let me know if you have any questions.

no, one of the commands I did run 3 times between refreshes while trying to get the repos to work was

~~~
yum clean all
yum repolist
yum repolist all
~~~

that would ever only list the repos of the redhat-source.repo, redhat.repo wouldn't get updated.

[root@vm-139 ~]# cat /etc/yum/pluginconf.d/subscription-manager.conf 
[main]
enabled=0

Setting enabled to 1 allows the subscription-manager plugin to update redhat.repos.  It is enabled by default.

The last comment should resolve your problem, please let me know if there's something else going on.  When I logged into your machine and set enabled=1, everything worked as intended.

Please let me know if there's anything else you need.

yup that does solve the problem. too bad nothing pointed at a misconfiguration other than the behaviour, a warning / error message would have been nice.