This job view page is being replaced by Spyglass soon. Check out the new job view.
PRchristianjoun: WIP: Implemented API loadbalancer class, allowing NLB and ELB support on AWS.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2020-09-19 17:23
Elapsed6m49s
Revisionade484777e8046417b5b5bf943fed1602ea588dd
Refs 9011

No Test Failures!


Error lines from build-log.txt

... skipping 624 lines ...
2020/09/19 17:27:55 process.go:155: Step '/workspace/get-kube.sh' finished in 25.319968866s
2020/09/19 17:27:55 process.go:153: Running: /workspace/kops get clusters e2e-a3c9821d38-ff1eb.test-cncf-aws.k8s.io

cluster not found "e2e-a3c9821d38-ff1eb.test-cncf-aws.k8s.io"
2020/09/19 17:27:56 process.go:155: Step '/workspace/kops get clusters e2e-a3c9821d38-ff1eb.test-cncf-aws.k8s.io' finished in 1.090751038s
2020/09/19 17:27:56 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2020/09/19 17:27:56 kops.go:514: failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404
2020/09/19 17:27:56 util.go:68: curl https://ip.jsb.workers.dev
2020/09/19 17:27:56 kops.go:439: Using external IP for admin access: 35.239.212.76/32
2020/09/19 17:27:56 process.go:153: Running: /workspace/kops create cluster --name e2e-a3c9821d38-ff1eb.test-cncf-aws.k8s.io --ssh-public-key /workspace/.ssh/kube_aws_rsa.pub --node-count 4 --node-volume-size 48 --master-volume-size 48 --master-count 1 --zones eu-central-1b --master-size c5.large --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.19.3-rc.0 --admin-access 35.239.212.76/32 --cloud aws --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes
I0919 17:27:56.490591    6548 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0919 17:27:56.627772    6548 create_cluster.go:721] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
W0919 17:27:57.334906    6548 channel.go:298] unable to parse kops version "pull-88e4094d8a"
... skipping 34 lines ...

2020/09/19 17:28:22 process.go:155: Step '/workspace/kops create cluster --name e2e-a3c9821d38-ff1eb.test-cncf-aws.k8s.io --ssh-public-key /workspace/.ssh/kube_aws_rsa.pub --node-count 4 --node-volume-size 48 --master-volume-size 48 --master-count 1 --zones eu-central-1b --master-size c5.large --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.19.3-rc.0 --admin-access 35.239.212.76/32 --cloud aws --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes' finished in 26.38525778s
2020/09/19 17:28:22 process.go:153: Running: /workspace/kops validate cluster e2e-a3c9821d38-ff1eb.test-cncf-aws.k8s.io --wait 15m
I0919 17:28:22.857801    6569 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-a3c9821d38-ff1eb.test-cncf-aws.k8s.io

W0919 17:28:24.317445    6569 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-a3c9821d38-ff1eb.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0919 17:28:34.369201    6569 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-a3c9821d38-ff1eb.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0919 17:28:44.434927    6569 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-a3c9821d38-ff1eb.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0919 17:28:54.481424    6569 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0919 17:29:04.526276    6569 validate_cluster.go:221] (will retry): cluster not yet healthy
W0919 17:29:14.557577    6569 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-a3c9821d38-ff1eb.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0919 17:29:24.594564    6569 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0919 17:29:34.682389    6569 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0919 17:29:44.726117    6569 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0919 17:29:54.770817    6569 validate_cluster.go:221] (will retry): cluster not yet healthy
{"component":"entrypoint","file":"prow/entrypoint/run.go:169","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Entrypoint received interrupt: terminated","severity":"error","time":"2020-09-19T17:30:02Z"}