This job view page is being replaced by Spyglass soon. Check out the new job view.
PRpohly: component-base: move v/vmodule/log-flush-frequency into LoggingConfiguration
ResultFAILURE
Tests 13 failed / 301 succeeded
Started2021-11-03 18:20
Elapsed1h55m
Revision25907036eac5dcb2d047ac38a352e284ff6d7b0d
Refs 106090
control_plane_node_os_imagecos-85-13310-1308-1
job-versionv1.23.0-alpha.4.50+94b0caa5bc76fd
kubetest-version
revisionv1.23.0-alpha.4.50+94b0caa5bc76fd
worker_node_os_imagecos-85-13310-1308-1

Test Failures


Kubernetes e2e suite [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should perform canary updates and phased rolling updates of template modifications [Conformance] 11m51s

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\scanary\supdates\sand\sphased\srolling\supdates\sof\stemplate\smodifications\s\[Conformance\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
Nov  3 19:42:32.591: Failed waiting for pods to enter running: timed out waiting for the condition
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/statefulset/wait.go:80
				
				Click to see stdout/stderrfrom junit_06.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-network] Services should serve multiport endpoints from pods [Conformance] 5m35s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sServices\sshould\sserve\smultiport\sendpoints\sfrom\spods\s\s\[Conformance\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
Nov  3 19:37:32.745: Unexpected error:
    <*errors.errorString | 0xc000266230>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/pods.go:107
				
				Click to see stdout/stderrfrom junit_07.xml

Filter through 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 [Excluded:WindowsDocker] [NodeConformance] [Conformance] 5m28s

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\[Excluded\:WindowsDocker\]\s\[NodeConformance\]\s\[Conformance\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
Nov  3 19:35:58.595: Expected
    <string>: 
to equal
    <string>: OK
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/runtime.go:165
				
				Click to see stdout/stderrfrom junit_03.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-node] Container Runtime blackbox test on terminated container should report termination message if TerminationMessagePath is set [Excluded:WindowsDocker] [NodeConformance] 5m8s

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\sif\sTerminationMessagePath\sis\sset\s\[Excluded\:WindowsDocker\]\s\[NodeConformance\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/runtime.go:171
Nov  3 19:52:11.279: Timed out after 300.015s.
Expected
    <v1.PodPhase>: Failed
to equal
    <v1.PodPhase>: Succeeded
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/runtime.go:154
				
				Click to see stdout/stderrfrom junit_07.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-node] Pods should be submitted and removed [NodeConformance] [Conformance] 5m36s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-node\]\sPods\sshould\sbe\ssubmitted\sand\sremoved\s\[NodeConformance\]\s\[Conformance\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
Nov  3 19:37:32.745: Unexpected error:
    <*errors.errorString | 0xc0002da220>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/pods.go:300
				
				Click to see stdout/stderrfrom junit_05.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] EmptyDir wrapper volumes should not conflict [Conformance] 5m35s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sEmptyDir\swrapper\svolumes\sshould\snot\sconflict\s\[Conformance\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
Nov  3 19:37:32.718: Unexpected error:
    <*errors.errorString | 0xc000266230>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/pods.go:107
				
				Click to see stdout/stderrfrom junit_08.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] Projected configMap should be consumable from pods in volume as non-root [NodeConformance] [Conformance] 5m36s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sProjected\sconfigMap\sshould\sbe\sconsumable\sfrom\spods\sin\svolume\sas\snon\-root\s\[NodeConformance\]\s\[Conformance\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
Nov  3 19:37:33.040: Unexpected error:
    <*errors.errorString | 0xc003d95240>: {
        s: "expected pod \"pod-projected-configmaps-b5aeed92-019a-4cf7-b962-cd1bb5c68686\" success: Gave up after waiting 5m0s for pod \"pod-projected-configmaps-b5aeed92-019a-4cf7-b962-cd1bb5c68686\" to be \"Succeeded or Failed\"",
    }
    expected pod "pod-projected-configmaps-b5aeed92-019a-4cf7-b962-cd1bb5c68686" success: Gave up after waiting 5m0s for pod "pod-projected-configmaps-b5aeed92-019a-4cf7-b962-cd1bb5c68686" to be "Succeeded or Failed"
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:743
				
				Click to see stdout/stderrfrom junit_01.xml

Find pod-projected-configmaps-b5aeed92-019a-4cf7-b962-cd1bb5c68686 mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] Subpath Atomic writer volumes should support subpaths with configmap pod [Excluded:WindowsDocker] [Conformance] 5m9s

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\s\[Excluded\:WindowsDocker\]\s\[Conformance\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
Nov  3 20:04:55.343: Unexpected error:
    <*errors.errorString | 0xc0036e7290>: {
        s: "expected pod \"pod-subpath-test-configmap-7x4n\" success: Gave up after waiting 5m0s for pod \"pod-subpath-test-configmap-7x4n\" to be \"Succeeded or Failed\"",
    }
    expected pod "pod-subpath-test-configmap-7x4n" success: Gave up after waiting 5m0s for pod "pod-subpath-test-configmap-7x4n" to be "Succeeded or Failed"
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:743
				
				Click to see stdout/stderrfrom junit_07.xml

Find pod-subpath-test-configmap-7x4n 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 [Excluded:WindowsDocker] [Conformance] 5m32s

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\[Excluded\:WindowsDocker\]\s\[Conformance\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
Nov  3 19:51:13.555: Unexpected error:
    <*errors.errorString | 0xc002d445a0>: {
        s: "expected pod \"pod-subpath-test-configmap-gf2k\" success: Gave up after waiting 5m0s for pod \"pod-subpath-test-configmap-gf2k\" to be \"Succeeded or Failed\"",
    }
    expected pod "pod-subpath-test-configmap-gf2k" success: Gave up after waiting 5m0s for pod "pod-subpath-test-configmap-gf2k" to be "Succeeded or Failed"
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:743
				
				Click to see stdout/stderrfrom junit_01.xml

Find pod-subpath-test-configmap-gf2k mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] Subpath Atomic writer volumes should support subpaths with downward pod [Excluded:WindowsDocker] [Conformance] 5m33s

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\sdownward\spod\s\[Excluded\:WindowsDocker\]\s\[Conformance\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
Nov  3 19:59:27.313: Unexpected error:
    <*errors.errorString | 0xc0078d6f50>: {
        s: "expected pod \"pod-subpath-test-downwardapi-f6zr\" success: Gave up after waiting 5m0s for pod \"pod-subpath-test-downwardapi-f6zr\" to be \"Succeeded or Failed\"",
    }
    expected pod "pod-subpath-test-downwardapi-f6zr" success: Gave up after waiting 5m0s for pod "pod-subpath-test-downwardapi-f6zr" to be "Succeeded or Failed"
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:743
				
				Click to see stdout/stderrfrom junit_07.xml

Find pod-subpath-test-downwardapi-f6zr mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] Subpath Atomic writer volumes should support subpaths with projected pod [Excluded:WindowsDocker] [Conformance] 5m7s

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\sprojected\spod\s\[Excluded\:WindowsDocker\]\s\[Conformance\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
Nov  3 20:04:15.009: Unexpected error:
    <*errors.errorString | 0xc005251e90>: {
        s: "expected pod \"pod-subpath-test-projected-nr8s\" success: Gave up after waiting 5m0s for pod \"pod-subpath-test-projected-nr8s\" to be \"Succeeded or Failed\"",
    }
    expected pod "pod-subpath-test-projected-nr8s" success: Gave up after waiting 5m0s for pod "pod-subpath-test-projected-nr8s" to be "Succeeded or Failed"
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:743