Project

Profile

Help

Send by e-mail

Bug #7359

wrong path in AWS check script in restore and create shanpshot jobs

Added by Timofey Turenko over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
High
Assignee:
Timofey Turenko
Category:
mdbci features
Sprint/Milestone:
0.9
Start date:
05.08.2016
Due date:
% Done:

100%

Estimated time:
0:30 h
Spent time:
2:00 h
Target branch:
Test scenario:

https://github.com/mariadb-corporation/maxscale-jenkins-jobs/tree/7359_wrong_path_in_AWS_check_script
https://github.com/mariadb-corporation/maxscale-jenkins-jobs/pull/63

# 1. Generate node at "/home/vagranttest
/mdbci" (echo $? => 0)
./mdbci --template confs/docker_lite.json generate SOME_DIR

# 2. Up nodes.
./mdbci up SOME_DIR

# 3. Create snapshot with job (path: SOME_DIR, result: success created snapshot) :
http://maxscale-jenkins.mariadb.com:8090/view/All/job/create_snapshot/build?delay=0sec

# 4. Restore snapshot with job (path: SOME_DIR, result: success restore snapshot):
http://maxscale-jenkins.mariadb.com:8090/view/All/job/restore_snapshot/build?delay=0sec

# Results: in console output cat command should search in absolute path and it must be created.

Description

Comment says: "Relative path in ~/mdbci folder for RUNING configuration. ", but in fact script using absolute path:

aws=`cat $environment_name/provider | grep -o aws | wc -l`

as result:

++ cat develop-jun14//provider
++ grep -o aws
++ wc -l
cat: develop-jun14//provider: No such file or directory
+ aws=0
log_up.txt (184 KB) Ilfat Kinyaev, 29.08.2016 19:14 log_up.txt

History

#1 Updated by Mark Zaslavskiy over 3 years ago

  • Category set to mdbci features
  • Assignee set to Mark Zaslavskiy
  • Sprint/Milestone set to 0.9

#2 Updated by Mark Zaslavskiy over 3 years ago

  • Priority changed from Normal to High

#3 Updated by Mark Zaslavskiy over 3 years ago

  • Assignee changed from Mark Zaslavskiy to Ilfat Kinyaev

#4 Updated by Ilfat Kinyaev over 3 years ago

  • Estimated time set to 0:30 h

#5 Updated by Ilfat Kinyaev over 3 years ago

  • Status changed from New to Active / In progress

#6 Updated by Ilfat Kinyaev over 3 years ago

  • % Done changed from 0 to 80
  • Test scenario updated (diff)

#8 Updated by Ilfat Kinyaev over 3 years ago

  • Status changed from Active / In progress to New

#9 Updated by Ilfat Kinyaev over 3 years ago

LOCK: AWS confs not upping, console output in the attachment.

#10 Updated by Ilfat Kinyaev over 3 years ago

#11 Updated by Ilfat Kinyaev over 3 years ago

  • Status changed from New to Active / In progress

#12 Updated by Ilfat Kinyaev over 3 years ago

  • Test scenario updated (diff)

#13 Updated by Ilfat Kinyaev over 3 years ago

  • Status changed from Active / In progress to Review
  • Assignee changed from Ilfat Kinyaev to Mark Zaslavskiy
  • % Done changed from 80 to 100

#14 Updated by Mark Zaslavskiy over 3 years ago

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

#15 Updated by Timofey Turenko over 3 years ago

  • Status changed from Testing to Closed
Send by e-mail

Also available in: Atom PDF