Actions
Issue #8683
closed
re-uploading an existing advisory makes new advisory upload fails
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 97
Quarter:
Description
Starting with a clean Pulp:
- upload an advisory
- upload the same advisory again (it will fail because it already exists)
- upload any new advisory and they will all fail
Versions:
python3-pulpcore-3.9.1-2.el8.noarch python3-pulp-rpm-3.10.0-1.el8.noarch
Related issues
Updated by guialemas almost 3 years ago
from ggainey on IRC: "select count(*) from rpm_updaterecord where digest = ''; shows one entry and further uploads fail
Updated by ggainey almost 3 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to ggainey
Updated by ggainey almost 3 years ago
Here's where the problem comes from, and a Giant Hammer for fixing it:
https://github.com/ggainey/pulp_rpm/commit/805aa8f2eb737a2d888011dffc4dc886aa95f275
Not ready to submit as a PR yet.
Updated by pulpbot almost 3 years ago
- Status changed from ASSIGNED to POST
Updated by ggainey almost 3 years ago
- Related to Issue #8708: Tasking: Uploading many advisories in a row can have intermittent failures added
Updated by ggainey almost 3 years ago
- Related to Issue #8716: Advisory-digest-calculation can result in the 'same' advisory having different digests added
Updated by dalley almost 3 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 96
Added by ggainey almost 3 years ago
Updated by ggainey almost 3 years ago
- Status changed from POST to MODIFIED
Applied in changeset e0570897ed9ec6f68b067444e3f2433e18e8fc8a.
Updated by pulpbot almost 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
.
Handle temporary-blank-digest advisory in create() error path(s).
Prior to this fix, a failure in create() would result in being unable to create() advisories again, ever, until the advisory with a blank digest is removed "by hand".
fixes #8683