Project

Profile

Help

Issue #4086

ArtifactSaver stage is vulnerable to race conditions.

Added by jortel@redhat.com over 1 year ago. Updated about 1 year ago.

Status:
CLOSED - DUPLICATE
Priority:
High
Assignee:
-
Category:
-
Sprint/Milestone:
Start date:
Due date:
Severity:
2. Medium
Version:
Platform Release:
Blocks Release:
OS:
Backwards Incompatible:
No
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

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

Duplicates Pulp - Issue #4060: QueryExistingArtifacts stage does not prevent duplicates within a stream CLOSED - CURRENTRELEASE Actions

History

#1 Updated by CodeHeeler over 1 year ago

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

#2 Updated by jortel@redhat.com over 1 year ago

  • Description updated (diff)

#3 Updated by amacdona@redhat.com over 1 year ago

  • Duplicates Issue #4060: QueryExistingArtifacts stage does not prevent duplicates within a stream added

#4 Updated by amacdona@redhat.com over 1 year ago

  • Status changed from NEW to CLOSED - DUPLICATE

#5 Updated by daviddavis about 1 year ago

  • Sprint/Milestone set to 3.0.0

#6 Updated by bmbouter about 1 year ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF