lock: allow unlock_one_safe to unlock same job#2121
Closed
lock: allow unlock_one_safe to unlock same job#2121
Conversation
Fix unlock_one_safe() to allow unlocking when the active job matches the current run/job id. Previously, it would refuse to unlock even when the same run was trying to clean up after itself. This change allows the same job to unlock machines it locked, which is necessary for proper cleanup when a job needs to unlock machines it's currently running on. Changes: - Allow unlock if active job matches current run id Signed-off-by: deepssin <deepssin@redhat.com>
Contributor
Author
|
Already handled by another PR |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix unlock_one_safe() to allow unlocking when the active job matches the current run/job id. Previously, it would refuse to unlock even when the same run was trying to clean up after itself.
This change allows the same job to unlock machines it locked, which is necessary for proper cleanup when a job needs to unlock machines it's currently running on.
Changes: