Update k8s tests to check cluster creation inside testsuite
This change moves the check of the cluster creation to the testsuite.
In that way, the test can change depending on whether the juju controller
exists or doesn't exist.
Change-Id: I072c27061745ca8d8766d0dc1ded71a252cceef2
Signed-off-by: garciadeblas <gerardo.garciadeblas@telefonica.com>
diff --git a/robot-systest/testsuite/basic_22-cross_model_relations.robot b/robot-systest/testsuite/basic_22-cross_model_relations.robot
index c19f16d..625278d 100644
--- a/robot-systest/testsuite/basic_22-cross_model_relations.robot
+++ b/robot-systest/testsuite/basic_22-cross_model_relations.robot
@@ -70,6 +70,7 @@
Add K8s Cluster To OSM
[Documentation] Register K8s cluster in OSM.
Create K8s Cluster %{K8S_CREDENTIALS} ${K8SCLUSTER_VERSION} %{VIM_TARGET} %{VIM_MGMT_NET} ${K8SCLUSTER_NAME}
+ Check For K8s Cluster To Be Enabled ${K8SCLUSTER_NAME}
Instantiate Charm Network Service
[Documentation] Instantiate NS for the testsuite.