Pulp

Use case¶

Say you dispatch N repo sync's every 6 hours, where N is large > 500 repos. Then say the server's Pulp is syncing from are temporarily slow, so they tasks are backing up enough that another "set" of sync's are dispatched. The user would like to cancel enough sync's so that for each repository there is only one, but they cannot know which ones to cancel because the reserved_resource_records field is not yet set.

The issue¶

The records are being created in the resource_manager here but they should be created in the enqueue_with_reservation function when the task record itself is created.

Implementation¶

1. Move this code to the enqueue_with_reservation function here.
2. Ensure that the Task, ReservedResourceRecord, and TaskReservedResourceRecord are all created as one transaction.