Project

Profile

Help

Issue #4086

ArtifactSaver stage is vulnerable to race conditions.

Added by jortel@redhat.com about 3 years ago. Updated over 2 years ago.

Status:
CLOSED - DUPLICATE
Priority:
High
Assignee:
-
Category:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

The ArtifactSaver stage creates Artifact using bulk_create() which will raise an IntegretyError on any constraint violation. The same artifact can be created concurrently during operations such as sync and upload when running more than 1 worker. The race condition exists between the QueryExistingArtifacts and ArtifactSaver stages. As a result, the un-handled IntegretyError will cause one of the operations to fail.

The impact on users is that syncs will randomly fail with an IntegretyError which will be very concerning.


Related issues

Is duplicate of Pulp - Issue #4060: QueryExistingArtifacts stage does not prevent duplicates within a streamCLOSED - CURRENTRELEASE<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by CodeHeeler about 3 years ago

  • Priority changed from Normal to High
  • Triaged changed from No to Yes

#2 Updated by jortel@redhat.com about 3 years ago

  • Description updated (diff)

#3 Updated by amacdona@redhat.com about 3 years ago

  • Is duplicate of Issue #4060: QueryExistingArtifacts stage does not prevent duplicates within a stream added

#4 Updated by amacdona@redhat.com about 3 years ago

  • Status changed from NEW to CLOSED - DUPLICATE

#5 Updated by daviddavis over 2 years ago

  • Sprint/Milestone set to 3.0.0

#6 Updated by bmbouter over 2 years ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF