This job view page is being replaced by Spyglass soon. Check out the new job view.
PRtedyu: Don't try to create VolumeSpec immediately after underlying PVC is being deleted
ResultFAILURE
Tests 4 failed / 756 succeeded
Started2020-01-14 23:14
Elapsed52m7s
Revision
Buildergke-prow-default-pool-cf4891d4-vb82
Refs master:edbd51bc
86670:53471836
pod927ffa9d-3723-11ea-a41b-32f42f64fdae
infra-commit797379095
job-versionv1.18.0-alpha.1.684+7740e206d42f00
master_os_imagecos-77-12371-89-0
node_os_imagecos-77-12371-89-0
pod927ffa9d-3723-11ea-a41b-32f42f64fdae
repok8s.io/kubernetes
repo-commit7740e206d42f003c23f7a8c634710621fffc3e57
repos{u'k8s.io/kubernetes': u'master:edbd51bc692608e445765e42bb8713497ff98edf,86670:534718362c5d8fe2a963081629d5bfeb66183717', u'k8s.io/release': u'master'}
revisionv1.18.0-alpha.1.684+7740e206d42f00

Test Failures


Kubernetes e2e suite [k8s.io] [sig-node] Security Context should support container.SecurityContext.RunAsUser [LinuxOnly] 43s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[k8s\.io\]\s\[sig\-node\]\sSecurity\sContext\sshould\ssupport\scontainer\.SecurityContext\.RunAsUser\s\[LinuxOnly\]$'
test/e2e/node/security_context.go:102
Jan 14 23:49:03.057: Unexpected error:
    <*errors.errorString | 0xc002c71020>: {
        s: "expected pod \"security-context-f4db543b-4df3-4225-9055-9732a8acee8a\" success: pod \"security-context-f4db543b-4df3-4225-9055-9732a8acee8a\" failed with status: {Phase:Failed Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2020-01-14 23:48:36 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2020-01-14 23:48:36 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [test-container]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2020-01-14 23:48:36 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [test-container]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2020-01-14 23:48:35 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.40.0.4 PodIP:10.64.2.139 PodIPs:[{IP:10.64.2.139}] StartTime:2020-01-14 23:48:36 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:test-container State:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:128,Signal:0,Reason:ContainerCannotRun,Message:OCI runtime start failed: container process is already dead: unknown,StartedAt:2020-01-14 23:48:47 +0000 UTC,FinishedAt:2020-01-14 23:48:47 +0000 UTC,ContainerID:docker://5a2e05a3e45ef3ad7f53bcaadb912c5feb13736bcba9a01f5c4fe5d43c126a44,}} LastTerminationState:{Waiting:nil Running:nil Terminated:nil} Ready:false RestartCount:0 Image:busybox:1.29 ImageID:docker-pullable://busybox@sha256:e004c2cc521c95383aebb1fb5893719aa7a8eae2e7a71f316a4410784edb00a9 ContainerID:docker://5a2e05a3e45ef3ad7f53bcaadb912c5feb13736bcba9a01f5c4fe5d43c126a44 Started:0xc002882759}] QOSClass:BestEffort EphemeralContainerStatuses:[]}",
    }
    expected pod "security-context-f4db543b-4df3-4225-9055-9732a8acee8a" success: pod "security-context-f4db543b-4df3-4225-9055-9732a8acee8a" failed with status: {Phase:Failed Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2020-01-14 23:48:36 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2020-01-14 23:48:36 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [test-container]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2020-01-14 23:48:36 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [test-container]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2020-01-14 23:48:35 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.40.0.4 PodIP:10.64.2.139 PodIPs:[{IP:10.64.2.139}] StartTime:2020-01-14 23:48:36 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:test-container State:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:128,Signal:0,Reason:ContainerCannotRun,Message:OCI runtime start failed: container process is already dead: unknown,StartedAt:2020-01-14 23:48:47 +0000 UTC,FinishedAt:2020-01-14 23:48:47 +0000 UTC,ContainerID:docker://5a2e05a3e45ef3ad7f53bcaadb912c5feb13736bcba9a01f5c4fe5d43c126a44,}} LastTerminationState:{Waiting:nil Running:nil Terminated:nil} Ready:false RestartCount:0 Image:busybox:1.29 ImageID:docker-pullable://busybox@sha256:e004c2cc521c95383aebb1fb5893719aa7a8eae2e7a71f316a4410784edb00a9 ContainerID:docker://5a2e05a3e45ef3ad7f53bcaadb912c5feb13736bcba9a01f5c4fe5d43c126a44 Started:0xc002882759}] QOSClass:BestEffort EphemeralContainerStatuses:[]}
occurred
test/e2e/framework/util.go:829
				
				Click to see stdout/stderrfrom junit_22.xml

Find security-context-f4db543b-4df3-4225-9055-9732a8acee8a mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] PersistentVolumes-local [Volume type: blockfswithformat] Two pods mounting a local volume one after the other should be able to write from pod1 and read from pod2 2m58s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sPersistentVolumes\-local\s\s\[Volume\stype\:\sblockfswithformat\]\sTwo\spods\smounting\sa\slocal\svolume\sone\safter\sthe\sother\sshould\sbe\sable\sto\swrite\sfrom\spod1\sand\sread\sfrom\spod2$'
test/e2e/storage/persistent_volumes-local.go:250
Jan 14 23:54:02.295: Unexpected error:
    <*errors.errorString | 0xc000210a90>: {
        s: "pod \"security-context-d2249f24-4e9a-489d-a28a-a6fa3d1a18c5\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-d2249f24-4e9a-489d-a28a-a6fa3d1a18c5" is not Running: timed out waiting for the condition
occurred
test/e2e/storage/persistent_volumes-local.go:747
				
				Click to see stdout/stderrfrom junit_20.xml

Find security-context-d2249f24-4e9a-489d-a28a-a6fa3d1a18c5 mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] PersistentVolumes-local [Volume type: dir-link] One pod requesting one prebound PVC should be able to mount volume and write from pod1 2m42s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sPersistentVolumes\-local\s\s\[Volume\stype\:\sdir\-link\]\sOne\spod\srequesting\sone\sprebound\sPVC\sshould\sbe\sable\sto\smount\svolume\sand\swrite\sfrom\spod1$'
test/e2e/storage/persistent_volumes-local.go:210
Jan 14 23:41:02.019: Unexpected error:
    <*errors.errorString | 0xc002c6ce50>: {
        s: "pod \"security-context-f563ac6a-291f-401c-b301-d67f3b3d3e45\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-f563ac6a-291f-401c-b301-d67f3b3d3e45" is not Running: timed out waiting for the condition
occurred
test/e2e/storage/persistent_volumes-local.go:213
				
				Click to see stdout/stderrfrom junit_02.xml

Find security-context-f563ac6a-291f-401c-b301-d67f3b3d3e45 mentions in log files | View test history on testgrid


Test 26m43s

error during ./hack/ginkgo-e2e.sh --ginkgo.skip=\[Slow\]|\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\] --minStartupPods=8 --report-dir=/workspace/_artifacts --disable-log-dump=true: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 756 Passed Tests

Show 4099 Skipped Tests