Bug 2040788

Summary:	Synchronizations timeout when syncing from Red Hat CDN
Product:	Red Hat Satellite	Reporter:	Mike McCune <mmccune>
Component:	Repositories	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Cole Higgins <chiggins>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.10.1	CC:	jsherril
Target Milestone:	6.11.0	Keywords:	Triaged
Target Release:	Unused
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:	2022-01-27 18:36:47 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 Mike McCune 2022-01-14 17:15:43 UTC

We have a set of customers hitting timeout errors when syncing from cdn.redhat.com only with Satellite 6.10. 

 "Request timed out for https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os/repodata/f6db0e620345bc404d1729a4a58e177ea68c91c2-other.xml.gz. 

Increasing the total_timeout value on the remote might help."

This is new behavior with 6.10 as customers have not reported this timeout error or deadlocked syncs with 6.9 and prior. THere is a KCS to increase the timeout:

https://access.redhat.com/solutions/6552991

We should consider a few immediate actions:

1) Increase the default to a higher value to work around the effect of errors during a sync

2) Continue to investigate with EXD if the changelog entries in our metadata are getting bigger than necessary.

3) Investigate if there is a bug in our synchronization code that is causing downloads to take longer than expected or we are hitting timeouts earlier than expected.

Comment 1 Mike McCune 2022-01-14 17:37:14 UTC

NOTE: that https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os/repodata/f6db0e620345bc404d1729a4a58e177ea68c91c2-other.xml.gz is almost 1GB in size so slower connections very well may hit the 5 minute limit.

Comment 2 Justin Sherrill 2022-01-27 18:36:47 UTC


*** This bug has been marked as a duplicate of bug 2043144 ***