Bug 1306521

Summary:	Multiple HTTP connections interrupts capsule sync
Product:	Red Hat Satellite	Reporter:	Jitendra Yejare <jyejare>
Component:	Capsule	Assignee:	John Mitsch <jomitsch>
Status:	CLOSED WORKSFORME	QA Contact:	Jitendra Yejare <jyejare>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	Unspecified	CC:	bbuckingham, mmccune
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-30 11:11:27 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 Jitendra Yejare 2016-02-11 07:24:14 UTC

Description of problem:
Multiple HTTP connections interrupting capsule sync on upgraded capsule from 6.0.8.

Version-Release number of selected component (if applicable):
Satellite 6.1.7 Compose #1

How reproducible:


Steps to Reproduce:
1. On Sat 6.0.8, Sync some repos in satellite and publish, promote them to some environment.
2. Don't sync capsule before upgrading to latest 6.1.
3. Upgrade the satellite and capsule to latest 6.1 version.
4. Trigger the capsule sync from satellite using hammer sync command.
5. Observe /var/log/messages in capsule.

Actual results:
Multiple HTTP connection request from capsule to Satellite interrupts capsule sync and throws worker errors and finally stops the entire sync.

Logs are Here: http://pastebin.com/0vgW2Bbm

Expected results:
Capsule sync success.

Additional info:

Comment 3 Mike McCune 2016-03-03 06:14:58 UTC

There are no customer tickets aligned to this, moving out of 6.1.Z

Comment 5 John Mitsch 2016-06-22 14:41:55 UTC

I was not able to reproduce this on a 6.1 > 6.2 upgrade

Comment 6 Jitendra Yejare 2016-06-30 11:11:27 UTC

Verified ! 

@ Sat 6.2 GA Snap 18

Observation:
While syncing capsule with satellite, I saw HTTP connection requests but that doesnt halt the sync. And the sync completed successfully.

So closing this bug as WorksForMe !