This job view page is being replaced by Spyglass soon. Check out the new job view.
PRfromanirh: e2e: node: re-enable the device plugin tests
ResultFAILURE
Tests 12 failed / 324 succeeded
Started2022-05-13 19:01
Elapsed53m46s
Revision0451ef31b6e46d5f4a597ffff8eb0fe18cf6ba88
Refs 109820

Test Failures


Kubernetes e2e suite [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications [Conformance] 18m32s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-apps\]\sStatefulSet\sBasic\sStatefulSet\sfunctionality\s\[StatefulSetBasic\]\sshould\sperform\srolling\supdates\sand\sroll\sbacks\sof\stemplate\smodifications\s\[Conformance\]$'
test/e2e/framework/framework.go:647
May 13 19:40:39.093: Failed waiting for state update: timed out waiting for the condition
test/e2e/apps/wait.go:124
				
				Click to see stdout/stderrfrom junit_24.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart http hook properly [NodeConformance] [Conformance] 9m11s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-node\]\sContainer\sLifecycle\sHook\swhen\screate\sa\spod\swith\slifecycle\shook\sshould\sexecute\spoststart\shttp\shook\sproperly\s\[NodeConformance\]\s\[Conformance\]$'
test/e2e/framework/framework.go:647
May 13 19:40:16.388: wait for pod "pod-with-poststart-http-hook" to disappear
Expected success, but got an error:
    <*pod.timeoutError | 0xc00438bfc0>: {
        msg: "timed out while waiting for pod container-lifecycle-hook-9536/pod-with-poststart-http-hook to disappear",
    }
    timed out while waiting for pod container-lifecycle-hook-9536/pod-with-poststart-http-hook to disappear
test/e2e/framework/pods.go:186
				
				Click to see stdout/stderrfrom junit_15.xml

Find pod-with-poststart-http-hook mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop http hook properly [NodeConformance] [Conformance] 4m56s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-node\]\sContainer\sLifecycle\sHook\swhen\screate\sa\spod\swith\slifecycle\shook\sshould\sexecute\sprestop\shttp\shook\sproperly\s\[NodeConformance\]\s\[Conformance\]$'
test/e2e/framework/framework.go:647
May 13 19:34:38.962: wait for pod "pod-with-prestop-http-hook" to disappear
Expected success, but got an error:
    <*pod.timeoutError | 0xc002ff2150>: {
        msg: "timed out while waiting for pod container-lifecycle-hook-9019/pod-with-prestop-http-hook to disappear",
    }
    timed out while waiting for pod container-lifecycle-hook-9019/pod-with-prestop-http-hook to disappear
test/e2e/framework/pods.go:186
				
				Click to see stdout/stderrfrom junit_16.xml

Find pod-with-prestop-http-hook mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-node] Container Runtime blackbox test on terminated container should report termination message from file when pod succeeds and TerminationMessagePolicy FallbackToLogsOnError is set [NodeConformance] [Conformance] 5m40s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-node\]\sContainer\sRuntime\sblackbox\stest\son\sterminated\scontainer\sshould\sreport\stermination\smessage\sfrom\sfile\swhen\spod\ssucceeds\sand\sTerminationMessagePolicy\sFallbackToLogsOnError\sis\sset\s\[NodeConformance\]\s\[Conformance\]$'
test/e2e/framework/framework.go:647
May 13 19:40:10.441: Timed out after 300.001s.
Expected
    <v1.PodPhase>: Running
to equal
    <v1.PodPhase>: Succeeded
test/e2e/common/node/runtime.go:156
				
				Click to see stdout/stderrfrom junit_10.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-node] Downward API should provide host IP as an env var [NodeConformance] [Conformance] 5m27s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-node\]\sDownward\sAPI\sshould\sprovide\shost\sIP\sas\san\senv\svar\s\[NodeConformance\]\s\[Conformance\]$'
test/e2e/framework/framework.go:647
May 13 19:45:42.818: Unexpected error:
    <*errors.errorString | 0xc002fedbf0>: {
        s: "expected pod \"downward-api-59b25149-8230-43be-a00a-a0b367d32eff\" success: timed out while waiting for pod downward-api-1927/downward-api-59b25149-8230-43be-a00a-a0b367d32eff to be Succeeded or Failed",
    }
    expected pod "downward-api-59b25149-8230-43be-a00a-a0b367d32eff" success: timed out while waiting for pod downward-api-1927/downward-api-59b25149-8230-43be-a00a-a0b367d32eff to be Succeeded or Failed
occurred
test/e2e/framework/util.go:770
				
				Click to see stdout/stderrfrom junit_03.xml

Find downward-api-59b25149-8230-43be-a00a-a0b367d32eff mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-node] Pods should delete a collection of pods [Conformance] 6m11s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-node\]\sPods\sshould\sdelete\sa\scollection\sof\spods\s\[Conformance\]$'
test/e2e/framework/framework.go:647
May 13 19:42:31.196: found a pod(s)
Unexpected error:
    <*errors.errorString | 0xc000204270>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
test/e2e/common/node/pods.go:886
				
				Click to see stdout/stderrfrom junit_19.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-node] Variable Expansion should fail substituting values in a volume subpath with absolute path [Slow] [Conformance] 4m59s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-node\]\sVariable\sExpansion\sshould\sfail\ssubstituting\svalues\sin\sa\svolume\ssubpath\swith\sabsolute\spath\s\[Slow\]\s\[Conformance\]$'
test/e2e/framework/framework.go:647
May 13 19:42:25.310: while waiting for the pod container to fail
Unexpected error:
    <*pod.timeoutError | 0xc0023eb650>: {
        msg: "timed out while waiting for pod var-expansion-1530/var-expansion-5c0b72ec-aa8c-460c-b6bc-793d84318693 to be container 0 failed with reason CreateContainerConfigError",
    }
    timed out while waiting for pod var-expansion-1530/var-expansion-5c0b72ec-aa8c-460c-b6bc-793d84318693 to be container 0 failed with reason CreateContainerConfigError
occurred
test/e2e/common/node/expansion.go:381
				
				Click to see stdout/stderrfrom junit_13.xml

Find container mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] ConfigMap should be consumable from pods in volume as non-root [NodeConformance] [Conformance] 6m3s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sConfigMap\sshould\sbe\sconsumable\sfrom\spods\sin\svolume\sas\snon\-root\s\[NodeConformance\]\s\[Conformance\]$'
test/e2e/framework/framework.go:647
May 13 19:40:17.607: Unexpected error:
    <*errors.errorString | 0xc0027d4670>: {
        s: "expected pod \"pod-configmaps-5bfab1ae-b85b-469d-9d15-7ea3b4febeb4\" success: timed out while waiting for pod configmap-4902/pod-configmaps-5bfab1ae-b85b-469d-9d15-7ea3b4febeb4 to be Succeeded or Failed",
    }
    expected pod "pod-configmaps-5bfab1ae-b85b-469d-9d15-7ea3b4febeb4" success: timed out while waiting for pod configmap-4902/pod-configmaps-5bfab1ae-b85b-469d-9d15-7ea3b4febeb4 to be Succeeded or Failed
occurred
test/e2e/framework/util.go:770
				
				Click to see stdout/stderrfrom junit_14.xml

Find pod-configmaps-5bfab1ae-b85b-469d-9d15-7ea3b4febeb4 mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] Downward API volume should provide node allocatable (cpu) as default cpu limit if the limit is not set [NodeConformance] [Conformance] 8m19s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sDownward\sAPI\svolume\sshould\sprovide\snode\sallocatable\s\(cpu\)\sas\sdefault\scpu\slimit\sif\sthe\slimit\sis\snot\sset\s\[NodeConformance\]\s\[Conformance\]$'
test/e2e/framework/framework.go:647
May 13 19:45:08.411: wait for pod "downwardapi-volume-2facb197-e2a9-4cba-9b47-065bd82594c6" to disappear
Expected success, but got an error:
    <*pod.timeoutError | 0xc001d0ec70>: {
        msg: "timed out while waiting for pod downward-api-1318/downwardapi-volume-2facb197-e2a9-4cba-9b47-065bd82594c6 to disappear",
    }
    timed out while waiting for pod downward-api-1318/downwardapi-volume-2facb197-e2a9-4cba-9b47-065bd82594c6 to disappear
test/e2e/framework/pods.go:186
				
				Click to see stdout/stderrfrom junit_11.xml

Find downwardapi-volume-2facb197-e2a9-4cba-9b47-065bd82594c6 mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] EmptyDir volumes volume on tmpfs should have the correct mode [LinuxOnly] [NodeConformance] [Conformance] 7m11s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sEmptyDir\svolumes\svolume\son\stmpfs\sshould\shave\sthe\scorrect\smode\s\[LinuxOnly\]\s\[NodeConformance\]\s\[Conformance\]$'
test/e2e/framework/framework.go:647
May 13 19:43:34.851: Unexpected error:
    <*errors.errorString | 0xc00221bfd0>: {
        s: "expected pod \"pod-cee0fa38-2147-455d-9760-64e321b0270a\" success: timed out while waiting for pod emptydir-5930/pod-cee0fa38-2147-455d-9760-64e321b0270a to be Succeeded or Failed",
    }
    expected pod "pod-cee0fa38-2147-455d-9760-64e321b0270a" success: timed out while waiting for pod emptydir-5930/pod-cee0fa38-2147-455d-9760-64e321b0270a to be Succeeded or Failed
occurred
test/e2e/framework/util.go:770
				
				Click to see stdout/stderrfrom junit_17.xml

Find pod-cee0fa38-2147-455d-9760-64e321b0270a mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] Projected downwardAPI should set mode on item file [LinuxOnly] [NodeConformance] [Conformance] 5m37s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sProjected\sdownwardAPI\sshould\sset\smode\son\sitem\sfile\s\[LinuxOnly\]\s\[NodeConformance\]\s\[Conformance\]$'
test/e2e/framework/framework.go:647
May 13 19:45:54.900: Unexpected error:
    <*errors.errorString | 0xc0027902b0>: {
        s: "expected pod \"downwardapi-volume-c2ff95cc-b608-4105-88f4-e338dcd3375e\" success: timed out while waiting for pod projected-8983/downwardapi-volume-c2ff95cc-b608-4105-88f4-e338dcd3375e to be Succeeded or Failed",
    }
    expected pod "downwardapi-volume-c2ff95cc-b608-4105-88f4-e338dcd3375e" success: timed out while waiting for pod projected-8983/downwardapi-volume-c2ff95cc-b608-4105-88f4-e338dcd3375e to be Succeeded or Failed
occurred
test/e2e/framework/util.go:770
				
				Click to see stdout/stderrfrom junit_08.xml

Find downwardapi-volume-c2ff95cc-b608-4105-88f4-e338dcd3375e mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] Subpath Atomic writer volumes should support subpaths with configmap pod with mountPath of existing file [Conformance] 6m15s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sSubpath\sAtomic\swriter\svolumes\sshould\ssupport\ssubpaths\swith\sconfigmap\spod\swith\smountPath\sof\sexisting\sfile\s\[Conformance\]$'
test/e2e/framework/framework.go:647
May 13 19:44:55.957: Unexpected error:
    <*errors.errorString | 0xc001dd8500>: {
        s: "expected pod \"pod-subpath-test-configmap-fg8f\" success: timed out while waiting for pod subpath-8231/pod-subpath-test-configmap-fg8f to be Succeeded or Failed",
    }
    expected pod "pod-subpath-test-configmap-fg8f" success: timed out while waiting for pod subpath-8231/pod-subpath-test-configmap-fg8f to be Succeeded or Failed
occurred
test/e2e/framework/util.go:770