Actions
Bug #18584
closedsemaphore gurading LDAP repos are created each time
Status:
Released
Priority:
N/A
Assignee:
Category:
Architecture - Internal libs
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Description
In place of being reuse, which mean that these semaphores don't do anything.
Updated by François ARMAND about 4 years ago
- Status changed from New to In progress
Updated by François ARMAND about 4 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/3373
Updated by François ARMAND about 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|33f7f0b8d9a5e58260dcadf7a3f792d687d9b3f2.
Updated by François ARMAND almost 4 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ almost 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.7 which was released today.
Updated by François ARMAND over 3 years ago
- Related to Bug #18983: A writeLock must never be in a read lock for LDAP repo added
Actions