Story #7986
closedTask #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)
0%
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.
Related issues
Updated by daviddavis about 4 years ago
Note that we probably can't verify publications without parsing publications. I'd recommend we not do this requirement.
Updated by daviddavis almost 4 years ago
We also need a way to inspect the current state of the system (e.g. what on-demand content is currently unusable). So perhaps this could also evaluate the current set of ALLOWED_CONTENT_CHECKSUMS if no checksums are supplied.
Updated by daviddavis almost 4 years ago
- Sprint/Milestone set to 3.11.0
- Sprint set to Sprint 91
Updated by ggainey almost 4 years ago
This should extend the handle-content-checksums command - maybe adding a --dry-run option?
Updated by ppicka almost 4 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to ppicka
Updated by daviddavis almost 4 years ago
I started working on a rough PoC to report the on-demand content. It may be useful.
Updated by daviddavis almost 4 years ago
- Blocks Story #8325: Write a guide for changing ALLOWED_CONTENT_CHECKSUMS added
Updated by daviddavis almost 4 years ago
- Sprint/Milestone changed from 3.11.0 to 3.12.0
Updated by pulpbot almost 4 years ago
- Status changed from ASSIGNED to POST
Updated by ipanova@redhat.com almost 4 years ago
- Sprint/Milestone changed from 3.12.0 to 3.11.0
Added by ppicka over 3 years ago
Updated by ipanova@redhat.com over 3 years ago
- Status changed from POST to MODIFIED
Updated by ipanova@redhat.com over 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Artifact checksums report
reports local and remote artifacts with forbidden checksum type.
re #7986 https://pulp.plan.io/issues/7986