Open ElenaGrigore opened 1 year ago
Related to this: if a target is reserved, acquired, and then released without kick, it takes a good while before the reservation expires. Is this intended behavior? If not, it seems like release
should be made to always clean up the reservation table, i.e. the fix for this bug can be to make sure that a released target also lets go of its reservation right away.
Hi,
I have below scenario:
After step 3 , the board is not acquired by anyone , but it can be re-acquired/locked only by user1 because the reservation table still keeps a record of allocated for that place to user1 - is this the wanted behavior? Shouldn't kick be more aggressive and also clean the reservation?
and with the commands/output: user1: makes a reservation for a board:
user1: lock the board
user2: release --kick the board
After step 3 , the board is not acquired by anyone , but it can be re-acquired/locked only by user1