Issue #8445: Remote artifacts are being rejected by the artifact checksum check - Pulp

Actions

Send by e-mail Copy link

Issue #8445

closed

Task #7960: FIPS and support for ALLOWED_CONTENT_CHECKSUMS

Remote artifacts are being rejected by the artifact checksum check

Added by daviddavis over 3 years ago. Updated over 3 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

ppicka

Category:

Sprint/Milestone:

3.12.0

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Version:

Platform Release:

OS:

Triaged:

Yes

Groomed:

Sprint Candidate:

Tags:

Sprint:

Sprint 93

Quarter:

Description

As of today, the check for remote content has not been added (see #8423). However, it appears that remote content with forbidden checksums is getting rejected. This is problematic because the criteria for rejecting artifacts and remote artifacts differs and it appears that the criteria for artifacts is being applied to remote artifacts.

Steps to reproduce:

name="md5-$RANDOM"
url="https://fixtures.pulpproject.org/rpm-with-md5/"
policy="on_demand"

pulp rpm remote create --name $name --url $url --policy $policy
pulp rpm repository create --name $name --remote $name
pulp rpm repository sync --name $name

Result:

Error: Task /pulp/api/v3/tasks/5696b620-2965-414c-967f-fd6adb1f8aea/ failed: 'Artifact contains forbidden checksum type md5. You can allow it with 'ALLOWED_CONTENT_CHECKSUMS' setting.'

Actions

Copy link

Updated by daviddavis over 3 years ago

Subject changed from The stages code rejects remote artifacts that have forbidden checksums to Remote artifacts are being rejected by the artifact checksum check

Actions

Copy link