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 2141454 - "rhc connect --username --password" on RHEL 8.7 system does not result in a system with working yum repositories
Summary: "rhc connect --username --password" on RHEL 8.7 system does not result in a s...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: rhc
Version: 8.7
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: Link Dupont
QA Contact: Pavol Kotvan
URL:
Whiteboard: SCRUB_20221201
Depends On:
Blocks: 2165099
TreeView+ depends on / blocked
 
Reported: 2022-11-09 22:30 UTC by Brian Smith
Modified: 2023-05-16 09:53 UTC (History)
5 users (show)

Fixed In Version: rhc-0.2.1-11.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2165099 (view as bug list)
Environment:
Last Closed: 2023-05-16 08:35:37 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github RedHatInsights rhc pull 30 0 None open Enable content when registering with username & password 2023-01-26 18:43:02 UTC
Red Hat Issue Tracker RHELPLAN-138881 0 None None None 2022-11-09 22:36:46 UTC
Red Hat Product Errata RHBA-2023:2819 0 None None None 2023-05-16 08:35:42 UTC

Description Brian Smith 2022-11-09 22:30:59 UTC 
Description of problem:
On newly built RHEL 8.7 system, running "rhc connect" does not result in a system with working RHEL yum repositories

Version-Release number of selected component (if applicable):  RHEL 8.7, rhc-0.2.1-9.el8.x86_64

How reproducible:
Only attempted one time

Steps to Reproduce:
1. Build RHEL 8.7 system from rhel-8.7-x86_64-dvd.iso 

2. Run "rhc connect", which successfully completes:
● Connected to Red Hat Subscription Management
● Connected to Red Hat Insights
● Activated the Red Hat connector daemon


Actual results:
There are no RHEL repositories configured:

# dnf repolist
Updating Subscription Management repositories.
No repositories available

# cat /etc/yum.repos.d/redhat.repo 
#
# Certificate-Based Repositories
# Managed by (rhsm) subscription-manager
#
# *** This file is auto-generated.  Changes made here will be over-written. ***
# *** Use "subscription-manager repo-override --help" if you wish to make changes. ***
#
# If this file is empty and this system is subscribed consider
# a "yum repolist" to refresh available repos
#

Expected results:
- Expected that after running "rhc connect" the BaseOS / AppStream repositories are available

Additional info:
- After running "subscription-manager refresh" the BaseOS / AppStream repositories are available/working.
Comment 1 Link Dupont 2022-12-01 16:43:58 UTC 
I could not reproduce this. Does the account you registered with have Simple Content Access enabled? 'rhc connect' does not activate any entitlements; it only registers the system with RHSM.
Comment 2 Brian Smith 2022-12-01 17:33:39 UTC 
Yes, my account has simple content access enabled.  

I built another two new RHEL 8.7 systems from the rhel-8.7-x86_64-dvd.iso:

- On one system, I ran "rhc connect" and reproduced the issue again as described in this BZ.  If I then run "subscription-manager refresh", the AppStream and BaseOS repositories are avalable.

- On the other system, I ran "subscription-manager register" and was left with both the AppStream and BaseOS repositories setup/available 

Why does "subscription-manager register" configure the repositories, but "rhc connect" doesn't?
Comment 4 Christian Marineau 2022-12-02 14:54:05 UTC 
I was able to reproduce the issue on RHEL 8.7
Comment 6 Link Dupont 2022-12-02 15:48:54 UTC 
I figured it out. I was able to reproduce it when I run 'rhc connect' using a username and password. I had previously run my reproduction steps using an org-id and activation key, which of course activates the repositories automatically.
Comment 24 errata-xmlrpc 2023-05-16 08:35:37 UTC 
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 (rhc 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/RHBA-2023:2819
Note You need to log in before you can comment on or make changes to this bug.