This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 9 failed / 634 succeeded
Started2019-11-14 04:15
Elapsed1h15m
Revision
Buildergke-prow-ssd-pool-1a225945-p1cl
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/185245c8-540e-459c-834f-5e91a934f73c/targets/test'}}
pod5bf01467-0695-11ea-b5c7-e216f5392f03
resultstorehttps://source.cloud.google.com/results/invocations/185245c8-540e-459c-834f-5e91a934f73c/targets/test
infra-commit9e15c062b
job-versionv1.16.4-beta.0.1+d70a3ca08fe72a-dirty
pod5bf01467-0695-11ea-b5c7-e216f5392f03
repok8s.io/kubernetes
repo-commitd70a3ca08fe72ad8dd0b2d72cf032474ab2ce2a9
repos{u'k8s.io/kubernetes': u'release-1.16', u'sigs.k8s.io/cloud-provider-azure': u'master'}
revisionv1.16.4-beta.0.1+d70a3ca08fe72a-dirty

Test Failures


Kubernetes e2e suite [k8s.io] Kubelet when scheduling a busybox command that always fails in a pod should have an terminated reason [NodeConformance] [Conformance] 1m22s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[k8s\.io\]\sKubelet\swhen\sscheduling\sa\sbusybox\scommand\sthat\salways\sfails\sin\sa\spod\sshould\shave\san\sterminated\sreason\s\[NodeConformance\]\s\[Conformance\]$'
test/e2e/framework/framework.go:698
Nov 14 04:56:25.085: Timed out after 60.000s.
Expected
    <*errors.errorString | 0xc002169690>: {
        s: "expected state to be terminated. Got pod status: {Phase:Pending Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2019-11-14 04:55:25 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2019-11-14 04:55:25 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [bin-falsec4788a1b-c4f8-453e-9f17-2cf69caa89a8]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2019-11-14 04:55:25 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [bin-falsec4788a1b-c4f8-453e-9f17-2cf69caa89a8]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2019-11-14 04:55:25 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.248.0.5 PodIP: PodIPs:[] StartTime:2019-11-14 04:55:25 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:bin-falsec4788a1b-c4f8-453e-9f17-2cf69caa89a8 State:{Waiting:&ContainerStateWaiting{Reason:ContainerCreating,Message:,} Running:nil Terminated:nil} LastTerminationState:{Waiting:nil Running:nil Terminated:nil} Ready:false RestartCount:0 Image:docker.io/library/busybox:1.29 ImageID: ContainerID: Started:0xc00213934a}] QOSClass:BestEffort EphemeralContainerStatuses:[]}",
    }
to be nil
test/e2e/common/kubelet.go:123
				
				Click to see stdout/stderrfrom junit_29.xml

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


Kubernetes e2e suite [k8s.io] Kubelet when scheduling a busybox command that always fails in a pod should have an terminated reason [NodeConformance] [Conformance] 1m34s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[k8s\.io\]\sKubelet\swhen\sscheduling\sa\sbusybox\scommand\sthat\salways\sfails\sin\sa\spod\sshould\shave\san\sterminated\sreason\s\[NodeConformance\]\s\[Conformance\]$'
test/e2e/framework/framework.go:698
Nov 14 04:54:50.138: Timed out after 60.000s.
Expected
    <*errors.errorString | 0xc0003458e0>: {
        s: "expected state to be terminated. Got pod status: {Phase:Pending Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2019-11-14 04:53:54 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2019-11-14 04:53:54 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [bin-falsee557e594-74c9-40fb-bc3d-b0eb2d920c80]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2019-11-14 04:53:54 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [bin-falsee557e594-74c9-40fb-bc3d-b0eb2d920c80]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2019-11-14 04:53:50 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.248.0.5 PodIP: PodIPs:[] StartTime:2019-11-14 04:53:54 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:bin-falsee557e594-74c9-40fb-bc3d-b0eb2d920c80 State:{Waiting:&ContainerStateWaiting{Reason:ContainerCreating,Message:,} Running:nil Terminated:nil} LastTerminationState:{Waiting:nil Running:nil Terminated:nil} Ready:false RestartCount:0 Image:docker.io/library/busybox:1.29 ImageID: ContainerID: Started:0xc0005b0a0a}] QOSClass:BestEffort EphemeralContainerStatuses:[]}",
    }
to be nil
test/e2e/common/kubelet.go:123
				
				Click to see stdout/stderrfrom junit_29.xml

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


Kubernetes e2e suite [k8s.io] [sig-node] Pods Extended [k8s.io] Delete Grace Period should be submitted and removed [Conformance] 57s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[k8s\.io\]\s\[sig\-node\]\sPods\sExtended\s\[k8s\.io\]\sDelete\sGrace\sPeriod\sshould\sbe\ssubmitted\sand\sremoved\s\[Conformance\]$'
test/e2e/framework/framework.go:698
Nov 14 04:53:06.718: kubelet never observed the termination notice
Unexpected error:
    <*errors.errorString | 0xc0000d5090>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
test/e2e/node/pods.go:163
				
				Click to see stdout/stderrfrom junit_12.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [k8s.io] [sig-node] Pods Extended [k8s.io] Delete Grace Period should be submitted and removed [Conformance] 1m36s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[k8s\.io\]\s\[sig\-node\]\sPods\sExtended\s\[k8s\.io\]\sDelete\sGrace\sPeriod\sshould\sbe\ssubmitted\sand\sremoved\s\[Conformance\]$'
test/e2e/framework/framework.go:698
Nov 14 04:54:04.744: kubelet never observed the termination notice
Unexpected error:
    <*errors.errorString | 0xc0000d5090>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
test/e2e/node/pods.go:163
				
				Click to see stdout/stderrfrom junit_12.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-scheduling] PreemptionExecutionPath runs ReplicaSets to verify preemption running path 2m51s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-scheduling\]\sPreemptionExecutionPath\sruns\sReplicaSets\sto\sverify\spreemption\srunning\spath$'
test/e2e/scheduling/preemption.go:345
Nov 14 04:54:36.481: Unexpected error:
    <*errors.errorString | 0xc002659790>: {
        s: "replicaset \"rs-pod1\" never had desired number of .status.availableReplicas",
    }
    replicaset "rs-pod1" never had desired number of .status.availableReplicas
occurred
test/e2e/scheduling/preemption.go:510
				
				Click to see stdout/stderrfrom junit_02.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-scheduling] PreemptionExecutionPath runs ReplicaSets to verify preemption running path 5m44s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-scheduling\]\sPreemptionExecutionPath\sruns\sReplicaSets\sto\sverify\spreemption\srunning\spath$'
test/e2e/scheduling/preemption.go:345
Nov 14 05:00:12.095: Unexpected error:
    <*errors.errorString | 0xc0018fa460>: {
        s: "replicaset \"rs-pod1\" never had desired number of .status.availableReplicas",
    }
    replicaset "rs-pod1" never had desired number of .status.availableReplicas
occurred
test/e2e/scheduling/preemption.go:510
				
				Click to see stdout/stderrfrom junit_02.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should be able to unmount after the subpath directory is deleted 5m58s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sCSI\sVolumes\s\[Driver\:\scsi\-hostpath\]\s\[Testpattern\:\sDynamic\sPV\s\(default\sfs\)\]\ssubPath\sshould\sbe\sable\sto\sunmount\safter\sthe\ssubpath\sdirectory\sis\sdeleted$'
test/e2e/storage/testsuites/subpath.go:425
Nov 14 04:58:40.003: Unexpected error:
    <*errors.errorString | 0xc002ce7420>: {
        s: "PersistentVolumeClaims [csi-hostpathn7ls6] not all in phase Bound within 5m0s",
    }
    PersistentVolumeClaims [csi-hostpathn7ls6] not all in phase Bound within 5m0s
occurred
test/e2e/storage/testsuites/base.go:366
				
				Click to see stdout/stderrfrom junit_10.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support readOnly directory specified in the volumeMount 7m16s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sCSI\sVolumes\s\[Driver\:\scsi\-hostpath\]\s\[Testpattern\:\sDynamic\sPV\s\(default\sfs\)\]\ssubPath\sshould\ssupport\sreadOnly\sdirectory\sspecified\sin\sthe\svolumeMount$'
test/e2e/storage/testsuites/subpath.go:347
Nov 14 05:19:19.433: Unexpected error:
    <*errors.errorString | 0xc0021711e0>: {
        s: "PersistentVolumeClaims [csi-hostpathndprd] not all in phase Bound within 5m0s",
    }
    PersistentVolumeClaims [csi-hostpathndprd] not all in phase Bound within 5m0s
occurred
test/e2e/storage/testsuites/base.go:366
				
				Click to see stdout/stderrfrom junit_11.xml

Filter through log files | View test history on testgrid


Test 41m38s

error during ./hack/ginkgo-e2e.sh --ginkgo.flakeAttempts=2 --num-nodes=2 --ginkgo.skip=\[Slow\]|\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\]|Network\sshould\sset\sTCP\sCLOSE_WAIT\stimeout|Mount\spropagation\sshould\spropagate\smounts\sto\sthe\shost|PodSecurityPolicy|PVC\sProtection\sVerify|should\sprovide\sbasic\sidentity|should\sadopt\smatching\sorphans\sand\srelease|should\snot\sdeadlock\swhen\sa\spod's\spredecessor\sfails|should\sperform\srolling\supdates\sand\sroll\sbacks\sof\stemplate\smodifications\swith\sPVCs|should\sperform\srolling\supdates\sand\sroll\sbacks\sof\stemplate\smodifications|Services\sshould\sbe\sable\sto\screate\sa\sfunctioning\sNodePort\sservice$|volumeMode\sshould\snot\smount\s/\smap\sunused\svolumes\sin\sa\spod --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 634 Passed Tests

Show 4107 Skipped Tests