Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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:6541
[root@kvm-02-guest09 ~]# rpm -qa | grep rhc rhc-0.2.4-1.el9.x86_64 [root@kvm-02-guest09 ~]# rpm -qa | grep insights-client insights-client-3.2.0-1.el9.noarch [root@kvm-02-guest09 ~]# subscription-manager config --server.hostname=subscription.rhsm.stage.redhat.com [root@kvm-02-guest09 ~]# subscription-manager register Registering to: subscription.rhsm.stage.redhat.com:443/subscription Username: zpetracek Password: The system has been registered with ID: a37eb3fe-fc1a-458b-b107-7eeb815c3dfd The registered system name is: kvm-02-guest09.rhts.eng.brq.redhat.com [root@kvm-02-guest09 ~]# subscription-manager repos --list-enabled +----------------------------------------------------------+ Available Repositories in /etc/yum.repos.d/redhat.repo +----------------------------------------------------------+ Repo ID: rhel-9-for-x86_64-baseos-beta-rpms Repo Name: Red Hat Enterprise Linux 9 for x86_64 - BaseOS Beta (RPMs) Repo URL: https://cdn.redhat.com/content/beta/rhel9/9/x86_64/baseos/os Enabled: 1 Repo ID: rhel-9-for-x86_64-appstream-beta-rpms Repo Name: Red Hat Enterprise Linux 9 for x86_64 - AppStream Beta (RPMs) Repo URL: https://cdn.redhat.com/content/beta/rhel9/9/x86_64/appstream/os Enabled: 1 [root@kvm-02-guest09 ~]# dnf -y update [root@kvm-02-guest09 ~]# dnf -y install rhc-worker-playbook Updating Subscription Management repositories. Last metadata expiration check: 0:00:32 ago on Thu 10 Aug 2023 02:59:31 PM CEST. Dependencies resolved. =========================================================================================================================== Package Architecture Version Repository Size =========================================================================================================================== Installing: rhc-worker-playbook x86_64 0.1.8-6.el9 beaker-AppStream 9.9 M Installing dependencies: ... Installed: ansible-core-1:2.14.7-1.el9.x86_64 git-core-2.39.3-1.el9_2.x86_64 python3-cffi-1.14.5-5.el9.x86_64 python3-cryptography-36.0.1-4.el9.x86_64 python3-packaging-20.9-5.el9.noarch python3-ply-3.11-14.el9.noarch python3-pycparser-2.20-6.el9.noarch python3-pyparsing-2.4.7-9.el9.noarch python3-resolvelib-0.5.4-5.el9.noarch rhc-worker-playbook-0.1.8-6.el9.x86_64 sshpass-1.09-4.el9.x86_64 Complete! [root@kvm-02-guest09 ~]# cat /etc/rhc/config.toml # rhc global configuration settings broker = ["wss://connect.cloud.stage.redhat.com:443"] data-host = "cert.cloud.stage.redhat.com" log-level = "debug" # optional cert-file = "/etc/pki/consumer/cert.pem" key-file = "/etc/pki/consumer/key.pem" [root@kvm-02-guest09 ~]# systemctl cat rhcd.service | grep Environment Environment="HTTP_PROXY=http://squid.corp.redhat.com:3128" Environment="HTTPS_PROXY=http://squid.corp.redhat.com:3128" [root@kvm-02-guest09 ~]# cat /etc/insights-client/insights-client.conf | egrep 'proxy=|base_url' proxy=http://squid.corp.redhat.com:3128 base_url=cert.console.stage.redhat.com [root@kvm-02-guest09 ~]# rhc connect Connecting kvm-02-guest09.rhts.eng.brq.redhat.com to Red Hat. This might take a few seconds. Username: zpetracek Password: ● Connected to Red Hat Subscription Management ● Connected to Red Hat Insights ● Activated the Remote Host Configuration daemon ● Enabled console.redhat.com services: compliance, remediations, remote configuration, insights Successfully connected to Red Hat! Manage your connected systems: https://red.ht/connector STEP DURATION rhsm 18.413s insights 46.594s Remote Host Configuration 22ms ^^ no error occured during connecting through rhc, therefore verification PASSED [root@kvm-02-guest09 ~]# echo $? 0