This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 7 failed / 323 succeeded
Started2023-01-29 13:07
Elapsed1h6m
Revisionmaster
control_plane_node_os_imagecos-85-13310-1308-1
job-versionv1.24.11-rc.0.6+7c685ed7305e76
kubetest-versionv20230127-9396ca613c
revisionv1.24.11-rc.0.6+7c685ed7305e76
worker_node_os_imagecos-85-13310-1308-1

Test Failures


Kubernetes e2e suite [sig-apps] ReplicaSet should serve a basic image on each replica with a public image [Conformance] 5m34s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-apps\]\sReplicaSet\sshould\sserve\sa\sbasic\simage\son\seach\sreplica\swith\sa\spublic\simage\s\s\[Conformance\]$'
test/e2e/framework/framework.go:652
Jan 29 13:40:02.896: Unexpected error:
    <*errors.errorString | 0xc00403c820>: {
        s: "pod \"my-hostname-basic-c51b3d4a-15b4-42f9-a367-8107d96771db-vq7kc\" never run (phase: Pending, conditions: [{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-29 13:35:02 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-29 13:35:02 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [my-hostname-basic-c51b3d4a-15b4-42f9-a367-8107d96771db]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-29 13:35:02 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [my-hostname-basic-c51b3d4a-15b4-42f9-a367-8107d96771db]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-29 13:35:02 +0000 UTC Reason: Message:}]): timed out waiting for the condition",
    }
    pod "my-hostname-basic-c51b3d4a-15b4-42f9-a367-8107d96771db-vq7kc" never run (phase: Pending, conditions: [{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-29 13:35:02 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-29 13:35:02 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [my-hostname-basic-c51b3d4a-15b4-42f9-a367-8107d96771db]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-29 13:35:02 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [my-hostname-basic-c51b3d4a-15b4-42f9-a367-8107d96771db]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-29 13:35:02 +0000 UTC Reason: Message:}]): timed out waiting for the condition
occurred
test/e2e/apps/replica_set.go:218
				
				Click to see stdout/stderrfrom junit_04.xml

Find my-hostname-basic-c51b3d4a-15b4-42f9-a367-8107d96771db-vq7kc 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 if TerminationMessagePath is set as non-root user and at a non-default path [NodeConformance] [Conformance] 7m50s

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\sas\snon\-root\suser\sand\sat\sa\snon\-default\spath\s\[NodeConformance\]\s\[Conformance\]$'
test/e2e/framework/framework.go:652
Jan 29 13:51:13.009: Timed out after 300.001s.
Expected
    <v1.PodPhase>: Failed
to equal
    <v1.PodPhase>: Succeeded
test/e2e/common/node/runtime.go:156
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-node] Probing container should *not* be restarted with a tcp:8080 liveness probe [NodeConformance] [Conformance] 6m3s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-node\]\sProbing\scontainer\sshould\s\*not\*\sbe\srestarted\swith\sa\stcp\:8080\sliveness\sprobe\s\[NodeConformance\]\s\[Conformance\]$'
test/e2e/framework/framework.go:652
Jan 29 13:39:34.034: starting pod liveness-2e8f9547-dee1-43c2-8356-36661eb5f853 in namespace container-probe-9252
Unexpected error:
    <*errors.errorString | 0xc00022a1e0>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
test/e2e/common/node/container_probe.go:901
				
				Click to see stdout/stderrfrom junit_03.xml

Find liveness-2e8f9547-dee1-43c2-8356-36661eb5f853 mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-windows] Services should be able to create a functioning NodePort service for Windows 3m32s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-windows\]\sServices\sshould\sbe\sable\sto\screate\sa\sfunctioning\sNodePort\sservice\sfor\sWindows$'
test/e2e/windows/service.go:44
Jan 29 13:53:05.009: Unexpected error:
    <*errors.errorString | 0xc003847ef0>: {
        s: "failed waiting for pods to be running: timeout waiting for 1 pods to be ready",
    }
    failed waiting for pods to be running: timeout waiting for 1 pods to be ready
occurred
test/e2e/windows/service.go:68
				
				Click to see stdout/stderrfrom junit_02.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-windows] [Feature:WindowsHostProcessContainers] [MinimumKubeletVersion:1.22] HostProcess containers should run as a process on the host/node 13s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-windows\]\s\[Feature\:WindowsHostProcessContainers\]\s\[MinimumKubeletVersion\:1\.22\]\sHostProcess\scontainers\sshould\srun\sas\sa\sprocess\son\sthe\shost\/node$'
test/e2e/windows/host_process.go:88
Jan 29 13:43:44.326: Expected
    <v1.PodPhase>: Failed
to equal
    <v1.PodPhase>: Succeeded
test/e2e/windows/host_process.go:134
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-windows] [Feature:WindowsHostProcessContainers] [MinimumKubeletVersion:1.22] HostProcess containers should support various volume mount types 13s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-windows\]\s\[Feature\:WindowsHostProcessContainers\]\s\[MinimumKubeletVersion\:1\.22\]\sHostProcess\scontainers\sshould\ssupport\svarious\svolume\smount\stypes$'
test/e2e/windows/host_process.go:422
Jan 29 13:48:22.625: Expected
    <v1.PodPhase>: Failed
to equal
    <v1.PodPhase>: Succeeded
test/e2e/windows/host_process.go:480
				
				Click to see stdout/stderrfrom junit_03.xml

Filter through log files | View test history on testgrid


kubetest 41m4s

error during /home/prow/go/src/sigs.k8s.io/windows-testing/gce/run-e2e.sh --node-os-distro=windows -prepull-images=true --ginkgo.focus=\[Conformance\]|\[NodeConformance\]|\[sig-windows\]|\[Feature:Windows\] --ginkgo.skip=\[LinuxOnly\]|\[Serial\]|\[alpha\]|\[Slow\]|\[GMSA\]|Guestbook.application.should.create.and.stop.a.working.application|device.plugin.for.Windows|\[sig-api-machinery\].Aggregator|\[Driver:.windows-gcepd\]: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 323 Passed Tests

Show 6661 Skipped Tests