I can't see the reserved resource records from the moment they are dispatched
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 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.
#4 Updated by bmbouter about 1 year ago
- Tracker changed from Story to Issue
- Subject changed from As a user, I can see the reserved resource records from the moment they are dispatched to I can't see the reserved resource records from the moment they are dispatched
- Severity set to 2. Medium
- Triaged set to No
Please register to edit this issue