Bug 1145226 - The RPM validate setting defaults to False, but it should default to True
Summary: The RPM validate setting defaults to False, but it should default to True
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Pulp
Classification: Retired
Component: rpm-support
Version: 2.4.0
Hardware: All
OS: Linux
high
medium
Target Milestone: ---
: 3.0.0
Assignee: pulp-bugs
QA Contact: pulp-qe-list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-22 15:07 UTC by Randy Barlow
Modified: 2015-02-28 22:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-28 22:21:16 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Pulp Redmine 536 0 None None None Never

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
Note You need to log in before you can comment on or make changes to this bug.