This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 5 failed / 190 succeeded
Started2020-02-12 08:45
Elapsed4h37m
Revision
Buildergke-prow-default-pool-cf4891d4-r4zq
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/78d91b91-d3de-4e6e-94f8-3c2cd9e49962/targets/test'}}
pode9fc0baa-4d73-11ea-8c6e-1aa579f21cc7
resultstorehttps://source.cloud.google.com/results/invocations/78d91b91-d3de-4e6e-94f8-3c2cd9e49962/targets/test
infra-commitf18efb258
job-versionv1.17.4-beta.0.1+aa9a28326e8075
master_os_imagecos-77-12371-89-0
node_os_imagecos-77-12371-89-0
pode9fc0baa-4d73-11ea-8c6e-1aa579f21cc7
revisionv1.17.4-beta.0.1+aa9a28326e8075

Test Failures


Kubernetes e2e suite [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand Verify if offline PVC expansion works 6m2s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sCSI\sVolumes\s\[Driver\:\spd\.csi\.storage\.gke\.io\]\[Serial\]\s\[Testpattern\:\sDynamic\sPV\s\(block\svolmode\)\(allowExpansion\)\]\svolume\-expand\sVerify\sif\soffline\sPVC\sexpansion\sworks$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:159
Feb 12 11:23:52.981: while recreating pod for resizing
Unexpected error:
    <*errors.errorString | 0xc002b4bca0>: {
        s: "pod \"security-context-f35a980a-f6f8-456a-9f3e-a562a4a76ac4\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-f35a980a-f6f8-456a-9f3e-a562a4a76ac4" is not Running: timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:213
				
				Click to see stdout/stderrfrom junit_01.xml

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


Kubernetes e2e suite [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand Verify if offline PVC expansion works 5m58s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sCSI\sVolumes\s\[Driver\:\spd\.csi\.storage\.gke\.io\]\[Serial\]\s\[Testpattern\:\sDynamic\sPV\s\(default\sfs\)\(allowExpansion\)\]\svolume\-expand\sVerify\sif\soffline\sPVC\sexpansion\sworks$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:159
Feb 12 10:23:36.684: while recreating pod for resizing
Unexpected error:
    <*errors.errorString | 0xc0035ee220>: {
        s: "pod \"security-context-20b15e28-f403-4a87-b766-f7ded0d06d3e\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-20b15e28-f403-4a87-b766-f7ded0d06d3e" is not Running: timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:213
				
				Click to see stdout/stderrfrom junit_01.xml

Find for 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 unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly] 4.50s

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\sunmount\sif\spod\sis\sgracefully\sdeleted\swhile\skubelet\sis\sdown\s\[Disruptive\]\[Slow\]\[LinuxOnly\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:340
Feb 12 12:57:57.679: while waiting for hostPath init pod to succeed
Unexpected error:
    <*errors.errorString | 0xc003091c10>: {
        s: "pod \"hostpath-symlink-prep-provisioning-3038\" failed with status: {Phase:Failed Conditions:[] Message:Pod Node didn't have enough resource: pods, requested: 1, used: 110, capacity: 110 Reason:OutOfpods NominatedNodeName: HostIP: PodIP: PodIPs:[] StartTime:2020-02-12 12:57:55 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[] QOSClass: EphemeralContainerStatuses:[]}",
    }
    pod "hostpath-symlink-prep-provisioning-3038" failed with status: {Phase:Failed Conditions:[] Message:Pod Node didn't have enough resource: pods, requested: 1, used: 110, capacity: 110 Reason:OutOfpods NominatedNodeName: HostIP: PodIP: PodIPs:[] StartTime:2020-02-12 12:57:55 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[] QOSClass: EphemeralContainerStatuses:[]}
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/drivers/in_tree.go:883
				
				Click to see stdout/stderrfrom junit_01.xml

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


Kubernetes e2e suite [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: gce-localssd-scsi-fs] [Serial] [Testpattern: Pre-provisioned PV (block volmode)] disruptive[Disruptive] Should test that pv used in a pod that is deleted while the kubelet is down cleans up when the kubelet returns. 1.90s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sIn\-tree\sVolumes\s\[Driver\:\slocal\]\[LocalVolumeType\:\sgce\-localssd\-scsi\-fs\]\s\[Serial\]\s\[Testpattern\:\sPre\-provisioned\sPV\s\(block\svolmode\)\]\sdisruptive\[Disruptive\]\sShould\stest\sthat\spv\sused\sin\sa\spod\sthat\sis\sdeleted\swhile\sthe\skubelet\sis\sdown\scleans\sup\swhen\sthe\skubelet\sreturns\.$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/disruptive.go:149
Feb 12 12:57:59.984: Unexpected error:
    <*errors.errorString | 0xc000508800>: {
        s: "pod ran to completion",
    }
    pod ran to completion
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/host_exec.go:103
				
				Click to see stdout/stderrfrom junit_01.xml

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


Test 4h18m

error during ./hack/ginkgo-e2e.sh --ginkgo.focus=\[Serial\]|\[Disruptive\] --ginkgo.skip=\[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 190 Passed Tests

Show 4666 Skipped Tests