This job view page is being replaced by Spyglass soon. Check out the new job view.
PRjohngmyers: WIP Remove InstanceGroup from NodeupModelContext
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2020-07-03 19:05
Elapsed16m33s
Revisiond12b4cff9fd63979cbeb40076043356f27d6e049
Refs 9294
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/a6b3b959-46fd-4ebd-8dfd-17ec78c5ede3/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/a6b3b959-46fd-4ebd-8dfd-17ec78c5ede3/targets/test

No Test Failures!


Error lines from build-log.txt

... skipping 526 lines ...
2020/07/03 19:13:19 process.go:155: Step '/workspace/get-kube.sh' finished in 37.071473822s
2020/07/03 19:13:19 process.go:153: Running: /workspace/kops get clusters e2e-ba398674d4-ff1eb.test-cncf-aws.k8s.io

cluster not found "e2e-ba398674d4-ff1eb.test-cncf-aws.k8s.io"
2020/07/03 19:13:20 process.go:155: Step '/workspace/kops get clusters e2e-ba398674d4-ff1eb.test-cncf-aws.k8s.io' finished in 722.098139ms
2020/07/03 19:13:20 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2020/07/03 19:13:20 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 19:13:20 util.go:68: curl https://ip.jsb.workers.dev
2020/07/03 19:13:20 kops.go:430: Using external IP for admin access: 104.198.67.186/32
2020/07/03 19:13:20 process.go:153: Running: /workspace/kops create cluster --name e2e-ba398674d4-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-2b --master-size c5.large --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.19.0-beta.2 --admin-access 104.198.67.186/32 --cloud aws --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes
I0703 19:13:20.482877    5906 featureflag.go:156] FeatureFlag "SpecOverrideFlag"=true
I0703 19:13:20.620467    5906 create_cluster.go:1145] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
W0703 19:13:21.251828    5906 channel.go:298] unable to parse kops version "pull-e759d7852"
... skipping 42 lines ...

2020/07/03 19:13:38 process.go:155: Step '/workspace/kops create cluster --name e2e-ba398674d4-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-2b --master-size c5.large --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.19.0-beta.2 --admin-access 104.198.67.186/32 --cloud aws --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes' finished in 18.520280251s
2020/07/03 19:13:38 process.go:153: Running: /workspace/kops validate cluster e2e-ba398674d4-ff1eb.test-cncf-aws.k8s.io --wait 15m
I0703 19:13:39.006497    5936 featureflag.go:156] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-ba398674d4-ff1eb.test-cncf-aws.k8s.io

W0703 19:13:42.026086    5936 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ba398674d4-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-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:13:52.074415    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:14:02.125601    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:14:12.177908    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:14:22.217792    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:14:32.255636    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
W0703 19:14:42.291600    5936 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ba398674d4-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-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:14:52.326174    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:15:02.365867    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:15:12.408054    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:15:22.454080    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:15:32.506700    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:15:42.543892    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:15:52.588361    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:16:02.639780    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:16:12.675321    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
W0703 19:16:22.698381    5936 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ba398674d4-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-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:16:32.729957    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:16:42.764538    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:16:52.799578    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:17:02.833695    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
W0703 19:17:12.853648    5936 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ba398674d4-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-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:17:22.888055    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:17:32.929996    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:17:42.965710    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:17:53.001979    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:18:03.046167    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:18:13.100377    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:18:23.135151    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:18:33.173432    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:18:43.218696    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:18:53.264408    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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

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

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

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

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

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

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 19:20:03.541929    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:20:13.578824    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:20:23.621512    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

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 19:20:33.663923    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Node	ip-172-20-35-5.ap-southeast-2.compute.internal	node "ip-172-20-35-5.ap-southeast-2.compute.internal" is not ready
Pod	kube-system/kube-dns-677d5df9b4-9mrtf		system-cluster-critical pod "kube-dns-677d5df9b4-9mrtf" is pending
Pod	kube-system/kube-dns-677d5df9b4-zm849		system-cluster-critical pod "kube-dns-677d5df9b4-zm849" is pending

Validation Failed
W0703 19:20:47.238621    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-677d5df9b4-9mrtf	system-cluster-critical pod "kube-dns-677d5df9b4-9mrtf" is not ready (kubedns)
Pod	kube-system/kube-dns-677d5df9b4-zm849	system-cluster-critical pod "kube-dns-677d5df9b4-zm849" is pending

Validation Failed
W0703 19:20:59.365580    5936 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes			Node	t3.medium	4	4	ap-southeast-2b

... skipping 1273 lines ...
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul  3 19:22:03.778: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "kubectl-8863" for this suite.

•
------------------------------
{"msg":"PASSED [sig-cli] Kubectl client Kubectl create quota should create a quota without scopes","total":-1,"completed":1,"skipped":0,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:116
Jul  3 19:22:04.305: INFO: Driver gluster doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 52 lines ...
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul  3 19:22:04.827: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "kubectl-4963" for this suite.

•
------------------------------
{"msg":"PASSED [sig-cli] Kubectl client Kubectl create quota should reject quota with invalid scopes","total":-1,"completed":1,"skipped":15,"failed":0}

SSS
------------------------------
[BeforeEach] [sig-auth] Metadata Concealment
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 143 lines ...
/workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/framework.go:23
  Kubectl run pod
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:1524
    should create a pod from an image when restart is Never  [Conformance]
    /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597
------------------------------
{"msg":"PASSED [sig-cli] Kubectl client Kubectl run pod should create a pod from an image when restart is Never  [Conformance]","total":-1,"completed":1,"skipped":0,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:116
Jul  3 19:22:06.680: INFO: Driver hostPathSymlink doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 21 lines ...
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [sig-storage] Projected downwardAPI
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_downwardapi.go:42
[It] should set DefaultMode on files [LinuxOnly] [NodeConformance] [Conformance]
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597
STEP: Creating a pod to test downward API volume plugin
Jul  3 19:22:03.008: INFO: Waiting up to 5m0s for pod "downwardapi-volume-9d5546c1-300e-47f1-8abf-361aa82c7125" in namespace "projected-2948" to be "Succeeded or Failed"
Jul  3 19:22:03.180: INFO: Pod "downwardapi-volume-9d5546c1-300e-47f1-8abf-361aa82c7125": Phase="Pending", Reason="", readiness=false. Elapsed: 172.502328ms
Jul  3 19:22:05.358: INFO: Pod "downwardapi-volume-9d5546c1-300e-47f1-8abf-361aa82c7125": Phase="Pending", Reason="", readiness=false. Elapsed: 2.35046874s
Jul  3 19:22:07.532: INFO: Pod "downwardapi-volume-9d5546c1-300e-47f1-8abf-361aa82c7125": Phase="Pending", Reason="", readiness=false. Elapsed: 4.523992958s
Jul  3 19:22:09.709: INFO: Pod "downwardapi-volume-9d5546c1-300e-47f1-8abf-361aa82c7125": Phase="Pending", Reason="", readiness=false. Elapsed: 6.700944622s
Jul  3 19:22:11.882: INFO: Pod "downwardapi-volume-9d5546c1-300e-47f1-8abf-361aa82c7125": Phase="Pending", Reason="", readiness=false. Elapsed: 8.874381992s
Jul  3 19:22:14.055: INFO: Pod "downwardapi-volume-9d5546c1-300e-47f1-8abf-361aa82c7125": Phase="Pending", Reason="", readiness=false. Elapsed: 11.047193996s
Jul  3 19:22:16.228: INFO: Pod "downwardapi-volume-9d5546c1-300e-47f1-8abf-361aa82c7125": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.220134632s
STEP: Saw pod success
Jul  3 19:22:16.228: INFO: Pod "downwardapi-volume-9d5546c1-300e-47f1-8abf-361aa82c7125" satisfied condition "Succeeded or Failed"
Jul  3 19:22:16.402: INFO: Trying to get logs from node ip-172-20-60-233.ap-southeast-2.compute.internal pod downwardapi-volume-9d5546c1-300e-47f1-8abf-361aa82c7125 container client-container: <nil>
STEP: delete the pod
Jul  3 19:22:16.766: INFO: Waiting for pod downwardapi-volume-9d5546c1-300e-47f1-8abf-361aa82c7125 to disappear
Jul  3 19:22:16.938: INFO: Pod downwardapi-volume-9d5546c1-300e-47f1-8abf-361aa82c7125 no longer exists
[AfterEach] [sig-storage] Projected downwardAPI
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 4 lines ...
• [SLOW TEST:15.697 seconds]
[sig-storage] Projected downwardAPI
/workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_downwardapi.go:36
  should set DefaultMode on files [LinuxOnly] [NodeConformance] [Conformance]
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597
------------------------------
{"msg":"PASSED [sig-storage] Projected downwardAPI should set DefaultMode on files [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":1,"skipped":8,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:116
Jul  3 19:22:17.475: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 5 lines ...
[sig-storage] In-tree Volumes
/workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  [Driver: local][LocalVolumeType: dir-link]
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:56
    [Testpattern: Dynamic PV (immediate binding)] topology
    /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:115
      should fail to schedule a pod which has topologies that conflict with AllowedTopologies [BeforeEach]
      /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Driver local doesn't support DynamicPV -- skipping

      /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:169
------------------------------
... skipping 28 lines ...
Jul  3 19:22:02.890: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should be consumable from pods in volume with mappings as non-root [NodeConformance] [Conformance]
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597
STEP: Creating configMap with name configmap-test-volume-map-0fb02f63-62f5-4b99-b6e0-c05cc674a864
STEP: Creating a pod to test consume configMaps
Jul  3 19:22:03.584: INFO: Waiting up to 5m0s for pod "pod-configmaps-c9223e0d-d8aa-4a5f-bbc4-f9c25b5fda83" in namespace "configmap-7061" to be "Succeeded or Failed"
Jul  3 19:22:03.758: INFO: Pod "pod-configmaps-c9223e0d-d8aa-4a5f-bbc4-f9c25b5fda83": Phase="Pending", Reason="", readiness=false. Elapsed: 173.997187ms
Jul  3 19:22:05.931: INFO: Pod "pod-configmaps-c9223e0d-d8aa-4a5f-bbc4-f9c25b5fda83": Phase="Pending", Reason="", readiness=false. Elapsed: 2.347731211s
Jul  3 19:22:08.105: INFO: Pod "pod-configmaps-c9223e0d-d8aa-4a5f-bbc4-f9c25b5fda83": Phase="Pending", Reason="", readiness=false. Elapsed: 4.521551033s
Jul  3 19:22:10.279: INFO: Pod "pod-configmaps-c9223e0d-d8aa-4a5f-bbc4-f9c25b5fda83": Phase="Pending", Reason="", readiness=false. Elapsed: 6.694851019s
Jul  3 19:22:12.452: INFO: Pod "pod-configmaps-c9223e0d-d8aa-4a5f-bbc4-f9c25b5fda83": Phase="Pending", Reason="", readiness=false. Elapsed: 8.867968348s
Jul  3 19:22:14.627: INFO: Pod "pod-configmaps-c9223e0d-d8aa-4a5f-bbc4-f9c25b5fda83": Phase="Pending", Reason="", readiness=false. Elapsed: 11.043794929s
Jul  3 19:22:16.802: INFO: Pod "pod-configmaps-c9223e0d-d8aa-4a5f-bbc4-f9c25b5fda83": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.217879787s
STEP: Saw pod success
Jul  3 19:22:16.802: INFO: Pod "pod-configmaps-c9223e0d-d8aa-4a5f-bbc4-f9c25b5fda83" satisfied condition "Succeeded or Failed"
Jul  3 19:22:16.975: INFO: Trying to get logs from node ip-172-20-60-233.ap-southeast-2.compute.internal pod pod-configmaps-c9223e0d-d8aa-4a5f-bbc4-f9c25b5fda83 container configmap-volume-test: <nil>
STEP: delete the pod
Jul  3 19:22:17.329: INFO: Waiting for pod pod-configmaps-c9223e0d-d8aa-4a5f-bbc4-f9c25b5fda83 to disappear
Jul  3 19:22:17.502: INFO: Pod pod-configmaps-c9223e0d-d8aa-4a5f-bbc4-f9c25b5fda83 no longer exists
[AfterEach] [sig-storage] ConfigMap
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 4 lines ...
• [SLOW TEST:16.257 seconds]
[sig-storage] ConfigMap
/workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/configmap_volume.go:36
  should be consumable from pods in volume with mappings as non-root [NodeConformance] [Conformance]
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597
------------------------------
{"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume with mappings as non-root [NodeConformance] [Conformance]","total":-1,"completed":1,"skipped":2,"failed":0}

SSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:116
Jul  3 19:22:18.046: INFO: Driver local doesn't support ext4 -- skipping
... skipping 49 lines ...
STEP: Building a namespace api object, basename configmap
STEP: Waiting for a default service account to be provisioned in namespace
[It] should be consumable from pods in volume as non-root with FSGroup [LinuxOnly] [NodeFeature:FSGroup]
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/configmap_volume.go:75
STEP: Creating configMap with name configmap-test-volume-53cab284-f469-4a85-83ad-5796959304fb
STEP: Creating a pod to test consume configMaps
Jul  3 19:22:07.844: INFO: Waiting up to 5m0s for pod "pod-configmaps-37e30a83-5f44-40b8-a437-d7954637d873" in namespace "configmap-3556" to be "Succeeded or Failed"
Jul  3 19:22:08.020: INFO: Pod "pod-configmaps-37e30a83-5f44-40b8-a437-d7954637d873": Phase="Pending", Reason="", readiness=false. Elapsed: 175.350587ms
Jul  3 19:22:10.195: INFO: Pod "pod-configmaps-37e30a83-5f44-40b8-a437-d7954637d873": Phase="Pending", Reason="", readiness=false. Elapsed: 2.350435687s
Jul  3 19:22:12.368: INFO: Pod "pod-configmaps-37e30a83-5f44-40b8-a437-d7954637d873": Phase="Pending", Reason="", readiness=false. Elapsed: 4.523300683s
Jul  3 19:22:14.542: INFO: Pod "pod-configmaps-37e30a83-5f44-40b8-a437-d7954637d873": Phase="Pending", Reason="", readiness=false. Elapsed: 6.697209361s
Jul  3 19:22:16.715: INFO: Pod "pod-configmaps-37e30a83-5f44-40b8-a437-d7954637d873": Phase="Pending", Reason="", readiness=false. Elapsed: 8.870830906s
Jul  3 19:22:18.889: INFO: Pod "pod-configmaps-37e30a83-5f44-40b8-a437-d7954637d873": Phase="Pending", Reason="", readiness=false. Elapsed: 11.044200954s
Jul  3 19:22:21.064: INFO: Pod "pod-configmaps-37e30a83-5f44-40b8-a437-d7954637d873": Phase="Pending", Reason="", readiness=false. Elapsed: 13.218894383s
Jul  3 19:22:23.237: INFO: Pod "pod-configmaps-37e30a83-5f44-40b8-a437-d7954637d873": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.391872903s
STEP: Saw pod success
Jul  3 19:22:23.237: INFO: Pod "pod-configmaps-37e30a83-5f44-40b8-a437-d7954637d873" satisfied condition "Succeeded or Failed"
Jul  3 19:22:23.409: INFO: Trying to get logs from node ip-172-20-53-142.ap-southeast-2.compute.internal pod pod-configmaps-37e30a83-5f44-40b8-a437-d7954637d873 container configmap-volume-test: <nil>
STEP: delete the pod
Jul  3 19:22:23.787: INFO: Waiting for pod pod-configmaps-37e30a83-5f44-40b8-a437-d7954637d873 to disappear
Jul  3 19:22:23.963: INFO: Pod pod-configmaps-37e30a83-5f44-40b8-a437-d7954637d873 no longer exists
[AfterEach] [sig-storage] ConfigMap
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 14 lines ...
STEP: Building a namespace api object, basename downward-api
Jul  3 19:22:02.838: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should provide pod UID as env vars [NodeConformance] [Conformance]
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597
STEP: Creating a pod to test downward api env vars
Jul  3 19:22:03.363: INFO: Waiting up to 5m0s for pod "downward-api-be157980-e78b-48e5-9477-798da3a41ffb" in namespace "downward-api-2305" to be "Succeeded or Failed"
Jul  3 19:22:03.538: INFO: Pod "downward-api-be157980-e78b-48e5-9477-798da3a41ffb": Phase="Pending", Reason="", readiness=false. Elapsed: 175.068358ms
Jul  3 19:22:05.711: INFO: Pod "downward-api-be157980-e78b-48e5-9477-798da3a41ffb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.348316777s
Jul  3 19:22:07.885: INFO: Pod "downward-api-be157980-e78b-48e5-9477-798da3a41ffb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.522433867s
Jul  3 19:22:10.061: INFO: Pod "downward-api-be157980-e78b-48e5-9477-798da3a41ffb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.698705709s
Jul  3 19:22:12.235: INFO: Pod "downward-api-be157980-e78b-48e5-9477-798da3a41ffb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.872520894s
Jul  3 19:22:14.410: INFO: Pod "downward-api-be157980-e78b-48e5-9477-798da3a41ffb": Phase="Pending", Reason="", readiness=false. Elapsed: 11.047234903s
Jul  3 19:22:16.588: INFO: Pod "downward-api-be157980-e78b-48e5-9477-798da3a41ffb": Phase="Pending", Reason="", readiness=false. Elapsed: 13.225621379s
Jul  3 19:22:18.769: INFO: Pod "downward-api-be157980-e78b-48e5-9477-798da3a41ffb": Phase="Pending", Reason="", readiness=false. Elapsed: 15.406779008s
Jul  3 19:22:20.943: INFO: Pod "downward-api-be157980-e78b-48e5-9477-798da3a41ffb": Phase="Pending", Reason="", readiness=false. Elapsed: 17.580274439s
Jul  3 19:22:23.123: INFO: Pod "downward-api-be157980-e78b-48e5-9477-798da3a41ffb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.760800956s
STEP: Saw pod success
Jul  3 19:22:23.123: INFO: Pod "downward-api-be157980-e78b-48e5-9477-798da3a41ffb" satisfied condition "Succeeded or Failed"
Jul  3 19:22:23.296: INFO: Trying to get logs from node ip-172-20-35-5.ap-southeast-2.compute.internal pod downward-api-be157980-e78b-48e5-9477-798da3a41ffb container dapi-container: <nil>
STEP: delete the pod
Jul  3 19:22:23.665: INFO: Waiting for pod downward-api-be157980-e78b-48e5-9477-798da3a41ffb to disappear
Jul  3 19:22:23.839: INFO: Pod downward-api-be157980-e78b-48e5-9477-798da3a41ffb no longer exists
[AfterEach] [sig-node] Downward API
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 4 lines ...
• [SLOW TEST:22.596 seconds]
[sig-node] Downward API
/workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/downward_api.go:34
  should provide pod UID as env vars [NodeConformance] [Conformance]
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597
------------------------------
{"msg":"PASSED [sig-node] Downward API should provide pod UID as env vars [NodeConformance] [Conformance]","total":-1,"completed":1,"skipped":6,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:116
Jul  3 19:22:24.368: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
... skipping 61 lines ...
• [SLOW TEST:7.471 seconds]
[sig-storage] Downward API volume
/workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/downwardapi_volume.go:37
  should update annotations on modification [NodeConformance] [Conformance]
  /workspace/anago-v1.19.0-beta.1.269+e7ca64fbe16d0c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597
------------------------------
{"msg":"PASSED [sig-storage] Downward API volume should update annotations on modification [NodeConformance] [Conformance]","total":-1,"completed":2,"skipped":17,"failed":0}

SSSSS