This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 17 failed / 12 succeeded
Started2020-10-24 02:58
Elapsed5h7m
Revision
Builderc828ab73-15a4-11eb-b256-6ee25ea2e440
infra-commitd88010efd
job-versionv1.20.0-alpha.3.112+1f756e4a375ce0
master_os_imagecos-85-13310-1041-9
node_os_imagecos-85-13310-1041-9
revisionv1.20.0-alpha.3.112+1f756e4a375ce0

Test Failures


Kubernetes e2e suite [sig-autoscaling] Cluster size autoscaling [Slow] Shouldn't perform scale up operation and should list unhealthy status if most of the cluster is broken[Feature:ClusterSizeAutoscalingScaleUp] 17m41s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-autoscaling\]\sCluster\ssize\sautoscaling\s\[Slow\]\sShouldn\'t\sperform\sscale\sup\soperation\sand\sshould\slist\sunhealthy\sstatus\sif\smost\sof\sthe\scluster\sis\sbroken\[Feature\:ClusterSizeAutoscalingScaleUp\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/cluster_size_autoscaling.go:881
Oct 24 03:29:27.078: Unexpected error:
    <*errors.StatusError | 0xc000d0fae0>: {
        ErrStatus: {
            TypeMeta: {Kind: "", APIVersion: ""},
            ListMeta: {
                SelfLink: "",
                ResourceVersion: "",
                Continue: "",
                RemainingItemCount: nil,
            },
            Status: "Failure",
            Message: "configmaps \"cluster-autoscaler-status\" not found",
            Reason: "NotFound",
            Details: {
                Name: "cluster-autoscaler-status",
                Group: "",
                Kind: "configmaps",
                UID: "",
                Causes: nil,
                RetryAfterSeconds: 0,
            },
            Code: 404,
        },
    }
    configmaps "cluster-autoscaler-status" not found
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/cluster_size_autoscaling.go:930
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-autoscaling] Cluster size autoscaling [Slow] should add node to the particular mig [Feature:ClusterSizeAutoscalingScaleUp] 38m29s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-autoscaling\]\sCluster\ssize\sautoscaling\s\[Slow\]\sshould\sadd\snode\sto\sthe\sparticular\smig\s\[Feature\:ClusterSizeAutoscalingScaleUp\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/cluster_size_autoscaling.go:538
Oct 24 04:42:26.191: Unexpected error:
    <*errors.errorString | 0xc0020f8330>: {
        s: "timeout waiting 5m0s for appropriate cluster size",
    }
    timeout waiting 5m0s for appropriate cluster size
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/cluster_size_autoscaling.go:583
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-autoscaling] Cluster size autoscaling [Slow] should be able to scale down by draining multiple pods one by one as dictated by pdb[Feature:ClusterSizeAutoscalingScaleDown] 25m6s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-autoscaling\]\sCluster\ssize\sautoscaling\s\[Slow\]\sshould\sbe\sable\sto\sscale\sdown\sby\sdraining\smultiple\spods\sone\sby\sone\sas\sdictated\sby\spdb\[Feature\:ClusterSizeAutoscalingScaleDown\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/cluster_size_autoscaling.go:733
Oct 24 07:32:00.362: Unexpected error:
    <*errors.errorString | 0xc000a640d0>: {
        s: "timeout waiting 20m0s for appropriate cluster size",
    }
    timeout waiting 20m0s for appropriate cluster size
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/cluster_size_autoscaling.go:736
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-autoscaling] Cluster size autoscaling [Slow] should be able to scale down by draining system pods with pdb[Feature:ClusterSizeAutoscalingScaleDown] 24m45s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-autoscaling\]\sCluster\ssize\sautoscaling\s\[Slow\]\sshould\sbe\sable\sto\sscale\sdown\sby\sdraining\ssystem\spods\swith\spdb\[Feature\:ClusterSizeAutoscalingScaleDown\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/cluster_size_autoscaling.go:741
Oct 24 06:36:23.885: Unexpected error:
    <*errors.errorString | 0xc0007c0e20>: {
        s: "timeout waiting 20m0s for appropriate cluster size",
    }
    timeout waiting 20m0s for appropriate cluster size
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/cluster_size_autoscaling.go:744
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-autoscaling] Cluster size autoscaling [Slow] should be able to scale down when rescheduling a pod is required and pdb allows for it[Feature:ClusterSizeAutoscalingScaleDown] 25m1s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-autoscaling\]\sCluster\ssize\sautoscaling\s\[Slow\]\sshould\sbe\sable\sto\sscale\sdown\swhen\srescheduling\sa\spod\sis\srequired\sand\spdb\sallows\sfor\sit\[Feature\:ClusterSizeAutoscalingScaleDown\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/cluster_size_autoscaling.go:715
Oct 24 05:40:14.720: Unexpected error:
    <*errors.errorString | 0xc0016c6000>: {
        s: "timeout waiting 20m0s for appropriate cluster size",
    }
    timeout waiting 20m0s for appropriate cluster size
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/cluster_size_autoscaling.go:718
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-autoscaling] Cluster size autoscaling [Slow] should correctly scale down after a node is not needed and one node is broken [Feature:ClusterSizeAutoscalingScaleDown] 24m45s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-autoscaling\]\sCluster\ssize\sautoscaling\s\[Slow\]\sshould\scorrectly\sscale\sdown\safter\sa\snode\sis\snot\sneeded\sand\sone\snode\sis\sbroken\s\[Feature\:ClusterSizeAutoscalingScaleDown\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/cluster_size_autoscaling.go:687
Oct 24 05:05:03.479: Unexpected error:
    <*errors.errorString | 0xc00307f490>: {
        s: "timeout waiting 20m0s for appropriate cluster size",
    }
    timeout waiting 20m0s for appropriate cluster size
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/cluster_size_autoscaling.go:680
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pending pods are small [Feature:ClusterSizeAutoscalingScaleUp] 6m15s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-autoscaling\]\sCluster\ssize\sautoscaling\s\[Slow\]\sshould\sincrease\scluster\ssize\sif\spending\spods\sare\ssmall\s\[Feature\:ClusterSizeAutoscalingScaleUp\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/cluster_size_autoscaling.go:204
Oct 24 06:05:15.782: Unexpected error:
    <*errors.errorString | 0xc000340480>: {
        s: "timeout waiting 5m0s for appropriate cluster size",
    }
    timeout waiting 5m0s for appropriate cluster size
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/cluster_size_autoscaling.go:199
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pending pods are small and one node is broken [Feature:ClusterSizeAutoscalingScaleUp] 7m18s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-autoscaling\]\sCluster\ssize\sautoscaling\s\[Slow\]\sshould\sincrease\scluster\ssize\sif\spending\spods\sare\ssmall\sand\sone\snode\sis\sbroken\s\[Feature\:ClusterSizeAutoscalingScaleUp\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/cluster_size_autoscaling.go:325
Oct 24 04:03:03.399: Unexpected error:
    <*errors.errorString | 0xc0036f2000>: {
        s: "timeout waiting 5m0s for appropriate cluster size",
    }
    timeout waiting 5m0s for appropriate cluster size
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/cluster_size_autoscaling.go:199
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pod requesting EmptyDir volume is pending [Feature:ClusterSizeAutoscalingScaleUp] 5m39s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-autoscaling\]\sCluster\ssize\sautoscaling\s\[Slow\]\sshould\sincrease\scluster\ssize\sif\spod\srequesting\sEmptyDir\svolume\sis\spending\s\[Feature\:ClusterSizeAutoscalingScaleUp\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/cluster_size_autoscaling.go:445
Oct 24 05:48:27.235: Unexpected error:
    <*errors.errorString | 0xc00061a9a0>: {
        s: "Only 0 pods started out of 1",
    }
    Only 0 pods started out of 1
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/cluster_size_autoscaling.go:459
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pod requesting volume is pending [Feature:ClusterSizeAutoscalingScaleUp] 10m45s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-autoscaling\]\sCluster\ssize\sautoscaling\s\[Slow\]\sshould\sincrease\scluster\ssize\sif\spod\srequesting\svolume\sis\spending\s\[Feature\:ClusterSizeAutoscalingScaleUp\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/cluster_size_autoscaling.go:466
Oct 24 05:12:41.687: Unexpected error:
    <*errors.errorString | 0xc000fd8770>: {
        s: "Only 0 pods started out of 1",
    }
    Only 0 pods started out of 1
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/cluster_size_autoscaling.go:528