Actions
Issue #7414
closedChecksum model for distribution tree allows null value for a checksum
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 84
Quarter:
Description
The Checksum model for distribution tree allows a null
value for the checksum
field.. The checksum
field is a part of uniqueness constraint. Since it's allowed to be null
, and every null
is unique, it's possible to have duplicates.
There is a spec (somewhat outdated) https://release-engineering.github.io/productmd/treeinfo-1.0.html which seems to say that checksums should always be present.
I'm not sure about real world examples when checksum type is null
for this model, however the data migration needs to consider that theoretical possibility.
Actions
Checksum to not allow null
Removing allow_null from checksum field from checksum model.
closes: #7414 https://pulp.plan.io/issues/7414 [nocoverage]