Bug 1828868

Summary:	Add keep alive option in Receptor node
Product:	Red Hat Satellite	Reporter:	Lindani Phiri <lphiri>
Component:	RH Cloud - Cloud Connector	Assignee:	Jason Stephens <jassteph>
Status:	CLOSED ERRATA	QA Contact:	Lukáš Hellebrandt <lhellebr>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.7.0	CC:	dehort, mhulan
Target Milestone:	6.8.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	receptor-0.6.2, ansiblerole-satellite-receptor-installer-0.6.6	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1832574 (view as bug list)		Environment:
Last Closed:	2020-10-27 13:02:11 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 Lindani Phiri 2020-04-28 13:43:01 UTC

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.

Comment 11 Lukáš Hellebrandt 2020-10-09 10:34:26 UTC

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.

Comment 14 errata-xmlrpc 2020-10-27 13:02:11 UTC

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