Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Version-Release number of selected component (if applicable):
Satellite 6.9
After correcting a manifest (ref bz 1965023) for receptor to connect properly, the manifest information is not updated
Running the cloud connector playbook again will correct the certs in /etc/receptor/rh_accountnumber/ but the service still shows failures:
~~~
● receptor - Receptor Node for rh_accountnumber
Loaded: loaded (/etc/systemd/system/receptor@.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2021-04-05 06:11:07 EDT; 1 months 21 days ago
Main PID: 1287 (receptor)
CGroup: /system.slice/system-receptor.slice/receptor
└─1287 /usr/bin/python3 /usr/bin/receptor -c /etc/receptor/rh_accountnumber/receptor.conf -d /var/data/receptor/rh_accountnumber node
May 27 11:19:52 hostname.example.com receptor[1287]: aiohttp.client_exceptions.WSServerHandshakeError: 403, message='Invalid response status', url=URL('wss://cert.cloud.redhat.com/wss/
receptor-controller/gateway')
May 27 11:19:57 hostname.example.com receptor[1287]: ERROR 2021-05-27 11:19:57,122 aa4c5445-c8a0-4170-874b-45ed889d7a40 ws ws.connect
May 27 11:19:57 hostname.example.com receptor[1287]: Traceback (most recent call last):
May 27 11:19:57 hostname.example.com receptor[1287]: File "/usr/lib/python3.6/site-packages/receptor/connection/ws.py", line 53, in connect
May 27 11:19:57 hostname.example.com receptor[1287]: proxy=proxy, proxy_auth=proxy_auth
May 27 11:19:57 hostname.example.com receptor[1287]: File "/usr/lib64/python3.6/site-packages/aiohttp/client.py", line 1012, in __aenter__
May 27 11:19:57 hostname.example.com receptor[1287]: self._resp = await self._coro
May 27 11:19:57 hostname.example.com receptor[1287]: File "/usr/lib64/python3.6/site-packages/aiohttp/client.py", line 738, in _ws_connect
May 27 11:19:57 hostname.example.com receptor[1287]: headers=resp.headers)
May 27 11:19:57 hostname.example.com receptor[1287]: aiohttp.client_exceptions.WSServerHandshakeError: 403, message='Invalid response status', url=URL('wss://cert.cloud.redhat.com/wss/receptor-controller/gateway')
~~~
First I tried removing all content in /var/data/receptor and then in /etc/receptor, but the service still fails after these. Disabling the service with `systemctl disable --now receptor` and running the playbook after now allows the service to run without error:
~~~
● receptor - Receptor Node for rh_accountnumber
Loaded: loaded (/etc/systemd/system/receptor@.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2021-05-27 11:23:20 EDT; 26s ago
Main PID: 12049 (receptor)
CGroup: /system.slice/system-receptor.slice/receptor
└─12049 /usr/bin/python3 /usr/bin/receptor -c /etc/receptor/rh_accountnumber/receptor.conf -d /var/data/receptor/rh_accountnumber node
May 27 11:23:20 hostname.example.com systemd[1]: Started Receptor Node for rh_accountnumber.
~~~
So it looks like after corrections are made to receptor configs or config files it doesn't restart after those changes.
The manifest has no affect on the RHC based implementation of cloud connector as the credentials used by RHC are the Satellite certificates registered to the portal and API credentials to the Satellite itself. Given this, and our dropping of receptor since 6.11 I am opting to close this.