Refactor #4178
closed
Update sync to use ContentSaver Stage
100%
Description
We can't use the vanilla ContentSaver due to #4085.
Use of that stage should replace the use of the SerialContentSave stage, which should be deleted:
https://github.com/pulp/pulp_docker/blob/master/pulp_docker/app/tasks/dedupe_save.py#L69
After completion of this task, the entire dedupe_save will probably be able to be removed.
Related issues
Updated by amacdona@redhat.com about 6 years ago
- Copied from Refactor #4177: Update sync to use ArtifactSaver Stage added
Updated by amacdona@redhat.com about 6 years ago
- Related to Issue #4085: ContentUnitSaver stage is vulnerable to race conditions. added
Updated by amacdona@redhat.com almost 6 years ago
- Tags Pulp 3 RC Blocker added
Adding RC blocker since this is the plugin that made the updated ContentSaver stage necessary.
Updated by ipanova@redhat.com almost 6 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to ipanova@redhat.com
- Groomed changed from No to Yes
- Sprint Candidate changed from No to Yes
- Sprint set to Sprint 46
Updated by ipanova@redhat.com almost 6 years ago
- Status changed from ASSIGNED to NEW
- Assignee deleted (
ipanova@redhat.com) - Sprint deleted (
Sprint 47) - Tags deleted (
Pulp 3 RC Blocker)
https://github.com/pulp/pulp_docker/pull/294 closing this PR for now.
We cannot use ContentUnitSaver stage in docker plugin, because it expects all the artifacts downloaded and saved.
Current docker design skips the contents units if the artifacts have not been downloaded/saved yet https://github.com/pulp/pulp_docker/pull/294/files#diff-db9e748d164d25b2078d659910c68878L42
Updated by amacdona@redhat.com almost 6 years ago
- Blocked by Refactor #4173: Change the multilayered design to use Futures to handle nested content added
Updated by ipanova@redhat.com over 5 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to ipanova@redhat.com
- Sprint set to Sprint 50
Updated by ipanova@redhat.com over 5 years ago
- Status changed from ASSIGNED to POST
Added by ipanova@redhat.com over 5 years ago
Added by ipanova@redhat.com over 5 years ago
Revision 568c4a35 | View on GitHub
Use Futures to handle nested docker content.
https://pulp.plan.io/issues/4173 https://pulp.plan.io/issues/4178
Added by ipanova@redhat.com over 5 years ago
Revision 568c4a35 | View on GitHub
Use Futures to handle nested docker content.
https://pulp.plan.io/issues/4173 https://pulp.plan.io/issues/4178
Added by ipanova@redhat.com over 5 years ago
Revision 568c4a35 | View on GitHub
Use Futures to handle nested docker content.
https://pulp.plan.io/issues/4173 https://pulp.plan.io/issues/4178
Updated by ipanova@redhat.com over 5 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset commit:pulp_docker|568c4a350964a91cb8c4fedd86e255e29537c19e.
Updated by ipanova@redhat.com about 5 years ago
- Project changed from Docker Support to Container Support
Updated by bmbouter almost 5 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
.
Use Futures to handle nested docker content.
closes #4173 closes #4178
https://pulp.plan.io/issues/4173 https://pulp.plan.io/issues/4178