kubernetes-sigs/aws-ebs-csi-driver PR #1233 pull-aws-ebs-csi-driver-external-test #1524210890017083392
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | torredil: Use minimal base image for linux builds |
| Result | ABORTED |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 28m19s |
| Revision | 2c204d817c821519bc2eabd7c1476918d08f4c4d |
| Refs |
1233 |
... skipping 635 lines ... ## Validating cluster test-cluster-6040.k8s.local # Using cluster from kubectl context: test-cluster-6040.k8s.local Validating cluster test-cluster-6040.k8s.local W0511 02:15:14.128466 9152 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-6040-k8s-qprg3k-175306052.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-6040-k8s-qprg3k-175306052.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host W0511 02:15:24.165229 9152 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-6040-k8s-qprg3k-175306052.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-6040-k8s-qprg3k-175306052.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host W0511 02:15:34.187654 9152 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-6040-k8s-qprg3k-175306052.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-6040-k8s-qprg3k-175306052.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host W0511 02:15:44.223497 9152 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-6040-k8s-qprg3k-175306052.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-6040-k8s-qprg3k-175306052.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host W0511 02:15:54.252946 9152 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-6040-k8s-qprg3k-175306052.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-6040-k8s-qprg3k-175306052.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host W0511 02:16:05.415843 9152 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-6040-k8s-qprg3k-175306052.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-6040-k8s-qprg3k-175306052.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host W0511 02:16:24.659789 9152 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-6040-k8s-qprg3k-175306052.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-6040-k8s-qprg3k-175306052.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host W0511 02:16:46.140169 9152 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-6040-k8s-qprg3k-175306052.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-6040-k8s-qprg3k-175306052.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host W0511 02:17:07.768235 9152 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes) W0511 02:17:29.318902 9152 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes) W0511 02:17:50.891607 9152 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes) INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master t3.medium 1 1 us-west-2a nodes-us-west-2a Node c5.large 1 1 us-west-2a nodes-us-west-2b Node c5.large 1 1 us-west-2b nodes-us-west-2c Node c5.large 1 1 us-west-2c ... skipping 6 lines ... KIND NAME MESSAGE Machine i-0772809d9ced215a5 machine "i-0772809d9ced215a5" has not yet joined cluster Machine i-09db03f7e69514aa1 machine "i-09db03f7e69514aa1" has not yet joined cluster Machine i-09e8afb7184f10ac6 machine "i-09e8afb7184f10ac6" has not yet joined cluster Node ip-172-20-34-85.us-west-2.compute.internal node "ip-172-20-34-85.us-west-2.compute.internal" of role "master" is not ready Validation Failed W0511 02:18:04.866747 9152 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master t3.medium 1 1 us-west-2a nodes-us-west-2a Node c5.large 1 1 us-west-2a nodes-us-west-2b Node c5.large 1 1 us-west-2b ... skipping 9 lines ... Machine i-09db03f7e69514aa1 machine "i-09db03f7e69514aa1" has not yet joined cluster Machine i-09e8afb7184f10ac6 machine "i-09e8afb7184f10ac6" has not yet joined cluster Node ip-172-20-34-85.us-west-2.compute.internal node "ip-172-20-34-85.us-west-2.compute.internal" of role "master" is not ready Pod kube-system/coredns-8f5559c9b-7pjs8 system-cluster-critical pod "coredns-8f5559c9b-7pjs8" is pending Pod kube-system/coredns-autoscaler-6f594f4c58-gmpd9 system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gmpd9" is pending Validation Failed W0511 02:18:17.195865 9152 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master t3.medium 1 1 us-west-2a nodes-us-west-2a Node c5.large 1 1 us-west-2a nodes-us-west-2b Node c5.large 1 1 us-west-2b ... skipping 11 lines ... Node ip-172-20-34-85.us-west-2.compute.internal master "ip-172-20-34-85.us-west-2.compute.internal" is missing kube-apiserver pod Node ip-172-20-34-85.us-west-2.compute.internal master "ip-172-20-34-85.us-west-2.compute.internal" is missing kube-controller-manager pod Node ip-172-20-34-85.us-west-2.compute.internal master "ip-172-20-34-85.us-west-2.compute.internal" is missing kube-scheduler pod Pod kube-system/coredns-8f5559c9b-7pjs8 system-cluster-critical pod "coredns-8f5559c9b-7pjs8" is pending Pod kube-system/coredns-autoscaler-6f594f4c58-gmpd9 system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gmpd9" is pending Validation Failed W0511 02:18:29.299819 9152 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master t3.medium 1 1 us-west-2a nodes-us-west-2a Node c5.large 1 1 us-west-2a nodes-us-west-2b Node c5.large 1 1 us-west-2b ... skipping 13 lines ... Node ip-172-20-34-85.us-west-2.compute.internal master "ip-172-20-34-85.us-west-2.compute.internal" is missing kube-scheduler pod Pod kube-system/coredns-8f5559c9b-7pjs8 system-cluster-critical pod "coredns-8f5559c9b-7pjs8" is pending Pod kube-system/coredns-autoscaler-6f594f4c58-gmpd9 system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gmpd9" is pending Pod kube-system/kube-controller-manager-ip-172-20-34-85.us-west-2.compute.internal system-cluster-critical pod "kube-controller-manager-ip-172-20-34-85.us-west-2.compute.internal" is pending Pod kube-system/kube-scheduler-ip-172-20-34-85.us-west-2.compute.internal system-cluster-critical pod "kube-scheduler-ip-172-20-34-85.us-west-2.compute.internal" is pending Validation Failed W0511 02:18:41.353340 9152 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master t3.medium 1 1 us-west-2a nodes-us-west-2a Node c5.large 1 1 us-west-2a nodes-us-west-2b Node c5.large 1 1 us-west-2b ... skipping 13 lines ... Pod kube-system/coredns-autoscaler-6f594f4c58-gmpd9 system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gmpd9" is pending Pod kube-system/etcd-manager-events-ip-172-20-34-85.us-west-2.compute.internal system-cluster-critical pod "etcd-manager-events-ip-172-20-34-85.us-west-2.compute.internal" is pending Pod kube-system/etcd-manager-main-ip-172-20-34-85.us-west-2.compute.internal system-cluster-critical pod "etcd-manager-main-ip-172-20-34-85.us-west-2.compute.internal" is pending Pod kube-system/kube-apiserver-ip-172-20-34-85.us-west-2.compute.internal system-cluster-critical pod "kube-apiserver-ip-172-20-34-85.us-west-2.compute.internal" is pending Pod kube-system/kube-proxy-ip-172-20-34-85.us-west-2.compute.internal system-node-critical pod "kube-proxy-ip-172-20-34-85.us-west-2.compute.internal" is pending Validation Failed W0511 02:18:53.539019 9152 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master t3.medium 1 1 us-west-2a nodes-us-west-2a Node c5.large 1 1 us-west-2a nodes-us-west-2b Node c5.large 1 1 us-west-2b ... skipping 9 lines ... KIND NAME MESSAGE Machine i-09e8afb7184f10ac6 machine "i-09e8afb7184f10ac6" has not yet joined cluster Node ip-172-20-87-59.us-west-2.compute.internal node "ip-172-20-87-59.us-west-2.compute.internal" of role "node" is not ready Pod kube-system/coredns-8f5559c9b-7pjs8 system-cluster-critical pod "coredns-8f5559c9b-7pjs8" is pending Pod kube-system/coredns-autoscaler-6f594f4c58-gmpd9 system-cluster-critical pod "coredns-autoscaler-6f594f4c58-gmpd9" is pending Validation Failed W0511 02:19:05.635165 9152 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master t3.medium 1 1 us-west-2a nodes-us-west-2a Node c5.large 1 1 us-west-2a nodes-us-west-2b Node c5.large 1 1 us-west-2b ... skipping 9 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node ip-172-20-87-59.us-west-2.compute.internal node "ip-172-20-87-59.us-west-2.compute.internal" of role "node" is not ready Pod kube-system/coredns-8f5559c9b-7pjs8 system-cluster-critical pod "coredns-8f5559c9b-7pjs8" is not ready (coredns) Pod kube-system/coredns-8f5559c9b-cctkc system-cluster-critical pod "coredns-8f5559c9b-cctkc" is not ready (coredns) Validation Failed W0511 02:19:18.083571 9152 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master t3.medium 1 1 us-west-2a nodes-us-west-2a Node c5.large 1 1 us-west-2a nodes-us-west-2b Node c5.large 1 1 us-west-2b ... skipping 250 lines ...