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.

Bug 2175793

Summary:	Unhelpful error message when subscribed to Satellite
Product:	Red Hat Enterprise Linux 8	Reporter:	Marko Myllynen <myllynen>
Component:	rhc	Assignee:	CSI Client Tools Bugs <csi-client-tools-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Red Hat subscription-manager QE Team <rhsm-qe>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.7	CC:	cmarinea, fjansen, pakotvan, redakkan
Target Milestone:	rc	Keywords:	MigratedToJIRA, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-07 14:03:13 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:

Description Marko Myllynen 2023-03-06 14:56:53 UTC

Description of problem:
Using rhc with Satellite is not (yet) supported however the error message when trying to start rhcd on a Satellite-registered system is not helpful:

cannot connect to broker: network Error : websocket: bad handshake

Ideally an error message would tell what exactly failed, why it failed, and is there anything that could be done to fix the issue. Or as in this case inform it's not possible/supported to use rhcd. Thanks.

Version-Release number of selected component (if applicable):
rhc-0.2.1-12.el8_7.x86_64

Comment 1 Link Dupont 2023-03-06 17:20:25 UTC

Could you set log-level = "trace" in /etc/rhcd/config.toml, start rhcd again and attach the output of `journalctl -u rhcd --no-pager`?

Comment 2 Marko Myllynen 2023-03-07 08:53:30 UTC

# insights-client --status
System is registered locally via .registered file. Registered at 2023-03-06T16:39:58.070587
Insights API confirms registration.
# systemctl stop rhcd.service
# grep -r log-level /etc/rhc
/etc/rhc/workers/rhc-package-manager.toml:log-level = "trace"
/etc/rhc/config.toml:log-level = "trace"
# systemctl start rhcd.service
# /usr/bin/journalctl -u rhcd --no-pager
-- Logs begin at Tue 2023-03-07 10:47:33 EET, end at Tue 2023-03-07 10:49:34 EET. --
Mar 07 10:49:33 idmc systemd[1]: Started Red Hat connector daemon.
Mar 07 10:49:33 idmc rhcd[6227]: [rhcd] 2023/03/07 10:49:33 /builddir/build/BUILD/rhc/yggdrasil-0.2.1/cmd/yggd/main.go:160: starting rhcd version 0.2.1
Mar 07 10:49:33 idmc rhcd[6227]: [rhcd] 2023/03/07 10:49:33 /builddir/build/BUILD/rhc/yggdrasil-0.2.1/cmd/yggd/main.go:162: attempting to kill any orphaned workers
Mar 07 10:49:33 idmc rhcd[6227]: [rhcd] 2023/03/07 10:49:33 /builddir/build/BUILD/rhc/yggdrasil-0.2.1/cmd/yggd/main.go:209: listening on socket: @yggd-dispatcher-aJUoAU
Mar 07 10:49:34 idmc rhcd[6227]: cannot connect to broker: network Error : websocket: bad handshake
Mar 07 10:49:34 idmc systemd[1]: rhcd.service: Main process exited, code=exited, status=1/FAILURE
Mar 07 10:49:34 idmc systemd[1]: rhcd.service: Failed with result 'exit-code'.
# rpm -q insights-client rhc rhc-worker-playbook
insights-client-3.1.7-9.el8_7.noarch
rhc-0.2.1-12.el8_7.x86_64
rhc-worker-playbook-0.1.8-4.el8_7.x86_64

Comment 3 Pino Toscano 2023-05-30 13:42:54 UTC

Just to confirm this once more: would it be possible to provide us with with the /etc/rhc/config.toml on your system, after the log-level change?
Also, which version of Satellite are you using?

Thanks!

Comment 4 Marko Myllynen 2023-05-30 14:11:13 UTC

I currently don't have the setup available anymore but it was against Satellite 6.12, haven't tested against 6.13. I'm 99.9% sure /etc/rhc/config.toml was exactly as provided by the RPM except for the log level change. Thanks.

Comment 5 RHEL Program Management 2023-09-07 13:58:34 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 6 RHEL Program Management 2023-09-07 14:03:13 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.