Actions
Issue #3952
closed
Using the ErrataRelatedModelSaver can result in creating incomplete content.
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 42
Quarter:
Description
The insert of errata and all of its related tables need to be committed atomically. A fatal exception or worker crash between stages can result in storing an incomplete Errata.
Related issues
Updated by daviddavis about 6 years ago
- Blocked by Story #3953: ContentUnitSaver should support creating content with related models inside its transaction added
Updated by bmbouter about 6 years ago
- Tracker changed from Issue to Story
- % Done set to 0
Converting to story per triage convo. Thanks for filing @jortel.
Updated by bmbouter about 6 years ago
- Tracker changed from Story to Issue
- Severity set to 2. Medium
- Triaged set to No
The story work is happening in core, so I'm moving this to be a bugfix, which for pulp_rpm users it is.
Updated by bmbouter about 6 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to bmbouter
- Sprint set to Sprint 42
Adding to sprint as part of rpm sync work.
Updated by bmbouter about 6 years ago
- Status changed from ASSIGNED to POST
PR available at: https://github.com/pulp/pulp_rpm/pull/1178
Added by bmbouter about 6 years ago
Updated by bmbouter about 6 years ago
- Status changed from POST to MODIFIED
Applied in changeset 22d250ffd8c7124de9766d90844875c3264c03da.
Updated by bmbouter almost 5 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
.
Use ContentUnitSaver _post_save hook
The ErrataRelatedModelSaver stage is instead repurposed as a subclass of the ContentUnitSaver stage. This is currently the best way for related objects to be saved within the same transaction.
Required PR: https://github.com/pulp/pulp/pull/3621
https://pulp.plan.io/issues/3952 closes #3952
asdf