This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 3 failed / 766 succeeded
Started2022-12-02 11:48
Elapsed35m27s
Revisionmaster

Test Failures


Kubernetes e2e suite [sig-network] Proxy version v1 should proxy through a service and a pod [Conformance] 3m22s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sProxy\sversion\sv1\sshould\sproxy\sthrough\sa\sservice\sand\sa\spod\s\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:633
Dec  2 12:16:16.693: 0: path /api/v1/namespaces/proxy-6288/services/http:proxy-service-768v9:portname2/proxy/ gave error: Get "https://api.e2e-e2e-kops-grid-calico-u2004-k23-ko25.test-cncf-aws.k8s.io/api/v1/namespaces/proxy-6288/services/http:proxy-service-768v9:portname2/proxy/": http2: client connection lost
0: path /api/v1/namespaces/proxy-6288/pods/proxy-service-768v9-8kk2s:160/proxy/ gave error: Get "https://api.e2e-e2e-kops-grid-calico-u2004-k23-ko25.test-cncf-aws.k8s.io/api/v1/namespaces/proxy-6288/pods/proxy-service-768v9-8kk2s:160/proxy/": http2: client connection lost
0: path /api/v1/namespaces/proxy-6288/pods/proxy-service-768v9-8kk2s/proxy/ took 3m1.549589264s > 30s
0: path /api/v1/namespaces/proxy-6288/pods/http:proxy-service-768v9-8kk2s:162/proxy/ took 3m1.69334132s > 30s
0: path /api/v1/namespaces/proxy-6288/pods/http:proxy-service-768v9-8kk2s:1080/proxy/ took 3m2.013489141s > 30s
0: path /api/v1/namespaces/proxy-6288/pods/https:proxy-service-768v9-8kk2s:460/proxy/ took 3m2.014475504s > 30s
0: path /api/v1/namespaces/proxy-6288/services/https:proxy-service-768v9:tlsportname1/proxy/ took 3m1.747022726s > 30s
0: path /api/v1/namespaces/proxy-6288/services/proxy-service-768v9:portname1/proxy/ took 3m2.100398686s > 30s
0: path /api/v1/namespaces/proxy-6288/services/https:proxy-service-768v9:tlsportname2/proxy/ took 3m2.099968558s > 30s
0: path /api/v1/namespaces/proxy-6288/pods/https:proxy-service-768v9-8kk2s:462/proxy/ took 3m2.100504787s > 30s
0: path /api/v1/namespaces/proxy-6288/pods/https:proxy-service-768v9-8kk2s:443/proxy/ took 3m2.096233811s > 30s
0: path /api/v1/namespaces/proxy-6288/services/http:proxy-service-768v9:portname1/proxy/ took 3m2.095245898s > 30s
0: path /api/v1/namespaces/proxy-6288/pods/proxy-service-768v9-8kk2s:162/proxy/ took 3m2.111846983s > 30s
0: path /api/v1/namespaces/proxy-6288/services/proxy-service-768v9:portname2/proxy/ took 3m2.10153876s > 30s
0: path /api/v1/namespaces/proxy-6288/pods/proxy-service-768v9-8kk2s:1080/proxy/ took 3m2.111408422s > 30s
0: path /api/v1/namespaces/proxy-6288/pods/http:proxy-service-768v9-8kk2s:160/proxy/ took 3m1.812280953s > 30s
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113
				
				Click to see stdout/stderrfrom junit_05.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-node] Probing container should *not* be restarted by liveness probe because startup probe delays it 3m58s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-node\]\sProbing\scontainer\sshould\s\*not\*\sbe\srestarted\sby\sliveness\sprobe\sbecause\sstartup\sprobe\sdelays\sit$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/container_probe.go:353
Dec  2 12:16:12.856: getting pod 
Unexpected error:
    <*fmt.wrapError | 0xc00352a580>: {
        msg: "unexpected error when reading response body. Please retry. Original error: http2: client connection lost",
        err: {
            s: "http2: client connection lost",
        },
    }
    unexpected error when reading response body. Please retry. Original error: http2: client connection lost
occurred
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/container_probe.go:921
				
				Click to see stdout/stderrfrom junit_06.xml

Filter through log files | View test history on testgrid


kubetest2 Test 23m14s

exit status 255
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 766 Passed Tests

Show 6303 Skipped Tests