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:
Due to a regression in a refactoring, when "rhc_baseurl" is not specified as a role parameter and a system is being registered, then the "baseurl" configuration option in the [rhsm] section of the /etc/rhsm/rhsm.conf file is set to empty. This obviously has the wrong side effect of not being able to receive content, since the repositories in /etc/yum.repos.d/redhat.repo have a wrong URL.

This was reported upstream as https://github.com/linux-system-roles/rhc/issues/126

Version-Release number of selected component (if applicable):
rhel-system-roles since 1.22.0-0.9

How reproducible:
100%

Steps to Reproduce:
1. register an unsubscribed system with the rhc role, without specifying "rhc_baseurl" (and thus registering to Red Hat RHSM)
2. try to update the system, or install packages, etc

Actual results:
The system cannot fetch any content.

Expected results:
The system can fetch updates, packages, etc.

Is there a workaround?  What is the impact/severity of this?  Is the rhc role mostly unusable? I'm trying to determine how we should address this issue - sounds like a 8.8.z/9.2.z but want to make sure

(In reply to Rich Megginson from comment #1)
> Is there a workaround?

# subscription-manager config --rhsm.baseurl https://cdn.redhat.com

> What is the impact/severity of this?

Pretty high, if you register to Hosted (and not to a Satellite server, or Stage).

> Is the rhc role mostly unusable?

The role is usable, it's about the modified/registered system.

> I'm trying to determine how we should address this
> issue - sounds like a 8.8.z/9.2.z but want to make sure

Nope, 9.2 is not affected (uses rhc 1.1.x).

Hopefully an easy fix: https://github.com/linux-system-roles/rhc/pull/127

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (rhel-system-roles bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2023:6390