Project

Profile

Help

Story #7986

closed

Task #7960: FIPS and support for ALLOWED_CONTENT_CHECKSUMS

As a user, I can evaluate a “what-if scenario” by generating a report of impacted content from a set of user provided checksums (not from ALLOWED_CONTENT_CHECKSUMS)

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

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 92
Quarter:

Description

For immediate content, it will give an idea of how long the switch to the new checksum setting might take (may need to just display the amount of content and provide docs a timeframe based on content count).

For on_demand content, show how many items will be unusable if a user doesn’t go back and download that content. It should also show what repos contain this content so users can download (or immediate sync) this content before switching.

For publications (rpm specific), produce a list of affected ones, so user knows what to republish (file separate task for this?)

Also, update this error message[0] to point users to how they can check on-demand content using this new tool.

[0] https://github.com/pulp/pulpcore/blob/94bb713f2a9f7a0c167305588fed47b039481045/pulpcore/app/settings.py#L347


Related issues

Blocks Pulp - Story #8325: Write a guide for changing ALLOWED_CONTENT_CHECKSUMSCLOSED - CURRENTRELEASEppicka

Actions

Also available in: Atom PDF