Project

Profile

Help

Story #7914

As an admin my pulp will not start if there are artifacts with forbidden checksums

Added by ipanova@redhat.com about 2 months ago. Updated about 2 months ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
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.

Associated revisions

Revision 39d395d9 View on GitHub
Added by ipanova@redhat.com about 2 months ago

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

History

#1 Updated by ipanova@redhat.com about 2 months ago

  • Description updated (diff)

#2 Updated by ipanova@redhat.com about 2 months ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ipanova@redhat.com
  • Sprint set to Sprint 86

#3 Updated by bmbouter about 2 months 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.

#4 Updated by ipanova@redhat.com about 2 months ago

  • Sprint/Milestone set to 3.9.0

#5 Updated by ipanova@redhat.com about 2 months ago

  • Status changed from ASSIGNED to POST

#6 Updated by rchan about 2 months ago

  • Sprint changed from Sprint 86 to Sprint 87

#7 Updated by ipanova@redhat.com about 2 months ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#8 Updated by pulpbot about 2 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF