[Jenkins] fix order in do_update procedure

Starting update after api geting ready

Change-Id: Ia484e076f89de1817e465820ce7d9153d890eb16

diff --git a/jenkins/build_cluster/build_cluster.py b/jenkins/build_cluster/build_cluster.py
index 3a3ba39ddc2550d3cb7f527e12326ca47c7c8e34..50e1ae7c0c5609b50175e5dc86632243d5094f60 100755 (executable)
--- a/jenkins/build_cluster/build_cluster.py
+++ b/jenkins/build_cluster/build_cluster.py
@@ -703,6 +703,10 @@ def main():
 
     inject_ifconfig_ssh()
 
+    start_slaves()
+
+    wait_for_api_is_ready()
+
     if cfg["UPDATE_FUEL"]=="true":
         if do_update(
             admin_ssh_conn_line(usr = cfg["FUEL_SSH_USERNAME"],subnet=cfg["ADMIN_SUBNET"]),
@@ -711,10 +715,6 @@ def main():
         else:
             print("ERROR: unable to update fuel")
 
-    start_slaves()
-
-    wait_for_api_is_ready()
-
     configure_nailgun()
 
     wait_for_cluster_is_ready()