Project

Profile

Help

Task #7663

Vagrant lock is not released http://max-tst-01.mariadb.com:8089/view/test/job/run_test_snapshot/14/consoleFull

Added by Mark Zaslavskiy over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
High
Assignee:
Timofey Turenko
Category:
jenkins_jobs
Sprint/Milestone:
Start date:
19.10.2016
Due date:
% Done:

0%

Estimated time:
Target branch:
Test scenario:

https://github.com/mariadb-corporation/maxscale-jenkins-jobs/pull/90/files

http://max-tst-01.mariadb.com:8089/job/validate_yaml_by_pushes/105/console

Test

Run and abort in about 5 seconds
http://maxscale-jenkins.mariadb.com:8090/job/7663_run_test_snapshot/

Check that was triggered
http://maxscale-jenkins.mariadb.com:8090/job/7663_smart_remove_lock_snapshot/
http://maxscale-jenkins.mariadb.com:8090/job/remove_lock_snapshot/
http://maxscale-jenkins.mariadb.com:8090/job/smart_remove_lock/


History

#1 Updated by Mark Zaslavskiy over 3 years ago

10:58] 
По поводу лока - очевидной причины не вижу, создал задачу https://dev.osll.ru/issues/7663

[10:58] 
пока подозреваю что проблема может быть в недавних правках build-scripts-vagrant

new messages
[10:59] 
timofey.turenko vagrant@ns3014560:~/build-scripts$ cat ~/vagrant_lock
run_test_snapshot-14

11:00]
mark.zaslavskiy а там по идее свой лок - /home/vagrant/mdbci/monitoring_of_particular_branch_set_in_maxscale-bsl-20/snapshot_lock

[11:00]
http://max-tst-01.mariadb.com:8089/job/smart_remove_lock_snapshot/10/console

new messages
[11:01]
timofey.turenko но этот поставлен и дальше ничего не работает

#2 Updated by Mark Zaslavskiy over 3 years ago

  • Description updated (diff)

#3 Updated by Mark Zaslavskiy over 3 years ago

  • Subject changed from Lock is not released http://max-tst-01.mariadb.com:8089/view/test/job/run_test_snapshot/14/consoleFull to Snapshot lock is not released http://max-tst-01.mariadb.com:8089/view/test/job/run_test_snapshot/14/consoleFull

#4 Updated by Mark Zaslavskiy over 3 years ago

  • Subject changed from Snapshot lock is not released http://max-tst-01.mariadb.com:8089/view/test/job/run_test_snapshot/14/consoleFull to Vagrant lock is not released http://max-tst-01.mariadb.com:8089/view/test/job/run_test_snapshot/14/consoleFull

#5 Updated by Mark Zaslavskiy over 3 years ago

  • Description updated (diff)

#6 Updated by Mark Zaslavskiy over 3 years ago

  • Description updated (diff)

#8 Updated by Alexander Kaluzhny over 3 years ago

  • Test scenario updated (diff)

#9 Updated by Mark Zaslavskiy over 3 years ago

  • Status changed from Review to New
  • Assignee changed from Mark Zaslavskiy to Alexander Kaluzhny

There are no results for "0. Check why http://max-tst-01.mariadb.com:8089/job/smart_remove_lock_snapshot/10/console failed" action point. Please comment.

#10 Updated by Alexander Kaluzhny over 3 years ago

Mark Zaslavskiy wrote:

There are no results for "0. Check why http://max-tst-01.mariadb.com:8089/job/smart_remove_lock_snapshot/10/console failed" action point. Please comment.

It's common behavior because lock is deleted in run_test_snapshot_sh script.

#11 Updated by Alexander Kaluzhny over 3 years ago

  • Status changed from New to Review
  • Assignee changed from Alexander Kaluzhny to Mark Zaslavskiy

#12 Updated by Mark Zaslavskiy over 3 years ago

  • Status changed from Review to Testing
  • Assignee changed from Mark Zaslavskiy to Timofey Turenko

#13 Updated by Timofey Turenko over 3 years ago

  • Status changed from Testing to Reopened

it tries to remove lock from wrong place:
http://max-tst-01.mariadb.com:8089/job/smart_remove_lock_snapshot/41/console

cat: /home/vagrant/mdbci/monitoring_of_particular_branch_set_in_maxscale-bsl-218/snapshot_lock: No such file or directory

aborted build http://max-tst-01.mariadb.com:8089/view/test/job/run_test_snapshot/107/console worked with 'centos_7_libvirt-mariadb-10.0-permanent', lock is in ~/mdbci/centos_7_libvirt-mariadb-10.0-permanent/snapshot_lock file

#14 Updated by Alexander Kaluzhny over 3 years ago

  • Status changed from Reopened to New
  • Assignee changed from Timofey Turenko to Alexander Kaluzhny

#15 Updated by Alexander Kaluzhny over 3 years ago

  • Status changed from New to Testing
  • Assignee changed from Alexander Kaluzhny to Timofey Turenko

#16 Updated by Timofey Turenko over 3 years ago

  • Status changed from Testing to Reopened

The problem appears if shanshot revert failed and run_test_snapshot is trying to restart constantly running VMs. In this case create_config.sh script sets vangrant_lock which is not removed in case of job abort.

#17 Updated by Timofey Turenko over 3 years ago

  • Status changed from Reopened to Closed

closing. Works! It takes some time until vagrant_lock is removed

Also available in: Atom PDF