kubernetes-sigs/aws-fsx-csi-driver PR #103 pull-aws-fsx-csi-driver-e2e #1181646266434588677
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | leakingtapan: Add e2e tests |
| Result | FAILURE |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 16m15s |
| Revision | 201ab4a280e2b1f8d080c7ba7c92469c3d48b4b7 |
| Refs |
103 |
... skipping 1398 lines ... Using cluster from kubectl context: test-cluster-43.k8s.local Validating cluster test-cluster-43.k8s.local unexpected error during validation: error listing nodes: Get https://api-test-cluster-43-k8s-l-slhle4-477816391.us-west-2.elb.amazonaws.com/api/v1/nodes: dial tcp: lookup api-test-cluster-43-k8s-l-slhle4-477816391.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host Using cluster from kubectl context: test-cluster-43.k8s.local Validating cluster test-cluster-43.k8s.local unexpected error during validation: error listing nodes: Get https://api-test-cluster-43-k8s-l-slhle4-477816391.us-west-2.elb.amazonaws.com/api/v1/nodes: dial tcp: lookup api-test-cluster-43-k8s-l-slhle4-477816391.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host Using cluster from kubectl context: test-cluster-43.k8s.local Validating cluster test-cluster-43.k8s.local unexpected error during validation: error listing nodes: Get https://api-test-cluster-43-k8s-l-slhle4-477816391.us-west-2.elb.amazonaws.com/api/v1/nodes: dial tcp: lookup api-test-cluster-43-k8s-l-slhle4-477816391.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host Using cluster from kubectl context: test-cluster-43.k8s.local Validating cluster test-cluster-43.k8s.local unexpected error during validation: error listing nodes: Get https://api-test-cluster-43-k8s-l-slhle4-477816391.us-west-2.elb.amazonaws.com/api/v1/nodes: dial tcp: lookup api-test-cluster-43-k8s-l-slhle4-477816391.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host Using cluster from kubectl context: test-cluster-43.k8s.local Validating cluster test-cluster-43.k8s.local unexpected error during validation: error listing nodes: Get https://api-test-cluster-43-k8s-l-slhle4-477816391.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF Using cluster from kubectl context: test-cluster-43.k8s.local Validating cluster test-cluster-43.k8s.local unexpected error during validation: error listing nodes: Get https://api-test-cluster-43-k8s-l-slhle4-477816391.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF Using cluster from kubectl context: test-cluster-43.k8s.local Validating cluster test-cluster-43.k8s.local unexpected error during validation: error listing nodes: Get https://api-test-cluster-43-k8s-l-slhle4-477816391.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF Using cluster from kubectl context: test-cluster-43.k8s.local Validating cluster test-cluster-43.k8s.local unexpected error during validation: error listing nodes: Get https://api-test-cluster-43-k8s-l-slhle4-477816391.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF Using cluster from kubectl context: test-cluster-43.k8s.local Validating cluster test-cluster-43.k8s.local unexpected error during validation: error listing nodes: Get https://api-test-cluster-43-k8s-l-slhle4-477816391.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF Using cluster from kubectl context: test-cluster-43.k8s.local Validating cluster test-cluster-43.k8s.local unexpected error during validation: error listing nodes: Get https://api-test-cluster-43-k8s-l-slhle4-477816391.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF Using cluster from kubectl context: test-cluster-43.k8s.local Validating cluster test-cluster-43.k8s.local unexpected error during validation: error listing nodes: Get https://api-test-cluster-43-k8s-l-slhle4-477816391.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF Using cluster from kubectl context: test-cluster-43.k8s.local Validating cluster test-cluster-43.k8s.local unexpected error during validation: error listing nodes: Get https://api-test-cluster-43-k8s-l-slhle4-477816391.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF Using cluster from kubectl context: test-cluster-43.k8s.local Validating cluster test-cluster-43.k8s.local unexpected error during validation: error listing nodes: Get https://api-test-cluster-43-k8s-l-slhle4-477816391.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF Using cluster from kubectl context: test-cluster-43.k8s.local Validating cluster test-cluster-43.k8s.local INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS ... skipping 8 lines ... KIND NAME MESSAGE Machine i-007f85e76cac05128 machine "i-007f85e76cac05128" has not yet joined cluster Machine i-038868bbb36a5ec9e machine "i-038868bbb36a5ec9e" has not yet joined cluster Machine i-0aa43fa8a15bb6289 machine "i-0aa43fa8a15bb6289" has not yet joined cluster Node ip-172-20-35-214.us-west-2.compute.internal master "ip-172-20-35-214.us-west-2.compute.internal" is not ready Validation Failed Using cluster from kubectl context: test-cluster-43.k8s.local Validating cluster test-cluster-43.k8s.local INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS ... skipping 11 lines ... Machine i-0aa43fa8a15bb6289 machine "i-0aa43fa8a15bb6289" has not yet joined cluster Node ip-172-20-35-214.us-west-2.compute.internal master "ip-172-20-35-214.us-west-2.compute.internal" is not ready Pod kube-system/aws-node-dnbjl kube-system pod "aws-node-dnbjl" is pending Pod kube-system/dns-controller-56455df565-t9n8l kube-system pod "dns-controller-56455df565-t9n8l" is pending Pod kube-system/kube-dns-autoscaler-577b4774b5-sxcbh kube-system pod "kube-dns-autoscaler-577b4774b5-sxcbh" is pending Validation Failed Using cluster from kubectl context: test-cluster-43.k8s.local Validating cluster test-cluster-43.k8s.local INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS ... skipping 9 lines ... Machine i-007f85e76cac05128 machine "i-007f85e76cac05128" has not yet joined cluster Machine i-038868bbb36a5ec9e machine "i-038868bbb36a5ec9e" has not yet joined cluster Machine i-0aa43fa8a15bb6289 machine "i-0aa43fa8a15bb6289" has not yet joined cluster Pod kube-system/kube-apiserver-ip-172-20-35-214.us-west-2.compute.internal kube-system pod "kube-apiserver-ip-172-20-35-214.us-west-2.compute.internal" is pending Pod kube-system/kube-dns-autoscaler-577b4774b5-sxcbh kube-system pod "kube-dns-autoscaler-577b4774b5-sxcbh" is pending Validation Failed Using cluster from kubectl context: test-cluster-43.k8s.local Validating cluster test-cluster-43.k8s.local INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS ... skipping 10 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node ip-172-20-56-158.us-west-2.compute.internal node "ip-172-20-56-158.us-west-2.compute.internal" is not ready Pod kube-system/kube-dns-66b6848cf6-hq6d7 kube-system pod "kube-dns-66b6848cf6-hq6d7" is pending Pod kube-system/kube-dns-autoscaler-577b4774b5-sxcbh kube-system pod "kube-dns-autoscaler-577b4774b5-sxcbh" is pending Validation Failed Using cluster from kubectl context: test-cluster-43.k8s.local Validating cluster test-cluster-43.k8s.local INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS ... skipping 169 lines ... dhcp-options:dopt-0f53f7b6c531b59fa ok Deleted kubectl config for test-cluster-43.k8s.local Deleted cluster: "test-cluster-43.k8s.local" 2019/10/08 19:19:38 exit status 2 exit status 1 Makefile:42: recipe for target 'test-e2e' failed make: *** [test-e2e] Error 1 + EXIT_VALUE=2 + set +o xtrace Cleaning up after docker in docker. ================================================================================ [Barnacle] 2019/10/08 19:19:39 Cleaning up Docker data root... [Barnacle] 2019/10/08 19:19:39 Removing all containers. ... skipping 25 lines ...