Project

Profile

Help

Task #7156

Make node in new libvirt config to refer to new cloned machine

Added by Alexander Kaluzhny almost 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Normal
Category:
-
Sprint/Milestone:
Start date:
28.06.2016
Due date:
% Done:

0%

Estimated time:
0:30 h
Target branch:
Test scenario:

Prepare machine:
./mdbci --template spec/test_machine_configurations/7156_refer_old_node_to_new.json generate libvirt_test
2012
./mdbci up libvirt_test

Run:
path_to_nodes_libvirt=libvirt_test node0_libvirt=node0 rspec spec/unit/7156_refer_old_node_to_new_spec.rb

Excpect: 2 examples, 0 failures


Description

After investigation(https://dev.osll.ru/issues/7155). Implement function that makes node in new libvirt config to refer to new cloned machine.
Function should have two parameters:

Function should make node in copied config to refer to new cloned machine (with function from https://dev.osll.ru/issues/7142)
Function should be implemented in clone.rb in core/ directory.


Related issues

Related to [mdbci] Maria DB Continuous integration tool - Task #7100: Implement "mdbci clone <configuration> <new_path>" commandClosed22.06.2016

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by Alexander Kaluzhny almost 5 years ago

  • Copied from Task #7154: Make node in new docker config to refer to new cloned machine added

#2 Updated by Alexander Kaluzhny almost 5 years ago

  • File deleted (test.json)

#3 Updated by Alexander Kaluzhny almost 5 years ago

  • Copied from deleted (Task #7154: Make node in new docker config to refer to new cloned machine)

#4 Updated by Alexander Kaluzhny almost 5 years ago

  • Related to Task #7100: Implement "mdbci clone <configuration> <new_path>" command added

#5 Updated by Mark Zaslavskiy almost 5 years ago

  • Assignee set to Alexander Kaluzhny

#6 Updated by Alexander Kaluzhny almost 5 years ago

  • Status changed from New to Active / In progress

#7 Updated by Alexander Kaluzhny almost 5 years ago

  • Estimated time set to 0:30 h

#8 Updated by Alexander Kaluzhny almost 5 years ago

  • Status changed from Active / In progress to Review
  • Assignee changed from Alexander Kaluzhny to Mark Zaslavskiy
  • Test scenario updated (diff)

#9 Updated by Alexander Kaluzhny almost 5 years ago

  • Status changed from Review to Active / In progress
  • Assignee changed from Mark Zaslavskiy to Alexander Kaluzhny

#10 Updated by Alexander Kaluzhny almost 5 years ago

  • Status changed from Active / In progress to Review
  • Assignee changed from Alexander Kaluzhny to Mark Zaslavskiy

#11 Updated by Mark Zaslavskiy almost 5 years ago

Conflicts at pull-request

#12 Updated by Mark Zaslavskiy almost 5 years ago

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

#13 Updated by Alexander Kaluzhny almost 5 years ago

  • Status changed from New to Active / In progress

#15 Updated by Alexander Kaluzhny almost 5 years ago

  • Status changed from Active / In progress to Review

#16 Updated by Alexander Kaluzhny almost 5 years ago

  • Assignee changed from Alexander Kaluzhny to Mark Zaslavskiy

#17 Updated by Mark Zaslavskiy almost 5 years ago

  • Status changed from Review to Closed

Also available in: Atom PDF