upstream/kubernetes
1
0
Fork 0
mirror of https://github.com/kubernetes/kubernetes.git synced 2026-06-09 08:55:55 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fix SELinux e2e tests waiting for "container created" event

Browse source 
A recent PR has changed the content of "Started container" event to "Container started".
Instead of checking the exact event message, check the event source
("kubelet") and reason ("Started"), that should uniquely identify the
event.
This commit is contained in:
Jan Safranek 2025-09-23 17:52:53 +02:00
parent 9f40c6f62c
commit 7930c2db4c
1 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
test/e2e/storage/csimock/csi_selinux_mount.go
View file

@ -353,7 +353,7 @@ var _ = utils.SIGDescribe("CSI Mock selinux on mount", func() {
} else {
// There is nothing blocking the second pod from starting, wait for the second pod to fullly start.
reason = string(events.StartedContainer)
msg = "Started container"
msg = "" // the message has changed in Kubernetes 1.35, the Reason must be enough.
}
}
eventSelector := fields.Set{
@ -361,6 +361,7 @@ var _ = utils.SIGDescribe("CSI Mock selinux on mount", func() {
"involvedObject.name": pod2.Name,
"involvedObject.namespace": pod2.Namespace,
"reason": reason,
"source": "kubelet",
}.AsSelector().String()
err = e2eevents.WaitTimeoutForEvent(ctx, m.cs, pod2.Namespace, eventSelector, msg, f.Timeouts.PodStart)
framework.ExpectNoError(err, "waiting for event %q in the second test pod", msg)