Actions
Issue #8430
closed
Pulp raises misleading message "Package matching query does not exist"
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
A user on pulp-list ran into this problem. Consider the case where you have a unique constraint for a Content unit that isn't part of the natural key. First, you hit this IntegrityError and Pulp assumes that there was a natural key conflict so it tries to look up the existing Content by natural key. However, since the unique constraint isn't part of the natural key, it hits a DoesNotExist and then logs "X matching query does not exist" which isn't helpful.
Related issues
Updated by pulpbot about 3 years ago
- Status changed from NEW to POST
Updated by daviddavis about 3 years ago
- Subject changed from Pulp raises unhelpful message "Package matching query does not exist" to Pulp raises misleading message "Package matching query does not exist"
Added by daviddavis about 3 years ago
Updated by daviddavis about 3 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulpcore|bd75e125adfd51108f7eb24c717379adb2775d6d.
Updated by pulpbot about 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Updated by dalley over 2 years ago
- Related to Issue #7828: syncing two repos with the same content at the same time results in an error added
Actions
.
Fix error for unique constraint violation
In the case where there's a unique constraint that isn't part of the natural key, using q() won't find the record. This erroneously raises a DoesNotExist exception.
fixes #8430