File system mdbci-lock stays after server restarting preventing tests from running
UPD: Possible solution: start_jenkins script clear locks.
After server restaring, lock files could saved in fact.
"destroy" cannot run, because directory with Vagrantfile can be deleted.
- script to:
-- find locks and delete it with VM stopping
-- find locks and delete it if VM does not exist
- automatically after server restart
- by hand, after server restart
#1 Updated by Timofey Turenko about 1 year ago
- Subject changed from Lock saved after server restarting to Lock stays locked forever server restarting
if host server rebooted vagrant_lock file stays forever
One part of solution is to check vagrant_lock file from start_jenkins.sh script when Jenkins is restarted, but the case when Jenkins slave is rebooted have to be checked (question: how Jenkins job behaves when slave is rebooted).
What can happen with snapshot_lock?