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