Actions
Issue #7438
closedcreate and update exporter should be async apis
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Katello
Sprint:
Sprint 93
Quarter:
Description
Currently create and update exporter are not async, and happen immediately. This cause a problem (or possibly just confusion) if these actions occur in the middle of an export.
Related issues
Updated by ggainey about 4 years ago
Updated by fao89 about 4 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 80
Updated by daviddavis almost 4 years ago
- Sprint/Milestone set to 3.12.0
- Sprint deleted (
Sprint 90)
Updated by mdellweg over 3 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to mdellweg
Updated by pulpbot over 3 years ago
- Status changed from ASSIGNED to POST
Updated by mdellweg over 3 years ago
- Copied to Issue #8451: create and update exporter should be async apis added
Added by mdellweg over 3 years ago
Updated by mdellweg over 3 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulpcore|2264c7eca36d24db1c865ef6e52b4e7dfac085cd.
Updated by pulpbot over 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Wrap Exporter update and destroy calls in tasks
Exporter is a resource that needs to be reserved to change it. Running an export task, while the exporter is being changed can lead to problems otherwise.
fixes #7438