Issue #536: The RPM validate setting defaults to False, but it should default to True - RPM Support - Pulp

Actions

Send by e-mail Copy link

Issue #536

closed

The RPM validate setting defaults to False, but it should default to True

Added by rbarlow over 9 years ago. Updated almost 5 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

High

Assignee:

jortel@redhat.com

Sprint/Milestone:

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Version:

2.4.0

Platform Release:

3.0.0

OS:

Triaged:

Yes

Groomed:

Sprint Candidate:

Tags:

Easy Fix

Sprint:

Sprint 7

Quarter:

Description

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.

+ This bug was cloned from Bugzilla Bug #1145226 +

Related issues