Bug 1377754

Summary:	Customer RPM in custom Product has different file size and hash on Capsule VS Satellite server
Product:	Red Hat Satellite	Reporter:	Calvin Hartwell <chartwel>
Component:	Pulp	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WORKSFORME	QA Contact:	Katello QA List <katello-qa-list>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	6.2.1	CC:	bbuckingham, chartwel, egolov, fcami, mhrivnak
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-11 19:38:30 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 Calvin Hartwell 2016-09-20 14:20:40 UTC

Description of problem:

Customer has fresh install of Satellite 6.2.1 and just created some custom products, content views etc as per usual. They have been using Satellite 6.1 for several months with no issues.

They published some content views and synchronised them to some freshly built capsules but we are getting a mismatch on an RPM on the satellite server and the capsule server both in terms of file size and checksum (I ran sha256sum for example). 

When a client registered to the capsule attempts to install the package we get a 416 error and the package cannot be installed. 

I suspect this has been caused by this: https://pulp.plan.io/issues/1389
or this: https://pulp.plan.io/issues/494

We've only seen the issue with 1 RPM so far but we are wary that it might have affected other RPMS and or happen again in the future. 

Version-Release number of selected component (if applicable):

6.2.1
6.2.X

How reproducible:

Consistent

Steps to Reproduce:
1. Install sat6.2, setup capsules
2. Sync some custom repos, publish some content views including CCV to capsules
3. Register a client to the capsule
4. Install one of the custom packages on a host. 

Actual results:

Cannot install custom package

Expected results:

Customer should be able to install custom packages and sync capsules as required. 

Additional info:

Comment 3 Michael Hrivnak 2016-10-05 15:08:35 UTC

Did the customer upload the package in question, or did this problem arise only after doing syncs?

Is the problem reproducible with a particular RPM? If so, could we get a copy of it?

Or is there a more specific set of reproducer steps? How easy is it to reproduce this?

Comment 4 Michael Hrivnak 2017-01-11 19:38:30 UTC

If this is still an issue, feel free to re-open, or file a new issue with as much detail as possible on how to reproduce.