Change:
// Verify PodReady is not set (since sandboxcreation is blocked) _, err = getTransitionTimeForPodConditionWithStatus(p, v1.PodReady, false) framework.ExpectNoError(err) <ins> // this testcase is creating the missing volume that unblock the pod above, // and check PodReadyToStartContainer is setting correctly. ginkgo.By("checking pod condition for a pod when volumes source is created") configmap := v1.ConfigMap{ ObjectMeta: metav1.ObjectMeta{ Name: "cm-that-unblock-pod-condition", }, Data: map[string]string{ "key": "value", }, BinaryData: map[string][]byte{ "binaryKey": []byte("value"), }, } _, err = f.ClientSet.CoreV1().ConfigMaps(f.Namespace.Name).Create(ctx, &configmap, metav1.CreateOptions{}) framework.ExpectNoError(err) defer func() { err = f.ClientSet.CoreV1().ConfigMaps(f.Namespace.Name).Delete(ctx, "cm-that-unblock-pod-condition", metav1.DeleteOptions{}) framework.ExpectNoError(err, "unable to delete configmap") }() p2 := webserverPodSpec("pod2-"+string(uuid.NewUUID()), "web2", "init2", hasInitContainers) p2.Spec.Volumes = []v1.Volume{ { Name: "cm-2", VolumeSource: v1.VolumeSource{ ConfigMap: &v1.ConfigMapVolumeSource{ LocalObjectReference: v1.LocalObjectReference{Name: "cm-that-unblock-pod-condition"}, }, }, }, } p2.Spec.Containers[0].VolumeMounts = []v1.VolumeMount{ { Name:      "cm-2", MountPath: "/config", }, } p2 = e2epod.NewPodClient(f).Create(ctx, p2) framework.ExpectNoError(e2epod.WaitTimeoutForPodReadyInNamespace(ctx, f.ClientSet, p2.Name, p2.Namespace, framework.PodStartTimeout)) p2, err = e2epod.NewPodClient(f).Get(ctx, p2.Name, metav1.GetOptions{}) framework.ExpectNoError(err) _, err = getTransitionTimeForPodConditionWithStatus(p2, v1.PodScheduled, true) framework.ExpectNoError(err) _, err = getTransitionTimeForPodConditionWithStatus(p2, v1.PodInitialized, true) framework.ExpectNoError(err) // Verify PodReadyToStartContainers is set (since sandboxcreation is unblocked) if checkPodReadyToStart { _, err = getTransitionTimeForPodConditionWithStatus(p2, v1.PodReadyToStartContainers, true) framework.ExpectNoError(err) } </ins> } }

Discussion:
Two serial tests from sig-node are keep failing: E2eNode Suite. E2eNode Suite. pls see: [1] [2] <fmt.wrapError | 0x40005e7840: failed to update pod "pod--65da-42b7-a6a5-": Pod "pod--65da-42b7-a6a5-" is invalid: spec: Forbidden: pod updates may not change fields other than ,,, (only additions to existing tolerations), (allow it to be set to 1 if it was previously negative) core.PodSpec{ Volumes: []core.Volume{ { Name: "cm", Name: "secret", VolumeSource: core.VolumeSource{ ... // 3 identical fields AWSElasticBlockStore: nil, GitRepo: nil, Secret: nil, Secret: &core.SecretVolumeSource{SecretName: "secret", DefaultMode: &420}, NFS: nil, ISCSI: nil, ... // 9 identical fields FC: nil, AzureFile: nil, ConfigMap: &core.ConfigMapVolumeSource{ LocalObjectReference: core.LocalObjectReference{Name: "does-not-exist"}, DefaultMode: &420, }, ConfigMap: nil, VsphereVolume: nil, AzureDisk: nil, ... // 7 identical fields }, }, }, InitContainers: {{Name: "init1", Image: "", Command: {"sh", "-c", "sleep 5s"}, TerminationMessagePath: "/dev/termination-log", ...}}, Containers: []core.Container{ { ... // 9 identical fields ResizePolicy: nil, RestartPolicy: nil, VolumeMounts: []core.VolumeMount{ { Name: "cm", Name: "secret", ReadOnly: false, MountPath: "/config", ... // 3 identical fields }, }, VolumeDevices: nil, LivenessProbe: nil, ... // 10 identical fields }, }, EphemeralContainers: nil, RestartPolicy: "Always", ... // 28 identical fields } happened since 18/10/23 run the e2e testcases manually No response <details</details<detailsImpacts all </details<details</details<details</details<details</details<details</details
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance.

The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign /cc
cc
failed on x86 as well:
/sig node
/unassign
is merged today. /cc
will take a look at this ASAP /assign
and I are sorry for the issue this caused. We decided to open to fix this issue. I think this test was more complicated than we thought. Sorry for this.