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 7 failed / 753 succeeded
Started2020-01-14 01:40
Elapsed56m7s
Revision
Buildergke-prow-default-pool-cf4891d4-p8rj
Refs master:b008eda8
86670:70e0f7c1
podcdafa125-366e-11ea-b9b8-f6c6e0243ab8
infra-commite65b3228e
job-versionv1.18.0-alpha.1.658+6735738a5484c8
master_os_imagecos-77-12371-89-0
node_os_imagecos-77-12371-89-0
podcdafa125-366e-11ea-b9b8-f6c6e0243ab8
repok8s.io/kubernetes
repo-commit6735738a5484c89dffb43b0397d42a8bd1340880
repos{u'k8s.io/kubernetes': u'master:b008eda8b2dc0fdd884cb56065f7f1667a970a16,86670:70e0f7c1a9063000ec543087fe91405e2a1b151c', u'k8s.io/release': u'master'}
revisionv1.18.0-alpha.1.658+6735738a5484c8

Test Failures


Kubernetes e2e suite [sig-apps] DisruptionController should block an eviction until the PDB is updated to allow it 49s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-apps\]\sDisruptionController\sshould\sblock\san\seviction\suntil\sthe\sPDB\sis\supdated\sto\sallow\sit$'
test/e2e/apps/disruption.go:202
Jan 14 02:16:58.324: Unexpected error:
    <*errors.StatusError | 0xc0013f61e0>: {
        ErrStatus: {
            TypeMeta: {Kind: "", APIVersion: ""},
            ListMeta: {
                SelfLink: "",
                ResourceVersion: "",
                Continue: "",
                RemainingItemCount: nil,
            },
            Status: "Failure",
            Message: "Cannot evict pod as it would violate the pod's disruption budget.",
            Reason: "TooManyRequests",
            Details: {
                Name: "",
                Group: "",
                Kind: "",
                UID: "",
                Causes: [
                    {
                        Type: "DisruptionBudget",
                        Message: "The disruption budget foo needs 2 healthy pods and has 2 currently",
                        Field: "",
                    },
                ],
                RetryAfterSeconds: 0,
            },
            Code: 429,
        },
    }
    Cannot evict pod as it would violate the pod's disruption budget.
occurred
test/e2e/apps/disruption.go:227
				
				Click to see stdout/stderrfrom junit_30.xml

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


Kubernetes e2e suite [sig-storage] In-tree Volumes [Driver: hostPathSymlink] [Testpattern: Inline-volume (default fs)] subPath should support readOnly file specified in the volumeMount [LinuxOnly] 1m2s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sIn\-tree\sVolumes\s\[Driver\:\shostPathSymlink\]\s\[Testpattern\:\sInline\-volume\s\(default\sfs\)\]\ssubPath\sshould\ssupport\sreadOnly\sfile\sspecified\sin\sthe\svolumeMount\s\[LinuxOnly\]$'
test/e2e/storage/testsuites/subpath.go:377
Jan 14 02:14:58.468: while waiting for hostPath init pod to succeed
Unexpected error:
    <*errors.errorString | 0xc0026730f0>: {
        s: "pod \"hostpath-symlink-prep-provisioning-4266\" failed with status: {Phase:Failed Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2020-01-14 02:14:20 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2020-01-14 02:14:20 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [init-volume-provisioning-4266]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2020-01-14 02:14:20 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [init-volume-provisioning-4266]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2020-01-14 02:14:20 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.40.0.4 PodIP:10.64.1.63 PodIPs:[{IP:10.64.1.63}] StartTime:2020-01-14 02:14:20 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:init-volume-provisioning-4266 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 02:14:30 +0000 UTC,FinishedAt:2020-01-14 02:14:30 +0000 UTC,ContainerID:docker://3193b014a0107edf8bec0b5dafb822958d72f767ff98780bb3804188256e9152,}} LastTerminationState:{Waiting:nil Running:nil Terminated:nil} Ready:false RestartCount:0 Image:busybox:1.29 ImageID:docker-pullable://busybox@sha256:e004c2cc521c95383aebb1fb5893719aa7a8eae2e7a71f316a4410784edb00a9 ContainerID:docker://3193b014a0107edf8bec0b5dafb822958d72f767ff98780bb3804188256e9152 Started:0xc00287b389}] QOSClass:BestEffort EphemeralContainerStatuses:[]}",
    }
    pod "hostpath-symlink-prep-provisioning-4266" failed with status: {Phase:Failed Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2020-01-14 02:14:20 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2020-01-14 02:14:20 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [init-volume-provisioning-4266]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2020-01-14 02:14:20 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [init-volume-provisioning-4266]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2020-01-14 02:14:20 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.40.0.4 PodIP:10.64.1.63 PodIPs:[{IP:10.64.1.63}] StartTime:2020-01-14 02:14:20 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:init-volume-provisioning-4266 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 02:14:30 +0000 UTC,FinishedAt:2020-01-14 02:14:30 +0000 UTC,ContainerID:docker://3193b014a0107edf8bec0b5dafb822958d72f767ff98780bb3804188256e9152,}} LastTerminationState:{Waiting:nil Running:nil Terminated:nil} Ready:false RestartCount:0 Image:busybox:1.29 ImageID:docker-pullable://busybox@sha256:e004c2cc521c95383aebb1fb5893719aa7a8eae2e7a71f316a4410784edb00a9 ContainerID:docker://3193b014a0107edf8bec0b5dafb822958d72f767ff98780bb3804188256e9152 Started:0xc00287b389}] QOSClass:BestEffort EphemeralContainerStatuses:[]}
occurred
test/e2e/storage/drivers/in_tree.go:944
				
				Click to see stdout/stderrfrom junit_07.xml

Find to 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 3m6s

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 02:19:10.047: Unexpected error:
    <*errors.errorString | 0xc00106dc10>: {
        s: "pod \"security-context-648416c7-ebc9-4fb3-95ce-3116a0427e38\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-648416c7-ebc9-4fb3-95ce-3116a0427e38" is not Running: timed out waiting for the condition
occurred
test/e2e/storage/persistent_volumes-local.go:747
				
				Click to see stdout/stderrfrom junit_06.xml

Find security-context-648416c7-ebc9-4fb3-95ce-3116a0427e38 mentions in log files | View test history on testgrid


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

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sPersistentVolumes\-local\s\s\[Volume\stype\:\sblockfswithoutformat\]\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 02:07:51.355: Unexpected error:
    <*errors.errorString | 0xc0022d6830>: {
        s: "pod \"security-context-52dc8d79-7bb3-4f50-9759-3dcfa976dda8\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-52dc8d79-7bb3-4f50-9759-3dcfa976dda8" is not Running: timed out waiting for the condition
occurred
test/e2e/storage/persistent_volumes-local.go:747
				
				Click to see stdout/stderrfrom junit_18.xml

Find security-context-52dc8d79-7bb3-4f50-9759-3dcfa976dda8 mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] PersistentVolumes-local [Volume type: dir-link-bindmounted] Two pods mounting a local volume at the same time should be able to write from pod1 and read from pod2 2m45s

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\-bindmounted\]\sTwo\spods\smounting\sa\slocal\svolume\sat\sthe\ssame\stime\sshould\sbe\sable\sto\swrite\sfrom\spod1\sand\sread\sfrom\spod2$'
test/e2e/storage/persistent_volumes-local.go:244
Jan 14 02:04:29.701: Unexpected error:
    <*errors.errorString | 0xc002d1d6a0>: {
        s: "pod \"security-context-1f164151-a40c-4cf2-8b0d-789c16a88e81\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-1f164151-a40c-4cf2-8b0d-789c16a88e81" is not Running: timed out waiting for the condition
occurred
test/e2e/storage/persistent_volumes-local.go:710
				
				Click to see stdout/stderrfrom junit_06.xml

Find security-context-1f164151-a40c-4cf2-8b0d-789c16a88e81 mentions in log files | View test history on testgrid


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

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sPersistentVolumes\-local\s\s\[Volume\stype\:\stmpfs\]\sOne\spod\srequesting\sone\sprebound\sPVC\sshould\sbe\sable\sto\smount\svolume\sand\sread\sfrom\spod1$'
test/e2e/storage/persistent_volumes-local.go:210
Jan 14 02:07:21.499: Unexpected error:
    <*errors.errorString | 0xc000352b20>: {
        s: "pod \"security-context-0d8342fc-2258-43e0-9aee-fb13a15a0ebb\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-0d8342fc-2258-43e0-9aee-fb13a15a0ebb" is not Running: timed out waiting for the condition
occurred
test/e2e/storage/persistent_volumes-local.go:213
				
				Click to see stdout/stderrfrom junit_10.xml

Find security-context-0d8342fc-2258-43e0-9aee-fb13a15a0ebb mentions in log files | View test history on testgrid


Test 30m8s

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 753 Passed Tests

Show 4099 Skipped Tests