node: e2e: memorymgr: Fix test failure

The change made in https://github.com/kubernetes/kubernetes/pull/112644
resulted in an update to the rejection message. In the memory manager
node e2e test, we still checked against the old expected error message
giving the impression that the pod succeeded to run even though it failed
as expected mainly because the check wasn't performed correctly.

In this patch, we update to the correct rejection message to make sure
that the memory manager is no longer failing.

NOTE: This test is supposed to run on multi NUMA systems and if the
underlying node does not have multi NUMA nodes, the test is skipped
which is what happens in upstream test infrastructure as it is mainly
composed of single NUMA nodes. Because of this, this test failure
wasn't evident via testgrid.

Signed-off-by: Swati Sehgal <swsehgal@redhat.com>
This commit is contained in:
Swati Sehgal 2022-10-13 11:33:24 +01:00
parent 525280d285
commit 6c6865af28

View File

@ -621,7 +621,7 @@ var _ = SIGDescribe("Memory Manager [Disruptive] [Serial] [Feature:MemoryManager
return false
}
if !strings.Contains(tmpPod.Status.Message, "Pod Allocate failed due to [memorymanager]") {
if !strings.Contains(tmpPod.Status.Message, "Allocate failed due to [memorymanager]") {
return false
}