This job view page is being replaced by Spyglass soon. Check out the new job view.
PRrdrgmnzs: Fix where etcd-cluster-spec is writen when etcd's BackupStore is defined -v2
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2020-07-02 06:05
Elapsed14m52s
Revision0a521ca58af03d35080bb47a0927915c832455e1
Refs 9474
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/3a02c301-277f-4060-9bee-ae99d6ba467f/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/3a02c301-277f-4060-9bee-ae99d6ba467f/targets/test

No Test Failures!


Error lines from build-log.txt

... skipping 532 lines ...
2020/07/02 06:19:13 process.go:155: Step '/workspace/get-kube.sh' finished in 1m31.274474924s
2020/07/02 06:19:13 process.go:153: Running: /workspace/kops get clusters e2e-cf22fceff6-ff1eb.test-cncf-aws.k8s.io

cluster not found "e2e-cf22fceff6-ff1eb.test-cncf-aws.k8s.io"
2020/07/02 06:19:15 process.go:155: Step '/workspace/kops get clusters e2e-cf22fceff6-ff1eb.test-cncf-aws.k8s.io' finished in 1.242941018s
2020/07/02 06:19:15 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2020/07/02 06:19:15 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/02 06:19:15 util.go:68: curl https://ip.jsb.workers.dev
2020/07/02 06:19:15 kops.go:430: Using external IP for admin access: 35.223.21.240/32
2020/07/02 06:19:15 process.go:153: Running: /workspace/kops create cluster --name e2e-cf22fceff6-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 ap-northeast-2a --master-size c5.large --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.19.0-beta.2 --admin-access 35.223.21.240/32 --cloud aws --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes
I0702 06:19:15.514356    5612 featureflag.go:156] FeatureFlag "SpecOverrideFlag"=true
I0702 06:19:15.858218    5612 create_cluster.go:1438] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
W0702 06:19:16.702603    5612 channel.go:298] unable to parse kops version "pull-d45397ebb"
... skipping 23 lines ...
I0702 06:19:27.445397    5612 keypair.go:223] Issuing new certificate: "kube-proxy"
I0702 06:19:27.448529    5612 keypair.go:223] Issuing new certificate: "kubecfg"
I0702 06:19:27.502570    5612 keypair.go:223] Issuing new certificate: "kubelet"
I0702 06:19:27.521544    5612 keypair.go:223] Issuing new certificate: "master"
I0702 06:19:28.779477    5612 executor.go:103] Tasks: 66 done / 86 total; 18 can run
I0702 06:19:31.741658    5612 executor.go:103] Tasks: 84 done / 86 total; 2 can run
W0702 06:19:33.404152    5612 executor.go:128] error running task "AutoscalingGroup/nodes.e2e-cf22fceff6-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-cf22fceff6-ff1eb.test-cncf-aws.k8s.io) for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name
	status code: 400, request id: ee605096-320a-447a-b0f4-7e2c18378b03
W0702 06:19:33.409864    5612 executor.go:128] error running task "AutoscalingGroup/master-ap-northeast-2a.masters.e2e-cf22fceff6-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-cf22fceff6-ff1eb.test-cncf-aws.k8s.io) for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name
	status code: 400, request id: 9cdfb02a-dfbe-4655-b95a-1f60e8b6848d
I0702 06:19:33.409917    5612 executor.go:143] No progress made, sleeping before retrying 2 failed task(s)
I0702 06:19:43.413508    5612 executor.go:103] Tasks: 84 done / 86 total; 2 can run
I0702 06:19:45.657391    5612 executor.go:103] Tasks: 86 done / 86 total; 0 can run
I0702 06:19:45.657437    5612 dns.go:155] Pre-creating DNS records
I0702 06:19:47.103778    5612 update_cluster.go:280] Exporting kubecfg for cluster
kops has set your kubectl context to e2e-cf22fceff6-ff1eb.test-cncf-aws.k8s.io

... skipping 8 lines ...

2020/07/02 06:19:47 process.go:155: Step '/workspace/kops create cluster --name e2e-cf22fceff6-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 ap-northeast-2a --master-size c5.large --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.19.0-beta.2 --admin-access 35.223.21.240/32 --cloud aws --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes' finished in 32.192886646s
2020/07/02 06:19:47 process.go:153: Running: /workspace/kops validate cluster e2e-cf22fceff6-ff1eb.test-cncf-aws.k8s.io --wait 15m
I0702 06:19:47.720260    5642 featureflag.go:156] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-cf22fceff6-ff1eb.test-cncf-aws.k8s.io

W0702 06:19:49.750478    5642 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-cf22fceff6-ff1eb.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W0702 06:19:59.813529    5642 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W0702 06:20:09.888080    5642 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W0702 06:20:19.982859    5642 validate_cluster.go:221] (will retry): cluster not yet healthy