You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
(venv) user2@ws2:~/test$ labgrid-client -p RO--MX6Q_sabresd--2 release --kick
warning: kicking user (workstation1/user1)
released place RO--MX6Q_sabresd--2
After step 3 , the board is not acquired by anyone , but it can be re-acquired/locked only by user1
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
The text was updated successfully, but these errors were encountered: