This job view page is being replaced by Spyglass soon. Check out the new job view.
PRmortent: Promote PodDisruptionBudget to policy/v1
ResultFAILURE
Tests 74 failed / 470 succeeded
Started2021-02-22 05:53
Elapsed1h15m
Revision4fc55d6e6aab54f503de3b6b7949cb1c424de53f
Refs 99290

Test Failures


Kubernetes e2e suite [k8s.io] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart exec hook properly [NodeConformance] [Conformance] 5m3s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[k8s\.io\]\sContainer\sLifecycle\sHook\swhen\screate\sa\spod\swith\slifecycle\shook\sshould\sexecute\spoststart\sexec\shook\sproperly\s\[NodeConformance\]\s\[Conformance\]$'
test/e2e/common/lifecycle_hook.go:52
Feb 22 06:52:46.343: Unexpected error:
    <*errors.errorString | 0xc00023e240>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
test/e2e/framework/pods.go:103
				
				Click to see stdout/stderrfrom junit_25.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [k8s.io] Docker Containers should be able to override the image's default command (docker entrypoint) [NodeConformance] [Conformance] 5m4s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[k8s\.io\]\sDocker\sContainers\sshould\sbe\sable\sto\soverride\sthe\simage\'s\sdefault\scommand\s\(docker\sentrypoint\)\s\[NodeConformance\]\s\[Conformance\]$'
test/e2e/framework/framework.go:640
Feb 22 06:50:00.449: Unexpected error:
    <*errors.errorString | 0xc00381db70>: {
        s: "expected pod \"client-containers-50daa92d-3e95-4110-bc28-523f06e0ddbf\" success: Gave up after waiting 5m0s for pod \"client-containers-50daa92d-3e95-4110-bc28-523f06e0ddbf\" to be \"Succeeded or Failed\"",
    }
    expected pod "client-containers-50daa92d-3e95-4110-bc28-523f06e0ddbf" success: Gave up after waiting 5m0s for pod "client-containers-50daa92d-3e95-4110-bc28-523f06e0ddbf" to be "Succeeded or Failed"
occurred
test/e2e/framework/util.go:742
				
				Click to see stdout/stderrfrom junit_10.xml

Find client-containers-50daa92d-3e95-4110-bc28-523f06e0ddbf mentions in log files | View test history on testgrid


Kubernetes e2e suite [k8s.io] InitContainer [NodeConformance] should invoke init containers on a RestartNever pod [Conformance] 5m2s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[k8s\.io\]\sInitContainer\s\[NodeConformance\]\sshould\sinvoke\sinit\scontainers\son\sa\sRestartNever\spod\s\[Conformance\]$'
test/e2e/framework/framework.go:640
Feb 22 06:31:51.615: Unexpected error:
    <*errors.errorString | 0xc0002b8230>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
test/e2e/common/init_container.go:225
				
				Click to see stdout/stderrfrom junit_03.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [k8s.io] InitContainer [NodeConformance] should not start app containers if init containers fail on a RestartAlways pod [Conformance] 5m2s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[k8s\.io\]\sInitContainer\s\[NodeConformance\]\sshould\snot\sstart\sapp\scontainers\sif\sinit\scontainers\sfail\son\sa\sRestartAlways\spod\s\[Conformance\]$'
test/e2e/framework/framework.go:640
Feb 22 06:46:21.698: Unexpected error:
    <*errors.errorString | 0xc0002b0230>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
test/e2e/common/init_container.go:432
				
				Click to see stdout/stderrfrom junit_17.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [k8s.io] Kubelet when scheduling a busybox Pod with hostAliases should write entries to /etc/hosts [LinuxOnly] [NodeConformance] [Conformance] 5m1s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[k8s\.io\]\sKubelet\swhen\sscheduling\sa\sbusybox\sPod\swith\shostAliases\sshould\swrite\sentries\sto\s\/etc\/hosts\s\[LinuxOnly\]\s\[NodeConformance\]\s\[Conformance\]$'
test/e2e/framework/framework.go:640
Feb 22 06:46:13.825: Unexpected error:
    <*errors.errorString | 0xc00023a230>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
test/e2e/framework/pods.go:103
				
				Click to see stdout/stderrfrom junit_14.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [k8s.io] Probing container should not be ready until startupProbe succeeds 5m4s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[k8s\.io\]\sProbing\scontainer\sshould\snot\sbe\sready\suntil\sstartupProbe\ssucceeds$'
test/e2e/common/container_probe.go:376
Feb 22 06:20:50.493: Unexpected error:
    <*errors.errorString | 0xc00328f2c0>: {
        s: "want pod 'startup-1d013ead-ad51-427e-a6b1-45912c7f91ba' on 'kind-worker' to be 'Running' but was 'Pending'",
    }
    want pod 'startup-1d013ead-ad51-427e-a6b1-45912c7f91ba' on 'kind-worker' to be 'Running' but was 'Pending'
occurred
test/e2e/common/container_probe.go:406
				
				Click to see stdout/stderrfrom junit_07.xml

Find startup-1d013ead-ad51-427e-a6b1-45912c7f91ba mentions in log files | View test history on testgrid


Kubernetes e2e suite [k8s.io] [sig-network] Networking Granular Checks: Pods should function for node-pod communication: http [LinuxOnly] [NodeConformance] [Conformance] 9m37s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[k8s\.io\]\s\[sig\-network\]\sNetworking\sGranular\sChecks\:\sPods\sshould\sfunction\sfor\snode\-pod\scommunication\:\shttp\s\[LinuxOnly\]\s\[NodeConformance\]\s\[Conformance\]$'
test/e2e/framework/framework.go:640
Feb 22 06:56:00.718: Unexpected error:
    <*errors.errorString | 0xc0002b0230>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
test/e2e/framework/network/utils.go:695
				
				Click to see stdout/stderrfrom junit_17.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [k8s.io] [sig-node] Security Context should support seccomp unconfined on the container [LinuxOnly] 5m7s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[k8s\.io\]\s\[sig\-node\]\sSecurity\sContext\sshould\ssupport\sseccomp\sunconfined\son\sthe\scontainer\s\[LinuxOnly\]$'
test/e2e/node/security_context.go:149
Feb 22 06:32:09.554: Unexpected error:
    <*errors.errorString | 0xc0020a1490>: {
        s: "expected pod \"security-context-74a0b940-87d6-4406-a6a8-7ec5c6949fac\" success: Gave up after waiting 5m0s for pod \"security-context-74a0b940-87d6-4406-a6a8-7ec5c6949fac\" to be \"Succeeded or Failed\"",
    }
    expected pod "security-context-74a0b940-87d6-4406-a6a8-7ec5c6949fac" success: Gave up after waiting 5m0s for pod "security-context-74a0b940-87d6-4406-a6a8-7ec5c6949fac" to be "Succeeded or Failed"
occurred
test/e2e/framework/util.go:742
				
				Click to see stdout/stderrfrom junit_02.xml

Find security-context-74a0b940-87d6-4406-a6a8-7ec5c6949fac 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. 15m22s

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 22 06:54:40.915: Unexpected error:
    <*errors.errorString | 0xc000238230>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
test/e2e/node/kubelet.go:376
				
				Click to see stdout/stderrfrom junit_08.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [k8s.io] [sig-storage] EmptyDir volumes should support (root,0644,default) [LinuxOnly] [NodeConformance] [Conformance] 5m6s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[k8s\.io\]\s\[sig\-storage\]\sEmptyDir\svolumes\sshould\ssupport\s\(root\,0644\,default\)\s\[LinuxOnly\]\s\[NodeConformance\]\s\[Conformance\]$'
test/e2e/framework/framework.go:640
Feb 22 06:54:14.229: Unexpected error:
    <*errors.errorString | 0xc003993ed0>: {
        s: "expected pod \"pod-bf60e3c4-eb98-4a66-937e-5a6f12d5eddf\" success: Gave up after waiting 5m0s for pod \"pod-bf60e3c4-eb98-4a66-937e-5a6f12d5eddf\" to be \"Succeeded or Failed\"",
    }
    expected pod "pod-bf60e3c4-eb98-4a66-937e-5a6f12d5eddf" success: Gave up after waiting 5m0s for pod "pod-bf60e3c4-eb98-4a66-937e-5a6f12d5eddf" to be "Succeeded or Failed"
occurred
test/e2e/framework/util.go:742
				
				Click to see stdout/stderrfrom junit_02.xml

Find pod-bf60e3c4-eb98-4a66-937e-5a6f12d5eddf mentions in log files | View test history on testgrid


Kubernetes e2e suite [k8s.io] [sig-storage] Projected configMap updates should be reflected in volume [NodeConformance] [Conformance] 5m2s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[k8s\.io\]\s\[sig\-storage\]\sProjected\sconfigMap\supdates\sshould\sbe\sreflected\sin\svolume\s\[NodeConformance\]\s\[Conformance\]$'
test/e2e/framework/framework.go:640
Feb 22 06:47:28.676: Unexpected error:
    <*errors.errorString | 0xc0002b0230>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
test/e2e/framework/pods.go:103
				
				Click to see stdout/stderrfrom junit_22.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [k8s.io] [sig-storage] Projected secret should be able to mount in a volume regardless of a different secret existing with same name in different namespace [NodeConformance] 5m9s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[k8s\.io\]\s\[sig\-storage\]\sProjected\ssecret\sshould\sbe\sable\sto\smount\sin\sa\svolume\sregardless\sof\sa\sdifferent\ssecret\sexisting\swith\ssame\sname\sin\sdifferent\snamespace\s\[NodeConformance\]$'
test/e2e/common/projected_secret.go:90
Feb 22 06:11:43.764: Unexpected error:
    <*errors.errorString | 0xc002dbb5d0>: {
        s: "expected pod \"pod-projected-secrets-17df1380-8781-4095-abbf-cf6366c072f1\" success: Gave up after waiting 5m0s for pod \"pod-projected-secrets-17df1380-8781-4095-abbf-cf6366c072f1\" to be \"Succeeded or Failed\"",
    }
    expected pod "pod-projected-secrets-17df1380-8781-4095-abbf-cf6366c072f1" success: Gave up after waiting 5m0s for pod "pod-projected-secrets-17df1380-8781-4095-abbf-cf6366c072f1" to be "Succeeded or Failed"
occurred
test/e2e/framework/util.go:742