-
Bug
-
Resolution: Fixed
-
Critical
-
1.609.1
A deadlock has been observed between The OldDataMonitor and an AuthorizationStrategy.
When a job has a new build it will call save which will trigger the OldDataMonitor via the SaveableListener.
This will call referTo which in the case of a Run will lookup the parent Job via it's full name. This will perform a permission check .
Now if the authorization strategy is also being saved at the same time then it is highly likely that a deadlock will occur.
- is related to
-
JENKINS-30060 Listeners are called back whilst holding locks which is prone to deadlocks
-
- Open
-
- links to
[JENKINS-29936] deadlock between OldDataMonitor and AuthorizationStrategy.
Assignee | New: James Nord [ teilo ] |
Remote Link | New: This issue links to "PR 1796 (Web Link)" [ 13112 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Labels | Original: authorization deadlock | New: authorization deadlock lts-candidate |
Labels | Original: authorization deadlock lts-candidate | New: 1.609.3-fixed authorization deadlock |
Labels | Original: 1.609.3-fixed authorization deadlock | New: 1.609.3-fixed authorization deadlock lts-candidate |
Labels | Original: 1.609.3-fixed authorization deadlock lts-candidate | New: 1.609.3-fixed authorization deadlock |
Link | New: This issue is related to JENKINS-30060 [ JENKINS-30060 ] |
Workflow | Original: JNJira [ 165014 ] | New: JNJira + In-Review [ 197597 ] |