This job view page is being replaced by Spyglass soon. Check out the new job view.
PRchristus02: Updating the YAMLs for Ingress-Citrix Addon
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2020-07-04 07:03
Elapsed5m6s
Revision648500e4e329cd63c7941607034e532f3aeb1131
Refs 9480
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/1b55ff79-ea6d-43fb-bd24-ee2f5d090b0f/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/1b55ff79-ea6d-43fb-bd24-ee2f5d090b0f/targets/test

No Test Failures!


Error lines from build-log.txt

... skipping 508 lines ...
2020/07/04 07:07:07 process.go:155: Step '/workspace/get-kube.sh' finished in 13.344755131s
2020/07/04 07:07:07 process.go:153: Running: /workspace/kops get clusters e2e-fa814f9881-ff1eb.test-cncf-aws.k8s.io

cluster not found "e2e-fa814f9881-ff1eb.test-cncf-aws.k8s.io"
2020/07/04 07:07:07 process.go:155: Step '/workspace/kops get clusters e2e-fa814f9881-ff1eb.test-cncf-aws.k8s.io' finished in 526.996205ms
2020/07/04 07:07:07 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2020/07/04 07:07:07 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/04 07:07:07 util.go:68: curl https://ip.jsb.workers.dev
2020/07/04 07:07:07 kops.go:430: Using external IP for admin access: 35.226.122.251/32
2020/07/04 07:07:07 process.go:153: Running: /workspace/kops create cluster --name e2e-fa814f9881-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-southeast-2a --master-size c5.large --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.19.0-beta.2 --admin-access 35.226.122.251/32 --cloud aws --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes
I0704 07:07:07.697804    5359 featureflag.go:156] FeatureFlag "SpecOverrideFlag"=true
I0704 07:07:07.733631    5359 create_cluster.go:1145] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
W0704 07:07:08.231479    5359 channel.go:298] unable to parse kops version "pull-bf169a8a7"
... skipping 23 lines ...
I0704 07:07:16.320104    5359 keypair.go:223] Issuing new certificate: "kube-proxy"
I0704 07:07:16.321807    5359 keypair.go:223] Issuing new certificate: "kubelet"
I0704 07:07:16.328549    5359 keypair.go:223] Issuing new certificate: "master"
I0704 07:07:16.333346    5359 keypair.go:223] Issuing new certificate: "kubecfg"
I0704 07:07:17.823814    5359 executor.go:103] Tasks: 66 done / 86 total; 18 can run
I0704 07:07:20.102952    5359 executor.go:103] Tasks: 84 done / 86 total; 2 can run
W0704 07:07:21.897737    5359 executor.go:128] error running task "AutoscalingGroup/nodes.e2e-fa814f9881-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-fa814f9881-ff1eb.test-cncf-aws.k8s.io) for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name
	status code: 400, request id: dc4acc03-bc2d-4174-9bce-b9638ff87f97
W0704 07:07:21.897775    5359 executor.go:128] error running task "AutoscalingGroup/master-ap-southeast-2a.masters.e2e-fa814f9881-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-fa814f9881-ff1eb.test-cncf-aws.k8s.io) for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name
	status code: 400, request id: b5e52d3a-94b8-4f23-a954-83d0785117ad
I0704 07:07:21.897786    5359 executor.go:143] No progress made, sleeping before retrying 2 failed task(s)
I0704 07:07:31.898026    5359 executor.go:103] Tasks: 84 done / 86 total; 2 can run
I0704 07:07:34.315967    5359 executor.go:103] Tasks: 86 done / 86 total; 0 can run
I0704 07:07:34.316026    5359 dns.go:155] Pre-creating DNS records
I0704 07:07:35.231484    5359 update_cluster.go:280] Exporting kubecfg for cluster
kops has set your kubectl context to e2e-fa814f9881-ff1eb.test-cncf-aws.k8s.io

... skipping 8 lines ...

2020/07/04 07:07:35 process.go:155: Step '/workspace/kops create cluster --name e2e-fa814f9881-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-southeast-2a --master-size c5.large --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.19.0-beta.2 --admin-access 35.226.122.251/32 --cloud aws --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes' finished in 27.771789219s
2020/07/04 07:07:35 process.go:153: Running: /workspace/kops validate cluster e2e-fa814f9881-ff1eb.test-cncf-aws.k8s.io --wait 15m
I0704 07:07:35.471223    5390 featureflag.go:156] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-fa814f9881-ff1eb.test-cncf-aws.k8s.io

W0704 07:07:36.954071    5390 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-fa814f9881-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-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes			Node	t3.medium	4	4	ap-southeast-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
W0704 07:07:46.992125    5390 validate_cluster.go:221] (will retry): cluster not yet healthy
W0704 07:07:57.023956    5390 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-fa814f9881-ff1eb.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0704 07:08:07.069853    5390 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-fa814f9881-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-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes			Node	t3.medium	4	4	ap-southeast-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
W0704 07:08:17.100348    5390 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes			Node	t3.medium	4	4	ap-southeast-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
W0704 07:08:27.145710    5390 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-04T07:08:28Z"}