Restart network and kill dhclient

Dirty hack for workaround network problems on CI envs.
When we deploy env some time after (few minutes) it change
resolv.conf into broken one. From this reason after bring up env we restart
network and kill dhclient. We also restart docker and kubelet to make
sure that all net-host containers are in good shape

Change-Id: I7965b692311a9b2e010a622151b195934d5c8f65
This commit is contained in:
Artur Zarzycki 2017-01-02 13:47:47 +01:00
parent ad16fbe211
commit 77ade87abf
1 changed files with 21 additions and 0 deletions

View File

@ -85,6 +85,27 @@ ${SSH_COMMAND} "sudo service ntp restart"
${SSH_COMMAND} "ssh -o StrictHostKeyChecking=no node2 sudo service ntp restart"
${SSH_COMMAND} "ssh -o StrictHostKeyChecking=no node3 sudo service ntp restart"
# Dirty hack for workaround network problems on CI envs.
# When we deploy env some time after (few minutes) it change resolv.conf into broken one
# From this reason after bring up env we restart network and and kill dhclient,
# we also restart docker and kubelet to make sure that all net-host containers are in good shape
cat > fix_dns.sh << EOF
sudo service networking restart
sudo pkill -9 dhclient
sudo service kubelet restart
sudo service docker restart
EOF
chmod +x fix_dns.sh
${SCP_COMMAND} fix_dns.sh vagrant@"${ADMIN_IP}":~/
${SSH_COMMAND} "scp -o StrictHostKeyChecking=no fix_dns.sh vagrant@node2:~/"
${SSH_COMMAND} "scp -o StrictHostKeyChecking=no fix_dns.sh vagrant@node3:~/"
${SSH_COMMAND} "sudo ./fix_dns.sh"
${SSH_COMMAND} "ssh -o StrictHostKeyChecking=no node2 sudo ./fix_dns.sh"
${SSH_COMMAND} "ssh -o StrictHostKeyChecking=no node3 sudo ./fix_dns.sh"
# Prepare env on "admin" VM:
if [ ${COMPONENT} == "full" ];then
${SCP_COMMAND} -r fuel-ccp/ vagrant@"${ADMIN_IP}":~/