kubernetes: kubernetes-e2e-gci-gke-test: broken test run

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gke-test/85/

Multiple broken tests:

Failed: [k8s.io] Kubelet [Serial] [Slow] [k8s.io] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubelet_perf.go:278
Oct 14 21:40:49.585: CPU usage exceeding limits:
 node gke-jenkins-e2e-default-pool-e08108cf-v7ys:
 container "kubelet": expected 95th% usage < 0.220; got 0.236
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubelet_perf.go:187

Issues about this test specifically: #26982 #32214 #33994 #34035

Failed: [k8s.io] V1Job should fail a job [Slow] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:134
Oct 14 23:36:03.850: All nodes should be ready after test, an error on the server ("Internal Server Error: \"/api/v1/nodes\"") has prevented the request from succeeding (get nodes)
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:418

Failed: [k8s.io] Pods should have their auto-restart back-off timer reset on image update [Slow] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/pods.go:628
getting pod pod-back-off-image
Expected error:
    <*errors.StatusError | 0xc821860b00>: {
        ErrStatus: {
            TypeMeta: {Kind: "", APIVersion: ""},
            ListMeta: {SelfLink: "", ResourceVersion: ""},
            Status: "Failure",
            Message: "the server has asked for the client to provide credentials (get pods pod-back-off-image)",
            Reason: "Unauthorized",
            Details: {
                Name: "pod-back-off-image",
                Group: "",
                Kind: "pods",
                Causes: [
                    {
                        Type: "UnexpectedServerResponse",
                        Message: "Unauthorized",
                        Field: "",
                    },
                ],
                RetryAfterSeconds: 0,
            },
            Code: 401,
        },
    }
    the server has asked for the client to provide credentials (get pods pod-back-off-image)
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/pods.go:105

Issues about this test specifically: #27360 #28096 #29615 #31775

Failed: [k8s.io] SchedulerPredicates [Serial] validates that NodeAffinity is respected if not matching {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:233
Expected error:
    <*errors.errorString | 0xc820de5680>: {
        s: "Namespace e2e-tests-v1job-h2mpf is active",
    }
    Namespace e2e-tests-v1job-h2mpf is active
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:211

Issues about this test specifically: #28019

Previous issues for this suite: #33400 #34077 #34835

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 31 (31 by maintainers)

Most upvoted comments

“broken test run” tends to show different sets of failures over time. So closing a bunch of them now during 1.5 release triage to let the bot open fresh ones.