Master node migration fails with: ssh: connect to host 10.109.34.6 port 22: No route to host

[Tatyanka]

Scenario:
0. Setup master node
1. Configuration releases
2. Bootstrap slave and make snapshot
3. Revert bootstrapped nodes
4. Create Fuel Environment
5. Add nodes to environment
6. Run network checker
7. Deploy environment
8. Run network checker
9. Migrate Fuel Master to a compute
10. Check periodically the status of Fuel Master migration process
11. Check that containers are up and running
12. Run network checker
13. Run health checker

Actual:
Migration fails according to connect to host 10.109.34.6 port 22: No route to host after reboot
 cecho 'Rebooting to begin the data sync process'
+ echo 'Rebooting to begin the data sync process'
+ umm on -c /usr/bin/fuel-migrate start
+ [[ on == \o\n ]]
+ /usr/bin/systemctl set-default umm-mg.target
rm '/etc/systemd/system/default.target'
ln -s '/etc/systemd/system/umm-mg.target' '/etc/systemd/system/default.target'
+ reboot
++ set +x
/usr/bin/fuel-migrate: line 1: 22859 Terminated reboot
+ cecho 'Start data sync phase'
+ echo 'Start data sync phase'
+ mv -f /root/fuel-migrate.var /root/fuel-migrate.var.old
+ wait_connection 600
++ date +%s
+ te=1453458067
+ ssh -o PasswordAuthentication=no -o ConnectTimeout=5 10.109.34.6 exit 0
ssh: connect to host 10.109.34.6 port 22: No route to host
+ sleep 2
++ date +%s
+ [[ 1453458067 -lt 1453457472 ]]
+ ssh -o PasswordAuthentication=no -o ConnectTimeout=5 10.109.34.6 exit 0
ssh: connect to host 10.109.34.6 port 22: No route to host
+ sleep 2
++ date +%s
+ [[ 1453458067 -lt 1453457475 ]]
+ ssh -o PasswordAuthentication=no -o ConnectTimeout=5 10.109.34.6 exit 0
ssh: connect to host 10.109.34.6 port 22: No route to host
+ sleep 2
++ date +%s

VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "8.0"
  api: "1.0"
  build_number: "466"
  build_id: "466"
  fuel-nailgun_sha: "f81311bbd6fee2665e3f96dcac55f72889b2f38c"
  python-fuelclient_sha: "4f234669cfe88a9406f4e438b1e1f74f1ef484a5"
  fuel-agent_sha: "6823f1d4005a634b8436109ab741a2194e2d32e0"
  fuel-nailgun-agent_sha: "b2bb466fd5bd92da614cdbd819d6999c510ebfb1"
  astute_sha: "b81577a5b7857c4be8748492bae1dec2fa89b446"
  fuel-library_sha: "fe03d887361eb80232e9914eae5b8d54304df781"
  fuel-ostf_sha: "ab5fd151fc6c1aa0b35bc2023631b1f4836ecd61"
  fuel-mirror_sha: "b62f3cce5321fd570c6589bc2684eab994c3f3f2"
  fuelmenu_sha: "fac143f4dfa75785758e72afbdc029693e94ff2b"
  shotgun_sha: "63645dea384a37dde5c01d4f8905566978e5d906"
  network-checker_sha: "9f0ba4577915ce1e77f5dc9c639a5ef66ca45896"
  fuel-upgrade_sha: "616a7490ec7199f69759e97e42f9b97dfc87e85b"
  fuelmain_sha: "727f7076f04cb0caccc9f305b149a2b5b5c2af3a"

[Peter Zhurba (pzhurba)]

fuel-migrate.log content and presence of some kernel crashes at dmes , allow us assume that main reason of issues may be following:
 e1000 driver
 vm kernel version
 host kernel version
 qemu version
 vm os version
 host version
 load of test host
 ....
 ....

Also analis at last passes of https://product-ci.infra.mirantis.net/view/8.0_swarm/job/8.0.system_test.ubuntu.fuel_master_migrate/ There is no one failure which looks like our.

Due to above, bug was closed. Feel free to reopen the bug by providing the requested information and set the bug status back to "New".