Project

Profile

Help

Story #7914

closed

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

Added by ipanova@redhat.com almost 2 years ago. Updated almost 2 years 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.

Actions #1

Updated by ipanova@redhat.com almost 2 years ago

  • Description updated (diff)
Actions #2

Updated by ipanova@redhat.com almost 2 years ago

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

Updated by bmbouter almost 2 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.

Actions #4

Updated by ipanova@redhat.com almost 2 years ago

  • Sprint/Milestone set to 3.9.0
Actions #5

Updated by ipanova@redhat.com almost 2 years ago

  • Status changed from ASSIGNED to POST
Actions #6

Updated by rchan almost 2 years ago

  • Sprint changed from Sprint 86 to Sprint 87

Added by ipanova@redhat.com almost 2 years ago

Revision 39d395d9

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

Actions #7

Updated by ipanova@redhat.com almost 2 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions #8

Updated by pulpbot almost 2 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF