Adding more logs to debug cluster deletion failure

Signed-off-by: Muhammad Adil Ghaffar <muhammad.adil.ghaffar@est.tech>
metal3-io · Oct 16, 2024 · 6ef8067 · 6ef8067
1 parent 0a96a82
commit 6ef8067
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 1 deletion.
diff --git a/test/e2e/common.go b/test/e2e/common.go
@@ -150,6 +150,11 @@ func DumpSpecResourcesAndCleanup(ctx context.Context, specName string, clusterPr
 			Namespace: namespace,
 		}, intervalsGetter(specName, "wait-delete-cluster")...)
 
+		// Listing bmh, m3m and machines once deletion is done
+		ListBareMetalHosts(ctx, clusterClient, client.InNamespace(namespace))
+		ListMetal3Machines(ctx, clusterClient, client.InNamespace(namespace))
+		ListMachines(ctx, clusterClient, client.InNamespace(namespace))
+
 		// Waiting for Metal3Datas, Metal3DataTemplates and Metal3DataClaims, as these may take longer time to delete
 		By("Checking leftover Metal3Datas, Metal3DataTemplates and Metal3DataClaims")
 		Eventually(func(g Gomega) {

diff --git a/test/e2e/config/e2e_conf.yaml b/test/e2e/config/e2e_conf.yaml
@@ -216,7 +216,7 @@ intervals:
   default/wait-cluster: ["20m", "30s"] # The second time to check the availibility of the cluster should happen late, so kcp object has time to be created
   default/wait-control-plane: ["30m", "10s"]
   default/wait-worker-nodes: ["60m", "10s"]
-  default/wait-delete-cluster: ["20m", "10s"]
+  default/wait-delete-cluster: ["40m", "10s"]
   default/wait-machine-upgrade: ["50m", "10s"]
   default/wait-machine-remediation: ["30m", "10s"]
   default/wait-vm-state: ["20m", "100ms"]