This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 83 failed / 610 succeeded
Started2019-11-10 04:05
Elapsed2h37m
Revision
Buildergke-prow-ssd-pool-1a225945-g9xl
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/fbf8019e-ccff-4a31-bccf-74ae5afe34e8/targets/test'}}
pod31cdeb6c-036f-11ea-b541-aebeeb3e99ae
resultstorehttps://source.cloud.google.com/results/invocations/fbf8019e-ccff-4a31-bccf-74ae5afe34e8/targets/test
infra-commit830666073
job-versionv1.16.3-beta.0.54+c3f2a6524ed89b-dirty
pod31cdeb6c-036f-11ea-b541-aebeeb3e99ae
repok8s.io/kubernetes
repo-commitc3f2a6524ed89bd9b3ded6f491f0d823b11523ae
repos{u'k8s.io/kubernetes': u'release-1.16', u'sigs.k8s.io/cloud-provider-azure': u'master'}
revisionv1.16.3-beta.0.54+c3f2a6524ed89b-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] 1m33s

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 10 04:54:29.395: Timed out after 60.000s.
Expected
    <*errors.errorString | 0xc00239c340>: {
        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-10 04:53:37 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2019-11-10 04:53:37 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [bin-falsec4fbe029-0124-4a71-a853-19a98ac70c39]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2019-11-10 04:53:37 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [bin-falsec4fbe029-0124-4a71-a853-19a98ac70c39]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2019-11-10 04:53:29 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.248.0.4 PodIP: PodIPs:[] StartTime:2019-11-10 04:53:37 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:bin-falsec4fbe029-0124-4a71-a853-19a98ac70c39 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:0xc000a40cca}] QOSClass:BestEffort EphemeralContainerStatuses:[]}",
    }
to be nil
test/e2e/common/kubelet.go:123
				
				Click to see stdout/stderrfrom junit_13.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] 2m0s

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 10 04:46:46.784: kubelet never observed the termination notice
Unexpected error:
    <*errors.errorString | 0xc0000a10a0>: {
        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_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-apps] CronJob should delete successful/failed finished jobs with limit of one job 6m26s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-apps\]\sCronJob\sshould\sdelete\ssuccessful\/failed\sfinished\sjobs\swith\slimit\sof\sone\sjob$'
test/e2e/apps/cronjob.go:233
Nov 10 04:52:45.564: Expected
    <int>: 2
to equal
    <int>: 1
test/e2e/framework/util.go:1339
				
				Click to see stdout/stderrfrom junit_30.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-apps] DisruptionController evictions: maxUnavailable allow single eviction, percentage => should allow an eviction 17m25s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-apps\]\sDisruptionController\sevictions\:\smaxUnavailable\sallow\ssingle\seviction\,\spercentage\s\=\>\sshould\sallow\san\seviction$'
test/e2e/framework/framework.go:152
Nov 10 05:40:11.644: Couldn't delete ns: "disruption-9040": namespace disruption-9040 was not deleted with limit: timed out waiting for the condition, pods remaining: 5 (&errors.errorString{s:"namespace disruption-9040 was not deleted with limit: timed out waiting for the condition, pods remaining: 5"})
test/e2e/framework/framework.go:336
				
				Click to see stdout/stderrfrom junit_22.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-apps] DisruptionController evictions: too few pods, absolute => should not allow an eviction 12m11s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-apps\]\sDisruptionController\sevictions\:\stoo\sfew\spods\,\sabsolute\s\=\>\sshould\snot\sallow\san\seviction$'
test/e2e/framework/framework.go:152
Nov 10 05:05:50.505: Couldn't delete ns: "disruption-3459": namespace disruption-3459 was not deleted with limit: timed out waiting for the condition, pods remaining: 1 (&errors.errorString{s:"namespace disruption-3459 was not deleted with limit: timed out waiting for the condition, pods remaining: 1"})
test/e2e/framework/framework.go:336
				
				Click to see stdout/stderrfrom junit_07.xml

Filter through log files | View test history on testgrid


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

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/framework/framework.go:152
Nov 10 05:07:43.447: Couldn't delete ns: "disruption-2213": namespace disruption-2213 was not deleted with limit: timed out waiting for the condition, pods remaining: 1 (&errors.errorString{s:"namespace disruption-2213 was not deleted with limit: timed out waiting for the condition, pods remaining: 1"})
test/e2e/framework/framework.go:336
				
				Click to see stdout/stderrfrom junit_08.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-apps] StatefulSet [k8s.io] Basic StatefulSet functionality [StatefulSetBasic] Should recreate evicted statefulset [Conformance] 6m25s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-apps\]\sStatefulSet\s\[k8s\.io\]\sBasic\sStatefulSet\sfunctionality\s\[StatefulSetBasic\]\sShould\srecreate\sevicted\sstatefulset\s\[Conformance\]$'
test/e2e/framework/framework.go:698
Nov 10 04:42:58.557: Pod ss-0 expected to be re-created at least once
test/e2e/apps/statefulset.go:740
				
				Click to see stdout/stderrfrom junit_29.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-apps] StatefulSet [k8s.io] Basic StatefulSet functionality [StatefulSetBasic] should implement legacy replacement when the update strategy is OnDelete 32m8s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-apps\]\sStatefulSet\s\[k8s\.io\]\sBasic\sStatefulSet\sfunctionality\s\[StatefulSetBasic\]\sshould\simplement\slegacy\sreplacement\swhen\sthe\supdate\sstrategy\sis\sOnDelete$'
test/e2e/apps/statefulset.go:88
Nov 10 05:32:22.672: Unexpected error:
    <*errors.errorString | 0xc000c2e060>: {
        s: "Failed to scale statefulset to 0 in 10m0s. Remaining pods:\n[ss2-1: deletion 2019-11-10 05:15:49 +0000 UTC, phase Running, readiness false]",
    }
    Failed to scale statefulset to 0 in 10m0s. Remaining pods:
    [ss2-1: deletion 2019-11-10 05:15:49 +0000 UTC, phase Running, readiness false]
occurred
test/e2e/framework/statefulset/rest.go:148
				
				Click to see stdout/stderrfrom junit_26.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-apps] StatefulSet [k8s.io] Basic StatefulSet functionality [StatefulSetBasic] should perform canary updates and phased rolling updates of template modifications [Conformance] 27m30s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-apps\]\sStatefulSet\s\[k8s\.io\]\sBasic\sStatefulSet\sfunctionality\s\[StatefulSetBasic\]\sshould\sperform\scanary\supdates\sand\sphased\srolling\supdates\sof\stemplate\smodifications\s\[Conformance\]$'
test/e2e/framework/framework.go:698
Nov 10 05:09:00.067: Failed waiting for state update: timed out waiting for the condition
test/e2e/framework/statefulset/wait.go:129
				
				Click to see stdout/stderrfrom junit_05.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-apps] StatefulSet [k8s.io] Basic StatefulSet functionality [StatefulSetBasic] should perform canary updates and phased rolling updates of template modifications [Conformance] 28m26s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-apps\]\sStatefulSet\s\[k8s\.io\]\sBasic\sStatefulSet\sfunctionality\s\[StatefulSetBasic\]\sshould\sperform\scanary\supdates\sand\sphased\srolling\supdates\sof\stemplate\smodifications\s\[Conformance\]$'
test/e2e/framework/framework.go:698
Nov 10 05:37:58.491: Failed waiting for state update: timed out waiting for the condition
test/e2e/framework/statefulset/wait.go:129
				
				Click to see stdout/stderrfrom junit_05.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-cli] Kubectl client Guestbook application should create and stop a working application [Conformance] 14m52s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-cli\]\sKubectl\sclient\sGuestbook\sapplication\sshould\screate\sand\sstop\sa\sworking\sapplication\s\s\[Conformance\]$'
test/e2e/framework/framework.go:152
Nov 10 05:14:50.534: Couldn't delete ns: "kubectl-7745": namespace kubectl-7745 was not deleted with limit: timed out waiting for the condition, pods remaining: 2 (&errors.errorString{s:"namespace kubectl-7745 was not deleted with limit: timed out waiting for the condition, pods remaining: 2"})
test/e2e/framework/framework.go:336
				
				Click to see stdout/stderrfrom junit_19.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-network] Services should serve a basic endpoint from pods [Conformance] 4m21s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sServices\sshould\sserve\sa\sbasic\sendpoint\sfrom\spods\s\s\[Conformance\]$'
test/e2e/framework/framework.go:698
Nov 10 05:11:31.277: failed to validate endpoints for service endpoint-test2 in namespace: services-205
Unexpected error:
    <*errors.errorString | 0xc0013b05c0>: {
        s: "Timed out waiting for service endpoint-test2 in namespace services-205 to expose endpoints map[pod1:[80] pod2:[80]] (3m0s elapsed)",
    }
    Timed out waiting for service endpoint-test2 in namespace services-205 to expose endpoints map[pod1:[80] pod2:[80]] (3m0s elapsed)
occurred
test/e2e/network/service.go:168
				
				Click to see stdout/stderrfrom junit_20.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-network] Services should serve a basic endpoint from pods [Conformance] 13m30s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sServices\sshould\sserve\sa\sbasic\sendpoint\sfrom\spods\s\s\[Conformance\]$'
test/e2e/framework/framework.go:152
Nov 10 05:25:56.974: Couldn't delete ns: "services-3383": namespace services-3383 was not deleted with limit: timed out waiting for the condition, pods remaining: 1 (&errors.errorString{s:"namespace services-3383 was not deleted with limit: timed out waiting for the condition, pods remaining: 1"})
test/e2e/framework/framework.go:336
				
				Click to see stdout/stderrfrom junit_20.xml

Filter through log files | View test history on testgrid


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

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 10 04:48:59.310: Unexpected error:
    <*errors.errorString | 0xc001d0c780>: {
        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