We have found that sometimes proxies do not send Websocket disconnection messages to the client in the Receptor node. In this state, the Cloud Connector connection is not usable and the Find It Fix execution will fail until the Satellite receptor nodes are manually started. This is can easily be resolved by enabling in built websocket keep alive mechanism. This has been resolved upstream and needs to added to the Satellite receptor RPM: https://github.com/project-receptor/receptor/issues/210 https://github.com/project-receptor/receptor/pull/211 We may also need to update the cloud to set the heartbeat value.
Verified with Sat 6.8 snap 18. 1) Installed Receptor-satellite, straced to the running process and watched traffic. There was periodical outgoing message. When I changed ws_heartbeat to 5 (default 1800) and bounced the service, there were more messages. So the heartbeat is indeed active. # strace -p 9020 -f -e trace=network -s 10000 2) After ~24 hours, I tried to apply a remediation through the Satellite. It was applied successfully.
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 (Important: Satellite 6.8 release), 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/RHSA-2020:4366