This job view page is being replaced by Spyglass soon. Check out the new job view.
PRjohngmyers: Default ClusterDNS appropriately when NodeLocalDNS is enabled
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2020-07-03 23:50
Elapsed7m27s
Revision30acb4abd17cce54d9c52361598d63f882fc21b5
Refs 9491
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/cbe27fe7-e11d-4b65-895c-d40c7bf132b1/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/cbe27fe7-e11d-4b65-895c-d40c7bf132b1/targets/test

No Test Failures!


Error lines from build-log.txt

... skipping 514 lines ...
2020/07/03 23:55:10 process.go:155: Step '/workspace/get-kube.sh' finished in 19.466848123s
2020/07/03 23:55:10 process.go:153: Running: /workspace/kops get clusters e2e-4fbac0be52-ff1eb.test-cncf-aws.k8s.io

cluster not found "e2e-4fbac0be52-ff1eb.test-cncf-aws.k8s.io"
2020/07/03 23:55:11 process.go:155: Step '/workspace/kops get clusters e2e-4fbac0be52-ff1eb.test-cncf-aws.k8s.io' finished in 557.931185ms
2020/07/03 23:55:11 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2020/07/03 23:55:11 kops.go:505: 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/07/03 23:55:11 util.go:68: curl https://ip.jsb.workers.dev
2020/07/03 23:55:11 kops.go:430: Using external IP for admin access: 35.192.125.221/32
2020/07/03 23:55:11 process.go:153: Running: /workspace/kops create cluster --name e2e-4fbac0be52-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-west-2c --master-size c5.large --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.19.0-beta.2 --admin-access 35.192.125.221/32 --cloud aws --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes
I0703 23:55:11.412394    5705 featureflag.go:156] FeatureFlag "SpecOverrideFlag"=true
I0703 23:55:11.479740    5705 create_cluster.go:1145] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
W0703 23:55:11.985477    5705 channel.go:298] unable to parse kops version "pull-95e490c2d"
... skipping 23 lines ...
I0703 23:55:18.232664    5705 keypair.go:223] Issuing new certificate: "master"
I0703 23:55:18.237470    5705 keypair.go:223] Issuing new certificate: "kubecfg"
I0703 23:55:18.260089    5705 keypair.go:223] Issuing new certificate: "kubelet"
I0703 23:55:18.281264    5705 keypair.go:223] Issuing new certificate: "kube-proxy"
I0703 23:55:19.331267    5705 executor.go:103] Tasks: 66 done / 86 total; 18 can run
I0703 23:55:21.635380    5705 executor.go:103] Tasks: 84 done / 86 total; 2 can run
W0703 23:55:22.922383    5705 executor.go:128] error running task "AutoscalingGroup/master-eu-west-2c.masters.e2e-4fbac0be52-ff1eb.test-cncf-aws.k8s.io" (9m58s remaining to succeed): error creating AutoscalingGroup: ValidationError: You must use a valid fully-formed launch template. Value (masters.e2e-4fbac0be52-ff1eb.test-cncf-aws.k8s.io) for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name
	status code: 400, request id: 6c25733a-866a-4b78-98b9-88f4f76df66b
W0703 23:55:22.922423    5705 executor.go:128] error running task "AutoscalingGroup/nodes.e2e-4fbac0be52-ff1eb.test-cncf-aws.k8s.io" (9m58s remaining to succeed): error creating AutoscalingGroup: ValidationError: You must use a valid fully-formed launch template. Value (nodes.e2e-4fbac0be52-ff1eb.test-cncf-aws.k8s.io) for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name
	status code: 400, request id: f46ffd32-212a-4c96-b400-b7fc9491f21e
I0703 23:55:22.922432    5705 executor.go:143] No progress made, sleeping before retrying 2 failed task(s)
I0703 23:55:32.922678    5705 executor.go:103] Tasks: 84 done / 86 total; 2 can run
I0703 23:55:34.749446    5705 executor.go:103] Tasks: 86 done / 86 total; 0 can run
I0703 23:55:34.749496    5705 dns.go:155] Pre-creating DNS records
I0703 23:55:35.611999    5705 update_cluster.go:280] Exporting kubecfg for cluster
kops has set your kubectl context to e2e-4fbac0be52-ff1eb.test-cncf-aws.k8s.io

... skipping 8 lines ...

2020/07/03 23:55:35 process.go:155: Step '/workspace/kops create cluster --name e2e-4fbac0be52-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-west-2c --master-size c5.large --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.19.0-beta.2 --admin-access 35.192.125.221/32 --cloud aws --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes' finished in 24.461682862s
2020/07/03 23:55:35 process.go:153: Running: /workspace/kops validate cluster e2e-4fbac0be52-ff1eb.test-cncf-aws.k8s.io --wait 15m
I0703 23:55:35.864655    5735 featureflag.go:156] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-4fbac0be52-ff1eb.test-cncf-aws.k8s.io

W0703 23:55:37.107444    5735 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-4fbac0be52-ff1eb.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0703 23:55:47.169788    5735 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-4fbac0be52-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-west-2c	Master	c5.large	1	1	eu-west-2c
nodes			Node	t3.medium	4	4	eu-west-2c

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
W0703 23:55:57.211356    5735 validate_cluster.go:221] (will retry): cluster not yet healthy
W0703 23:56:07.235044    5735 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-4fbac0be52-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-west-2c	Master	c5.large	1	1	eu-west-2c
nodes			Node	t3.medium	4	4	eu-west-2c

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
W0703 23:56:17.280096    5735 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2c	Master	c5.large	1	1	eu-west-2c
nodes			Node	t3.medium	4	4	eu-west-2c

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
W0703 23:56:27.316659    5735 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2c	Master	c5.large	1	1	eu-west-2c
nodes			Node	t3.medium	4	4	eu-west-2c

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
W0703 23:56:37.353326    5735 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2c	Master	c5.large	1	1	eu-west-2c
nodes			Node	t3.medium	4	4	eu-west-2c

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
W0703 23:56:47.390905    5735 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2c	Master	c5.large	1	1	eu-west-2c
nodes			Node	t3.medium	4	4	eu-west-2c

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
W0703 23:56:57.437882    5735 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2c	Master	c5.large	1	1	eu-west-2c
nodes			Node	t3.medium	4	4	eu-west-2c

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
W0703 23:57:07.469208    5735 validate_cluster.go:221] (will retry): cluster not yet healthy
W0703 23:57:17.498014    5735 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-4fbac0be52-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-west-2c	Master	c5.large	1	1	eu-west-2c
nodes			Node	t3.medium	4	4	eu-west-2c

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
W0703 23:57:27.528740    5735 validate_cluster.go:221] (will retry): cluster not yet healthy
{"component":"entrypoint","file":"prow/entrypoint/run.go:168","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Entrypoint received interrupt: terminated","severity":"error","time":"2020-07-03T23:57:28Z"}