Actions
Story #7914
closed
As an admin my pulp will not start if there are artifacts with forbidden checksums
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 87
Quarter:
Description
We have a check that prevents pulp to start if there are missing checksums. Add similar check that will prevent pulp to start if there would be found artifacts with forbidden checksums.
Updated by ipanova@redhat.com over 3 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to ipanova@redhat.com
- Sprint set to Sprint 86
Updated by bmbouter over 3 years ago
This looks right to me. It would be great for it to recommend to the user the command to run to fix it for them.
Updated by ipanova@redhat.com over 3 years ago
- Status changed from ASSIGNED to POST
Added by ipanova@redhat.com over 3 years ago
Updated by ipanova@redhat.com over 3 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulpcore|39d395d9751b5eec63069443715d00c64b3cee4e.
Updated by pulpbot over 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
.
As a user, I have artifacts compliant with the allowed checksums.
Enabled users to add/remove checksums to ALLOWED_CONTENT_CHECKSUMS. Added check for forbidden checksums. Added command to handle artifacts with missing and fobidden checksums.
closes #7561 closes #7914
https://pulp.plan.io/issues/7914 https://pulp.plan.io/issues/7561