Make initial cluster setup more robust

Action "reset" triggers cluster shutdown attempt which will cause
failure of subsequent calls for cluster status.

Issue-ID: INT-1571
Change-Id: I4e607358fbeb910a250ac038cfc43682fb94bdea
Signed-off-by: Pawel Wieczorek <p.wieczorek2@samsung.com>
(cherry picked from commit 782390acef88ade323003fd12f26e0ffa9ef27a0)

diff --git a/test/security/check_versions/env/Vagrantfile b/test/security/check_versions/env/Vagrantfile
index 28abbc5..9753a74 100644 (file)
--- a/test/security/check_versions/env/Vagrantfile
+++ b/test/security/check_versions/env/Vagrantfile
@@ -27,7 +27,8 @@ Vagrant.configure("2") do |config|
        end
        config.vm.provision :reload;
        config.vm.provision "shell", privileged: false, inline: <<-end
-               microk8s reset &&\
+               microk8s start &&\
+               microk8s status --wait-ready &&\
                microk8s config > /home/vagrant/.kube/config &&\
                microk8s kubectl apply -f /home/vagrant/k8s_bin_versions_inspector/env/configuration
        end