Bug 1384408

Summary:	Register clients: rhnreg_ks fail (timeout) due to network latency in a automated scenario.
Product:	[Community] Spacewalk	Reporter:	Dario Maiocchi <dmaiocchi>
Component:	Clients	Assignee:	Michael Mráka <mmraka>
Status:	CLOSED EOL	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.5	CC:	mmraka
Target Milestone:	---
Target Release:	---
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:	2019-07-12 11:19:16 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:

Description Dario Maiocchi 2016-10-13 09:01:18 UTC

Description of problem:
When testing automatically spacewalk , with some slow machines or with networks latency testscenarios, 

i noticed that rhnreg_ks fail because of a timeout.

I already modified networkRetries=1 --> 10 but it still failing. (from /etc/sysconfig/rhn/up2date )

Is there any chance to get an config-variable to modify the timeout for rhnreg_ks?

Best

Comment 1 Michael Mráka 2019-07-12 11:19:16 UTC

Spacewalk 2.8 (and older) has already reached it's End Of Life.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before end of life. If you would still like
to see this bug fixed and are able to reproduce it against current version
of Spacewalk 2.9, you are encouraged change the 'version' and re-open it.