Project

General

Profile

Feature #23398

File system mdbci-lock stays after server restarting preventing tests from running

Added by Ilfat Kinyaev about 1 year ago. Updated about 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
MaxScale Tests
Start date:
22 Nov 2017
Due date:
Close

Description

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.

Proposed resolve:
- script to:
-- find locks and delete it with VM stopping
-- find locks and delete it if VM does not exist
Script run:
- automatically after server restart
- by hand, after server restart

History

#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?

#2 Updated by Timofey Turenko about 1 year ago

to be checked: if it is possible to run some script/job automatically when Jenkins slave or master restarted? Such script job can check all renaming locks and other artifacts (like shuttled off VMs)

#3 Updated by Timofey Turenko about 1 year ago

  • Subject changed from Lock stays locked forever server restarting to Lock stays locked forever after server restarting

#4 Updated by Andrey Vasilyev about 1 year ago

  • Subject changed from Lock stays locked forever after server restarting to File system mdbci-lock stays after server restarting preventing tests from running
  • Category set to MaxScale Tests

Also available in: Atom PDF