This job view page is being replaced by Spyglass soon. Check out the new job view.
PRchymy: Remove unused code in test/e2e/{upgrades,storage,network}
ResultFAILURE
Tests 13 failed / 652 succeeded
Started2021-02-23 08:40
Elapsed38m1s
Revisionc32793a4c9a79964f4c0ff5cdbd5fb505e3655ec
Refs 99348

Test Failures


Kubernetes e2e suite [k8s.io] Probing container should be restarted by liveness probe after startup probe enables it 5m1s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[k8s\.io\]\sProbing\scontainer\sshould\sbe\srestarted\sby\sliveness\sprobe\safter\sstartup\sprobe\senables\sit$'
test/e2e/common/container_probe.go:347
Feb 23 09:12:24.129: starting pod startup-bb7b426a-84a2-4846-ba3c-dac004dcc7c8 in namespace container-probe-5010
Unexpected error:
    <*errors.errorString | 0xc0002b8230>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
test/e2e/common/container_probe.go:592
				
				Click to see stdout/stderrfrom junit_08.xml

Find startup-bb7b426a-84a2-4846-ba3c-dac004dcc7c8 mentions in log files | View test history on testgrid


Kubernetes e2e suite [k8s.io] Variable Expansion should allow substituting values in a volume subpath [sig-storage] [Conformance] 5m5s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[k8s\.io\]\sVariable\sExpansion\sshould\sallow\ssubstituting\svalues\sin\sa\svolume\ssubpath\s\[sig\-storage\]\s\[Conformance\]$'
test/e2e/framework/framework.go:640
Feb 23 09:13:58.072: Unexpected error:
    <*errors.errorString | 0xc002c60db0>: {
        s: "expected pod \"var-expansion-77101514-3293-45a8-ad20-4eb1a38e3aad\" success: Gave up after waiting 5m0s for pod \"var-expansion-77101514-3293-45a8-ad20-4eb1a38e3aad\" to be \"Succeeded or Failed\"",
    }
    expected pod "var-expansion-77101514-3293-45a8-ad20-4eb1a38e3aad" success: Gave up after waiting 5m0s for pod "var-expansion-77101514-3293-45a8-ad20-4eb1a38e3aad" to be "Succeeded or Failed"
occurred
test/e2e/framework/util.go:742
				
				Click to see stdout/stderrfrom junit_13.xml

Find var-expansion-77101514-3293-45a8-ad20-4eb1a38e3aad mentions in log files | View test history on testgrid


Kubernetes e2e suite [k8s.io] [sig-node] kubelet [k8s.io] [sig-node] Clean up pods on node kubelet should be able to delete 10 pods per node in 1m0s. 9m31s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[k8s\.io\]\s\[sig\-node\]\skubelet\s\[k8s\.io\]\s\[sig\-node\]\sClean\sup\spods\son\snode\skubelet\sshould\sbe\sable\sto\sdelete\s10\spods\sper\snode\sin\s1m0s\.$'
test/e2e/node/kubelet.go:341
Feb 23 09:13:52.586: Unexpected error:
    <*errors.errorString | 0xc001e5b8d0>: {
        s: "Only 19 pods started out of 20",
    }
    Only 19 pods started out of 20
occurred
test/e2e/node/kubelet.go:354
				
				Click to see stdout/stderrfrom junit_02.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [k8s.io] [sig-storage] EmptyDir volumes volume on tmpfs should have the correct mode [LinuxOnly] [NodeConformance] [Conformance] 5m5s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[k8s\.io\]\s\[sig\-storage\]\sEmptyDir\svolumes\svolume\son\stmpfs\sshould\shave\sthe\scorrect\smode\s\[LinuxOnly\]\s\[NodeConformance\]\s\[Conformance\]$'
test/e2e/framework/framework.go:640
Feb 23 09:14:13.604: Unexpected error:
    <*errors.errorString | 0xc00221c3b0>: {
        s: "expected pod \"pod-e7f8809c-4952-4f0f-9365-d1a1c9e5d876\" success: Gave up after waiting 5m0s for pod \"pod-e7f8809c-4952-4f0f-9365-d1a1c9e5d876\" to be \"Succeeded or Failed\"",
    }
    expected pod "pod-e7f8809c-4952-4f0f-9365-d1a1c9e5d876" success: Gave up after waiting 5m0s for pod "pod-e7f8809c-4952-4f0f-9365-d1a1c9e5d876" to be "Succeeded or Failed"
occurred
test/e2e/framework/util.go:742
				
				Click to see stdout/stderrfrom junit_09.xml

Find pod-e7f8809c-4952-4f0f-9365-d1a1c9e5d876 mentions in log files | View test history on testgrid


Kubernetes e2e suite [k8s.io] [sig-storage] EmptyDir volumes when FSGroup is specified [LinuxOnly] [NodeFeature:FSGroup] new files should be created with FSGroup ownership when container is root 5m6s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[k8s\.io\]\s\[sig\-storage\]\sEmptyDir\svolumes\swhen\sFSGroup\sis\sspecified\s\[LinuxOnly\]\s\[NodeFeature\:FSGroup\]\snew\sfiles\sshould\sbe\screated\swith\sFSGroup\sownership\swhen\scontainer\sis\sroot$'
test/e2e/common/empty_dir.go:55
Feb 23 09:12:05.119: Unexpected error:
    <*errors.errorString | 0xc001dace10>: {
        s: "expected pod \"pod-dcc0faaa-07cf-41d7-8ec7-ce0156b23032\" success: Gave up after waiting 5m0s for pod \"pod-dcc0faaa-07cf-41d7-8ec7-ce0156b23032\" to be \"Succeeded or Failed\"",
    }
    expected pod "pod-dcc0faaa-07cf-41d7-8ec7-ce0156b23032" success: Gave up after waiting 5m0s for pod "pod-dcc0faaa-07cf-41d7-8ec7-ce0156b23032" to be "Succeeded or Failed"
occurred
test/e2e/framework/util.go:742
				
				Click to see stdout/stderrfrom junit_17.xml

Find pod-dcc0faaa-07cf-41d7-8ec7-ce0156b23032 mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-apps] ReplicaSet Replicaset should have a working scale subresource 5m7s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-apps\]\sReplicaSet\sReplicaset\sshould\shave\sa\sworking\sscale\ssubresource$'
test/e2e/apps/replica_set.go:122
Feb 23 09:12:53.938: error in waiting for pods to come up: failed to wait for pods running: [timed out waiting for the condition]
Unexpected error:
    <*errors.errorString | 0xc002cbf340>: {
        s: "failed to wait for pods running: [timed out waiting for the condition]",
    }
    failed to wait for pods running: [timed out waiting for the condition]
occurred
test/e2e/apps/replica_set.go:371
				
				Click to see stdout/stderrfrom junit_06.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 10m31s

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:501
Feb 23 09:14:23.740: Failed waiting for pods to enter running: timed out waiting for the condition
test/e2e/framework/statefulset/wait.go:80
				
				Click to see stdout/stderrfrom junit_14.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-cli] Kubectl client Simple pod should return command exit codes 3m49s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-cli\]\sKubectl\sclient\sSimple\spod\sshould\sreturn\scommand\sexit\scodes$'
test/e2e/kubectl/kubectl.go:502
Feb 23 08:57:33.787: Unexpected error:
    <exec.CodeExitError>: {
        Err: {
            s: "error running /home/prow/go/src/k8s.io/kubernetes/bazel-out/k8-fastbuild-ST-5e46445d989a/bin/cmd/kubectl/kubectl_/kubectl --server=https://127.0.0.1:33441 --kubeconfig=/root/.kube/kind-test-config --namespace=kubectl-507 run -i --image=k8s.gcr.io/e2e-test-images/busybox:1.29 --restart=Never failure-4 --leave-stdin-open -- /bin/sh -c exit 42:\nCommand stdout:\n\nstderr:\nerror: timed out waiting for the condition\n\nerror:\nexit status 1",
        },
        Code: 1,
    }
    error running /home/prow/go/src/k8s.io/kubernetes/bazel-out/k8-fastbuild-ST-5e46445d989a/bin/cmd/kubectl/kubectl_/kubectl --server=https://127.0.0.1:33441 --kubeconfig=/root/.kube/kind-test-config --namespace=kubectl-507 run -i --image=k8s.gcr.io/e2e-test-images/busybox:1.29 --restart=Never failure-4 --leave-stdin-open -- /bin/sh -c exit 42:
    Command stdout:
    
    stderr:
    error: timed out waiting for the condition
    
    error:
    exit status 1
occurred
test/e2e/kubectl/kubectl.go:548
				
				Click to see stdout/stderrfrom junit_25.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-network] Services should allow pods to hairpin back to themselves through services 5m3s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sServices\sshould\sallow\spods\sto\shairpin\sback\sto\sthemselves\sthrough\sservices$'
test/e2e/network/service.go:979
Feb 23 09:12:03.804: Unexpected error:
    <*errors.errorString | 0xc000238230>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
test/e2e/network/service.go:997
				
				Click to see stdout/stderrfrom junit_19.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-network] Services should be able to update service type to NodePort listening on same port number but different protocols 5m4s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sServices\sshould\sbe\sable\sto\supdate\sservice\stype\sto\sNodePort\slistening\son\ssame\sport\snumber\sbut\sdifferent\sprotocols$'
test/e2e/network/service.go:1202
Feb 23 09:08:35.038: Unexpected error:
    <*errors.errorString | 0xc001fa6290>: {
        s: "Only 0 pods started out of 2",
    }
    Only 0 pods started out of 2
occurred
test/e2e/network/service.go:1232
				
				Click to see stdout/stderrfrom junit_09.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] volumes should store data 5m45s

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\(block\svolmode\)\]\svolumes\sshould\sstore\sdata$'
test/e2e/storage/testsuites/volumes.go:159
Feb 23 09:08:15.950: Failed to create injector pod: timed out waiting for the condition
test/e2e/storage/testsuites/volumes.go:186
				
				Click to see stdout/stderrfrom junit_13.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] CSI mock volume CSI FSGroupPolicy [LinuxOnly] should modify fsGroup if fsGroupPolicy=File 5m28s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sCSI\smock\svolume\sCSI\sFSGroupPolicy\s\[LinuxOnly\]\sshould\smodify\sfsGroup\sif\sfsGroupPolicy\=File$'
test/e2e/storage/csi_mock_volume.go:1435
Feb 23 09:12:33.844: failed to start pod
Unexpected error:
    <*errors.errorString | 0xc0002b8230>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
test/e2e/storage/csi_mock_volume.go:1461
				
				Click to see stdout/stderrfrom junit_21.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] CSI mock volume CSI workload information using mock driver should not be passed when CSIDriver does not exist 5m25s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sCSI\smock\svolume\sCSI\sworkload\sinformation\susing\smock\sdriver\sshould\snot\sbe\spassed\swhen\sCSIDriver\sdoes\snot\sexist$'
test/e2e/storage/csi_mock_volume.go:488
Feb 23 09:12:09.047: Failed to start pod: timed out waiting for the condition
Unexpected error:
    <*errors.errorString | 0xc00023e240>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
test/e2e/storage/csi_mock_volume.go:500
				
				Click to see stdout/stderrfrom junit_23.xml

Filter through log files | View test history on testgrid


Show 652 Passed Tests

Show 5061 Skipped Tests