Bug 1145226

Summary:	The RPM validate setting defaults to False, but it should default to True
Product:	[Retired] Pulp	Reporter:	Randy Barlow <rbarlow>
Component:	rpm-support	Assignee:	pulp-bugs
Status:	CLOSED UPSTREAM	QA Contact:	pulp-qe-list
Severity:	medium	Docs Contact:
Priority:	high
Version:	2.4.0	CC:	mhrivnak, skarmark
Target Milestone:	---	Keywords:	Triaged
Target Release:	3.0.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-28 22:21: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:
Embargoed:

Description Randy Barlow 2014-09-22 15:07:43 UTC

Description of problem:
We cannot change this until Pulp 3.0.0 due to semantic versioning issues, but the validate setting defaults to False and it would be better if it defaulted to True.

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

How reproducible:
Every time.

Steps to Reproduce:
1. Create an RPM repo with a feed that has corrupted RPMs. (You can corrupt an RPM by writing incorrect bytes over it.)
2. Do not set the validate flag at all.
3. Sync the repo.

Actual results:
Nothing will complain about the corrupted RPM.

Expected results:
The sync should complain about the RPM being corrupt.

Additional info:
This should not be fixed in any 2.Y release of Pulp, as it is an API change.

Comment 1 Brian Bouterse 2015-02-28 22:21:16 UTC

Moved to https://pulp.plan.io/issues/536