Bug 2141454
Summary: | "rhc connect --username --password" on RHEL 8.7 system does not result in a system with working yum repositories | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Brian Smith <briasmit> | |
Component: | rhc | Assignee: | Link Dupont <link> | |
Status: | CLOSED ERRATA | QA Contact: | Pavol Kotvan <pakotvan> | |
Severity: | medium | Docs Contact: | ||
Priority: | high | |||
Version: | 8.7 | CC: | cmarinea, fjansen, jhnidek, link, pakotvan | |
Target Milestone: | rc | Keywords: | Triaged, ZStream | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | SCRUB_20221201 | |||
Fixed In Version: | rhc-0.2.1-11.el8 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 2165099 (view as bug list) | Environment: | ||
Last Closed: | 2023-05-16 08:35:37 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 2165099 |
Description
Brian Smith
2022-11-09 22:30:59 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. 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? I was able to reproduce the issue on RHEL 8.7 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. 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 |