e2e: ensure correct NRT data in pod running tests

make sure the NRT data looks correct before attempting to run a pod which consumes it. Signed-off-by: Francesco Romani <[email protected]>
ffromani · Mar 5, 2024 · 5fa216b · 5fa216b
1 parent 434d685
commit 5fa216b
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 0 deletions.
diff --git a/test/e2e/manifests.go b/test/e2e/manifests.go
@@ -101,6 +101,8 @@ var _ = ginkgo.Describe("[ManifestFlow] Deployer rendering", func() {
 					ginkgo.Skip("skipping the pod check - not enough resources")
 				}
 
+				expectNodeResourceTopologyData()
+
 				testNs := &corev1.Namespace{
 					ObjectMeta: metav1.ObjectMeta{
 						GenerateName: "tas-test-",

diff --git a/test/e2e/positive.go b/test/e2e/positive.go
@@ -277,6 +277,8 @@ var _ = ginkgo.Describe("[PositiveFlow] Deployer execution", func() {
 					ginkgo.Fail("no worker nodes found in the cluster")
 				}
 
+				expectNodeResourceTopologyData()
+
 				// min 1 reserved + min 1 allocatable = 2
 				nodes, err := e2enodes.FilterNodesWithEnoughCores(workerNodes, "2")
 				gomega.Expect(err).ToNot(gomega.HaveOccurred())
@@ -362,6 +364,8 @@ var _ = ginkgo.Describe("[PositiveFlow] Deployer execution", func() {
 					ginkgo.Skip("skipping the pod check - not enough resources")
 				}
 
+				expectNodeResourceTopologyData()
+
 				testNs := &corev1.Namespace{
 					ObjectMeta: metav1.ObjectMeta{
 						GenerateName: "tas-test-",