This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-10-01 08:36
Elapsed34m33s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 132 lines ...
I1001 08:37:39.304944    4720 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I1001 08:37:39.306604    4720 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.23.0-alpha.2+v1.23.0-alpha.1-308-g7ecc132461/linux/amd64/kops
I1001 08:37:40.516052    4720 up.go:43] Cleaning up any leaked resources from previous cluster
I1001 08:37:40.516087    4720 dumplogs.go:40] /logs/artifacts/96abbf9a-2292-11ec-ab3b-42a255cc6876/kops toolbox dump --name e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1001 08:37:40.556110    4739 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1001 08:37:40.556242    4739 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-3e65cd3106-93705.test-cncf-aws.k8s.io" not found
W1001 08:37:41.118814    4720 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1001 08:37:41.118865    4720 down.go:48] /logs/artifacts/96abbf9a-2292-11ec-ab3b-42a255cc6876/kops delete cluster --name e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --yes
I1001 08:37:41.140180    4749 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1001 08:37:41.140301    4749 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-3e65cd3106-93705.test-cncf-aws.k8s.io" not found
I1001 08:37:41.689107    4720 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/01 08:37:41 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
I1001 08:37:41.702762    4720 http.go:37] curl https://ip.jsb.workers.dev
I1001 08:37:41.824643    4720 up.go:144] /logs/artifacts/96abbf9a-2292-11ec-ab3b-42a255cc6876/kops create cluster --name e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.20.11 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=amazon/amzn2-ami-kernel-5.10-hvm-2.0.20210813.1-x86_64-gp2 --channel=alpha --networking=flannel --container-runtime=containerd --admin-access 34.123.251.80/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-1a --master-size c5.large
I1001 08:37:41.865496    4759 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1001 08:37:41.865653    4759 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1001 08:37:41.915194    4759 create_cluster.go:838] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I1001 08:37:42.581586    4759 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 42 lines ...

I1001 08:38:12.822624    4720 up.go:181] /logs/artifacts/96abbf9a-2292-11ec-ab3b-42a255cc6876/kops validate cluster --name e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I1001 08:38:12.859913    4779 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1001 08:38:12.860016    4779 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-3e65cd3106-93705.test-cncf-aws.k8s.io

W1001 08:38:14.347890    4779 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-3e65cd3106-93705.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-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:38:24.393581    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:38:34.448452    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:38:44.490300    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:38:54.533976    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:39:04.576244    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:39:14.622969    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:39:24.669914    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:39:34.712130    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:39:44.755304    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:39:54.799301    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:40:04.840848    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:40:14.883264    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:40:24.914920    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:40:34.973467    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
W1001 08:40:45.004216    4779 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-3e65cd3106-93705.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-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:40:55.060724    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:41:05.100758    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:41:15.135243    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:41:25.174750    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:41:35.215653    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:41:45.262764    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:41:55.303596    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:42:05.336604    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:42:15.371294    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:42:25.406324    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

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
W1001 08:42:35.439382    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
Machine	i-02ad688f57412ef93					machine "i-02ad688f57412ef93" has not yet joined cluster
Machine	i-0f2d0ebcc75c00614					machine "i-0f2d0ebcc75c00614" has not yet joined cluster
Node	ip-172-20-33-232.ap-northeast-1.compute.internal	master "ip-172-20-33-232.ap-northeast-1.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-64497985bd-8lbd5			system-cluster-critical pod "coredns-64497985bd-8lbd5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-hvgvq		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-hvgvq" is pending

Validation Failed
W1001 08:42:48.984388    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 14 lines ...
Pod	kube-system/coredns-autoscaler-84d4cfd89c-hvgvq		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-hvgvq" is pending
Pod	kube-system/kube-flannel-ds-5sk5f			system-node-critical pod "kube-flannel-ds-5sk5f" is pending
Pod	kube-system/kube-flannel-ds-b248w			system-node-critical pod "kube-flannel-ds-b248w" is pending
Pod	kube-system/kube-flannel-ds-bjskt			system-node-critical pod "kube-flannel-ds-bjskt" is pending
Pod	kube-system/kube-flannel-ds-ws6td			system-node-critical pod "kube-flannel-ds-ws6td" is pending

Validation Failed
W1001 08:43:01.466898    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 6 lines ...
ip-172-20-60-245.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-64497985bd-g9tx2	system-cluster-critical pod "coredns-64497985bd-g9tx2" is not ready (coredns)

Validation Failed
W1001 08:43:13.807475    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 21 lines ...
ip-172-20-60-245.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-proxy-ip-172-20-41-255.ap-northeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-41-255.ap-northeast-1.compute.internal" is pending

Validation Failed
W1001 08:43:38.995029    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 22 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-proxy-ip-172-20-35-235.ap-northeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-35-235.ap-northeast-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-60-245.ap-northeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-60-245.ap-northeast-1.compute.internal" is pending

Validation Failed
W1001 08:44:03.616280    4779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 581 lines ...
[sig-storage] In-tree Volumes
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  [Driver: gcepd]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Dynamic PV (delayed binding)] topology
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should fail to schedule a pod which has topologies that conflict with AllowedTopologies [BeforeEach]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Only supported for providers [gce gke] (not aws)

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/drivers/in_tree.go:1304
------------------------------
... skipping 402 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:46:35.908: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "node-lease-test-9619" for this suite.

•
------------------------------
{"msg":"PASSED [k8s.io] NodeLease when the NodeLease feature is enabled should have OwnerReferences set","total":-1,"completed":1,"skipped":1,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ntfs)][sig-windows] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:46:36.209: INFO: Only supported for providers [openstack] (not aws)
... skipping 31 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:46:37.300: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "lease-test-8524" for this suite.

•
------------------------------
{"msg":"PASSED [k8s.io] Lease lease API should be available [Conformance]","total":-1,"completed":1,"skipped":4,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:46:37.737: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 36 lines ...
STEP: Destroying namespace "services-8556" for this suite.
[AfterEach] [sig-network] Services
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:749

•
------------------------------
{"msg":"PASSED [sig-network] Services should prevent NodePort collisions","total":-1,"completed":2,"skipped":8,"failed":0}

SS
------------------------------
[BeforeEach] [sig-apps] DisruptionController
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 17 lines ...
• [SLOW TEST:5.308 seconds]
[sig-apps] DisruptionController
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23
  evictions: too few pods, absolute => should not allow an eviction
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/disruption.go:222
------------------------------
{"msg":"PASSED [sig-apps] DisruptionController evictions: too few pods, absolute =\u003e should not allow an eviction","total":-1,"completed":1,"skipped":2,"failed":0}
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:46:39.956: INFO: Driver supports dynamic provisioning, skipping InlineVolume pattern
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 111 lines ...
Oct  1 08:46:35.322: INFO: No PSP annotation exists on dry run pod; assuming PodSecurityPolicy is disabled
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [k8s.io] Security Context
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/security_context.go:41
[It] should run the container with readonly rootfs when readOnlyRootFilesystem=true [LinuxOnly] [NodeConformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/security_context.go:212
Oct  1 08:46:35.724: INFO: Waiting up to 5m0s for pod "busybox-readonly-true-e1f54743-6148-4d7f-be8a-298073136365" in namespace "security-context-test-7093" to be "Succeeded or Failed"
Oct  1 08:46:35.858: INFO: Pod "busybox-readonly-true-e1f54743-6148-4d7f-be8a-298073136365": Phase="Pending", Reason="", readiness=false. Elapsed: 133.701624ms
Oct  1 08:46:37.992: INFO: Pod "busybox-readonly-true-e1f54743-6148-4d7f-be8a-298073136365": Phase="Pending", Reason="", readiness=false. Elapsed: 2.267919866s
Oct  1 08:46:40.129: INFO: Pod "busybox-readonly-true-e1f54743-6148-4d7f-be8a-298073136365": Phase="Pending", Reason="", readiness=false. Elapsed: 4.404661671s
Oct  1 08:46:42.263: INFO: Pod "busybox-readonly-true-e1f54743-6148-4d7f-be8a-298073136365": Phase="Failed", Reason="", readiness=false. Elapsed: 6.538820938s
Oct  1 08:46:42.263: INFO: Pod "busybox-readonly-true-e1f54743-6148-4d7f-be8a-298073136365" satisfied condition "Succeeded or Failed"
[AfterEach] [k8s.io] Security Context
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:46:42.263: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "security-context-test-7093" for this suite.


... skipping 2 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  When creating a pod with readOnlyRootFilesystem
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/security_context.go:166
    should run the container with readonly rootfs when readOnlyRootFilesystem=true [LinuxOnly] [NodeConformance]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/security_context.go:212
------------------------------
{"msg":"PASSED [k8s.io] Security Context When creating a pod with readOnlyRootFilesystem should run the container with readonly rootfs when readOnlyRootFilesystem=true [LinuxOnly] [NodeConformance]","total":-1,"completed":1,"skipped":1,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:46:42.696: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 25 lines ...
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [sig-storage] Projected downwardAPI
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_downwardapi.go:41
[It] should provide container's memory limit [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating a pod to test downward API volume plugin
Oct  1 08:46:35.675: INFO: Waiting up to 5m0s for pod "downwardapi-volume-b4a178e1-d7ea-48a9-8c19-06f1ffb5674c" in namespace "projected-2449" to be "Succeeded or Failed"
Oct  1 08:46:35.806: INFO: Pod "downwardapi-volume-b4a178e1-d7ea-48a9-8c19-06f1ffb5674c": Phase="Pending", Reason="", readiness=false. Elapsed: 131.391832ms
Oct  1 08:46:37.951: INFO: Pod "downwardapi-volume-b4a178e1-d7ea-48a9-8c19-06f1ffb5674c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.275906044s
Oct  1 08:46:40.084: INFO: Pod "downwardapi-volume-b4a178e1-d7ea-48a9-8c19-06f1ffb5674c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.409412049s
Oct  1 08:46:42.218: INFO: Pod "downwardapi-volume-b4a178e1-d7ea-48a9-8c19-06f1ffb5674c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.542831109s
STEP: Saw pod success
Oct  1 08:46:42.218: INFO: Pod "downwardapi-volume-b4a178e1-d7ea-48a9-8c19-06f1ffb5674c" satisfied condition "Succeeded or Failed"
Oct  1 08:46:42.349: INFO: Trying to get logs from node ip-172-20-35-235.ap-northeast-1.compute.internal pod downwardapi-volume-b4a178e1-d7ea-48a9-8c19-06f1ffb5674c container client-container: <nil>
STEP: delete the pod
Oct  1 08:46:42.635: INFO: Waiting for pod downwardapi-volume-b4a178e1-d7ea-48a9-8c19-06f1ffb5674c to disappear
Oct  1 08:46:42.768: INFO: Pod downwardapi-volume-b4a178e1-d7ea-48a9-8c19-06f1ffb5674c no longer exists
[AfterEach] [sig-storage] Projected downwardAPI
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 4 lines ...
• [SLOW TEST:8.574 seconds]
[sig-storage] Projected downwardAPI
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_downwardapi.go:35
  should provide container's memory limit [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-storage] Projected downwardAPI should provide container's memory limit [NodeConformance] [Conformance]","total":-1,"completed":1,"skipped":4,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:46:43.188: INFO: Only supported for node OS distro [gci ubuntu custom] (not debian)
... skipping 25 lines ...
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [sig-storage] HostPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/host_path.go:37
[It] should support subPath [NodeConformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/host_path.go:93
STEP: Creating a pod to test hostPath subPath
Oct  1 08:46:35.666: INFO: Waiting up to 5m0s for pod "pod-host-path-test" in namespace "hostpath-4130" to be "Succeeded or Failed"
Oct  1 08:46:35.800: INFO: Pod "pod-host-path-test": Phase="Pending", Reason="", readiness=false. Elapsed: 134.201532ms
Oct  1 08:46:37.951: INFO: Pod "pod-host-path-test": Phase="Pending", Reason="", readiness=false. Elapsed: 2.28485694s
Oct  1 08:46:40.086: INFO: Pod "pod-host-path-test": Phase="Pending", Reason="", readiness=false. Elapsed: 4.419701028s
Oct  1 08:46:42.222: INFO: Pod "pod-host-path-test": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.556014056s
STEP: Saw pod success
Oct  1 08:46:42.222: INFO: Pod "pod-host-path-test" satisfied condition "Succeeded or Failed"
Oct  1 08:46:42.359: INFO: Trying to get logs from node ip-172-20-60-245.ap-northeast-1.compute.internal pod pod-host-path-test container test-container-2: <nil>
STEP: delete the pod
Oct  1 08:46:43.184: INFO: Waiting for pod pod-host-path-test to disappear
Oct  1 08:46:43.319: INFO: Pod pod-host-path-test no longer exists
[AfterEach] [sig-storage] HostPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 70 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/framework.go:23
  Kubectl label
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:1312
    should update the label on a resource  [Conformance]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-cli] Kubectl client Kubectl label should update the label on a resource  [Conformance]","total":-1,"completed":1,"skipped":6,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:46:43.759: INFO: Driver local doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 64 lines ...
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [sig-storage] Projected downwardAPI
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_downwardapi.go:41
[It] should provide podname as non-root with fsgroup and defaultMode [LinuxOnly] [NodeFeature:FSGroup]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_downwardapi.go:106
STEP: Creating a pod to test downward API volume plugin
Oct  1 08:46:37.713: INFO: Waiting up to 5m0s for pod "metadata-volume-29b74a7e-abdc-4172-a658-251b902d0d13" in namespace "projected-2272" to be "Succeeded or Failed"
Oct  1 08:46:37.848: INFO: Pod "metadata-volume-29b74a7e-abdc-4172-a658-251b902d0d13": Phase="Pending", Reason="", readiness=false. Elapsed: 135.007064ms
Oct  1 08:46:39.980: INFO: Pod "metadata-volume-29b74a7e-abdc-4172-a658-251b902d0d13": Phase="Pending", Reason="", readiness=false. Elapsed: 2.266552087s
Oct  1 08:46:42.112: INFO: Pod "metadata-volume-29b74a7e-abdc-4172-a658-251b902d0d13": Phase="Pending", Reason="", readiness=false. Elapsed: 4.39869748s
Oct  1 08:46:44.243: INFO: Pod "metadata-volume-29b74a7e-abdc-4172-a658-251b902d0d13": Phase="Pending", Reason="", readiness=false. Elapsed: 6.529626339s
Oct  1 08:46:46.374: INFO: Pod "metadata-volume-29b74a7e-abdc-4172-a658-251b902d0d13": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.660392183s
STEP: Saw pod success
Oct  1 08:46:46.374: INFO: Pod "metadata-volume-29b74a7e-abdc-4172-a658-251b902d0d13" satisfied condition "Succeeded or Failed"
Oct  1 08:46:46.505: INFO: Trying to get logs from node ip-172-20-60-245.ap-northeast-1.compute.internal pod metadata-volume-29b74a7e-abdc-4172-a658-251b902d0d13 container client-container: <nil>
STEP: delete the pod
Oct  1 08:46:46.788: INFO: Waiting for pod metadata-volume-29b74a7e-abdc-4172-a658-251b902d0d13 to disappear
Oct  1 08:46:46.918: INFO: Pod metadata-volume-29b74a7e-abdc-4172-a658-251b902d0d13 no longer exists
[AfterEach] [sig-storage] Projected downwardAPI
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 4 lines ...
• [SLOW TEST:12.556 seconds]
[sig-storage] Projected downwardAPI
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_downwardapi.go:35
  should provide podname as non-root with fsgroup and defaultMode [LinuxOnly] [NodeFeature:FSGroup]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_downwardapi.go:106
------------------------------
{"msg":"PASSED [sig-storage] Projected downwardAPI should provide podname as non-root with fsgroup and defaultMode [LinuxOnly] [NodeFeature:FSGroup]","total":-1,"completed":1,"skipped":20,"failed":0}

S
------------------------------
[BeforeEach] [sig-storage] Projected combined
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 4 lines ...
STEP: Waiting for a default service account to be provisioned in namespace
[It] should project all components that make up the projection API [Projection][NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating configMap with name configmap-projected-all-test-volume-cdb3668b-26ea-4170-9dd7-d93f9e823ea1
STEP: Creating secret with name secret-projected-all-test-volume-ab5af413-4b98-4c99-a762-0568773e0cb0
STEP: Creating a pod to test Check all projections for projected volume plugin
Oct  1 08:46:36.004: INFO: Waiting up to 5m0s for pod "projected-volume-5881f3ef-e927-46ae-87e9-1365e5597581" in namespace "projected-8481" to be "Succeeded or Failed"
Oct  1 08:46:36.146: INFO: Pod "projected-volume-5881f3ef-e927-46ae-87e9-1365e5597581": Phase="Pending", Reason="", readiness=false. Elapsed: 142.122079ms
Oct  1 08:46:38.287: INFO: Pod "projected-volume-5881f3ef-e927-46ae-87e9-1365e5597581": Phase="Pending", Reason="", readiness=false. Elapsed: 2.283510874s
Oct  1 08:46:40.422: INFO: Pod "projected-volume-5881f3ef-e927-46ae-87e9-1365e5597581": Phase="Pending", Reason="", readiness=false. Elapsed: 4.418494683s
Oct  1 08:46:42.558: INFO: Pod "projected-volume-5881f3ef-e927-46ae-87e9-1365e5597581": Phase="Pending", Reason="", readiness=false. Elapsed: 6.554487893s
Oct  1 08:46:44.693: INFO: Pod "projected-volume-5881f3ef-e927-46ae-87e9-1365e5597581": Phase="Pending", Reason="", readiness=false. Elapsed: 8.689173971s
Oct  1 08:46:46.828: INFO: Pod "projected-volume-5881f3ef-e927-46ae-87e9-1365e5597581": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.823804613s
STEP: Saw pod success
Oct  1 08:46:46.828: INFO: Pod "projected-volume-5881f3ef-e927-46ae-87e9-1365e5597581" satisfied condition "Succeeded or Failed"
Oct  1 08:46:46.963: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod projected-volume-5881f3ef-e927-46ae-87e9-1365e5597581 container projected-all-volume-test: <nil>
STEP: delete the pod
Oct  1 08:46:47.265: INFO: Waiting for pod projected-volume-5881f3ef-e927-46ae-87e9-1365e5597581 to disappear
Oct  1 08:46:47.400: INFO: Pod projected-volume-5881f3ef-e927-46ae-87e9-1365e5597581 no longer exists
[AfterEach] [sig-storage] Projected combined
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 4 lines ...
• [SLOW TEST:13.178 seconds]
[sig-storage] Projected combined
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_combined.go:32
  should project all components that make up the projection API [Projection][NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-storage] Projected combined should project all components that make up the projection API [Projection][NodeConformance] [Conformance]","total":-1,"completed":1,"skipped":2,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:46:47.819: INFO: Driver local doesn't support InlineVolume -- skipping
... skipping 73 lines ...
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [sig-storage] HostPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/host_path.go:37
[It] should support r/w [NodeConformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/host_path.go:65
STEP: Creating a pod to test hostPath r/w
Oct  1 08:46:36.063: INFO: Waiting up to 5m0s for pod "pod-host-path-test" in namespace "hostpath-3099" to be "Succeeded or Failed"
Oct  1 08:46:36.196: INFO: Pod "pod-host-path-test": Phase="Pending", Reason="", readiness=false. Elapsed: 132.985225ms
Oct  1 08:46:38.335: INFO: Pod "pod-host-path-test": Phase="Pending", Reason="", readiness=false. Elapsed: 2.271655373s
Oct  1 08:46:40.467: INFO: Pod "pod-host-path-test": Phase="Pending", Reason="", readiness=false. Elapsed: 4.403794902s
Oct  1 08:46:42.599: INFO: Pod "pod-host-path-test": Phase="Pending", Reason="", readiness=false. Elapsed: 6.535712257s
Oct  1 08:46:44.731: INFO: Pod "pod-host-path-test": Phase="Pending", Reason="", readiness=false. Elapsed: 8.667701591s
Oct  1 08:46:46.863: INFO: Pod "pod-host-path-test": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.799804117s
STEP: Saw pod success
Oct  1 08:46:46.863: INFO: Pod "pod-host-path-test" satisfied condition "Succeeded or Failed"
Oct  1 08:46:46.995: INFO: Trying to get logs from node ip-172-20-41-255.ap-northeast-1.compute.internal pod pod-host-path-test container test-container-2: <nil>
STEP: delete the pod
Oct  1 08:46:47.521: INFO: Waiting for pod pod-host-path-test to disappear
Oct  1 08:46:47.654: INFO: Pod pod-host-path-test no longer exists
[AfterEach] [sig-storage] HostPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 4 lines ...
• [SLOW TEST:13.427 seconds]
[sig-storage] HostPath
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/host_path.go:34
  should support r/w [NodeConformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/host_path.go:65
------------------------------
{"msg":"PASSED [sig-storage] HostPath should support r/w [NodeConformance]","total":-1,"completed":1,"skipped":0,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:46:48.061: INFO: Only supported for providers [openstack] (not aws)
[AfterEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 40 lines ...
• [SLOW TEST:14.641 seconds]
[sig-api-machinery] ResourceQuota
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
  should create a ResourceQuota and capture the life of a persistent volume claim with a storage class. [sig-storage]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/resource_quota.go:516
------------------------------
{"msg":"PASSED [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a persistent volume claim with a storage class. [sig-storage]","total":-1,"completed":1,"skipped":5,"failed":0}

SSSSS
------------------------------
[BeforeEach] [k8s.io] [sig-node] Security Context
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:46:43.197: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename security-context
STEP: Waiting for a default service account to be provisioned in namespace
[It] should support seccomp runtime/default [LinuxOnly]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/node/security_context.go:164
STEP: Creating a pod to test seccomp.security.alpha.kubernetes.io/pod
Oct  1 08:46:43.997: INFO: Waiting up to 5m0s for pod "security-context-4d42285c-384c-489c-9421-9830fb950c17" in namespace "security-context-4446" to be "Succeeded or Failed"
Oct  1 08:46:44.131: INFO: Pod "security-context-4d42285c-384c-489c-9421-9830fb950c17": Phase="Pending", Reason="", readiness=false. Elapsed: 133.72775ms
Oct  1 08:46:46.264: INFO: Pod "security-context-4d42285c-384c-489c-9421-9830fb950c17": Phase="Running", Reason="", readiness=true. Elapsed: 2.26637236s
Oct  1 08:46:48.395: INFO: Pod "security-context-4d42285c-384c-489c-9421-9830fb950c17": Phase="Running", Reason="", readiness=true. Elapsed: 4.398085542s
Oct  1 08:46:50.527: INFO: Pod "security-context-4d42285c-384c-489c-9421-9830fb950c17": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.529779234s
STEP: Saw pod success
Oct  1 08:46:50.527: INFO: Pod "security-context-4d42285c-384c-489c-9421-9830fb950c17" satisfied condition "Succeeded or Failed"
Oct  1 08:46:50.659: INFO: Trying to get logs from node ip-172-20-41-255.ap-northeast-1.compute.internal pod security-context-4d42285c-384c-489c-9421-9830fb950c17 container test-container: <nil>
STEP: delete the pod
Oct  1 08:46:50.928: INFO: Waiting for pod security-context-4d42285c-384c-489c-9421-9830fb950c17 to disappear
Oct  1 08:46:51.059: INFO: Pod security-context-4d42285c-384c-489c-9421-9830fb950c17 no longer exists
[AfterEach] [k8s.io] [sig-node] Security Context
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 4 lines ...
• [SLOW TEST:8.128 seconds]
[k8s.io] [sig-node] Security Context
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  should support seccomp runtime/default [LinuxOnly]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/node/security_context.go:164
------------------------------
{"msg":"PASSED [k8s.io] [sig-node] Security Context should support seccomp runtime/default [LinuxOnly]","total":-1,"completed":2,"skipped":6,"failed":0}
[BeforeEach] [Testpattern: Inline-volume (ntfs)][sig-windows] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:46:51.334: INFO: Only supported for providers [azure] (not aws)
[AfterEach] [Testpattern: Inline-volume (ntfs)][sig-windows] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 282 lines ...
• [SLOW TEST:20.359 seconds]
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
  should mutate custom resource with different stored version [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource with different stored version [Conformance]","total":-1,"completed":1,"skipped":5,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:46:55.026: INFO: Only supported for node OS distro [gci ubuntu custom] (not debian)
... skipping 122 lines ...
• [SLOW TEST:11.330 seconds]
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
  should include webhook resources in discovery documents [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should include webhook resources in discovery documents [Conformance]","total":-1,"completed":2,"skipped":9,"failed":0}

SSSSSS
------------------------------
{"msg":"PASSED [sig-storage] HostPath should support subPath [NodeConformance]","total":-1,"completed":1,"skipped":0,"failed":0}
[BeforeEach] [sig-cli] Kubectl Port forwarding
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:46:43.731: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename port-forwarding
STEP: Waiting for a default service account to be provisioned in namespace
... skipping 30 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/portforward.go:452
    that expects NO client request
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/portforward.go:462
      should support a client that connects, sends DATA, and disconnects
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/portforward.go:463
------------------------------
{"msg":"PASSED [sig-cli] Kubectl Port forwarding With a server listening on 0.0.0.0 that expects NO client request should support a client that connects, sends DATA, and disconnects","total":-1,"completed":2,"skipped":0,"failed":0}

SSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ext3)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:46:56.768: INFO: Driver local doesn't support InlineVolume -- skipping
... skipping 154 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:188
    One pod requesting one prebound PVC
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:205
      should be able to mount volume and read from pod1
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:228
------------------------------
{"msg":"PASSED [sig-storage] PersistentVolumes-local  [Volume type: block] One pod requesting one prebound PVC should be able to mount volume and read from pod1","total":-1,"completed":1,"skipped":3,"failed":0}

SSSS
------------------------------
[BeforeEach] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 31 lines ...
• [SLOW TEST:24.059 seconds]
[sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin]
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
  works for CRD preserving unknown fields in an embedded object [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD preserving unknown fields in an embedded object [Conformance]","total":-1,"completed":1,"skipped":2,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:46:58.711: INFO: Driver local doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 58 lines ...
Oct  1 08:46:43.457: INFO: PersistentVolumeClaim pvc-vm5q7 found but phase is Pending instead of Bound.
Oct  1 08:46:45.593: INFO: PersistentVolumeClaim pvc-vm5q7 found and phase=Bound (2.268741046s)
Oct  1 08:46:45.593: INFO: Waiting up to 3m0s for PersistentVolume local-z8vxd to have phase Bound
Oct  1 08:46:45.725: INFO: PersistentVolume local-z8vxd found and phase=Bound (131.795745ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-7jzn
STEP: Creating a pod to test subpath
Oct  1 08:46:46.126: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-7jzn" in namespace "provisioning-5905" to be "Succeeded or Failed"
Oct  1 08:46:46.260: INFO: Pod "pod-subpath-test-preprovisionedpv-7jzn": Phase="Pending", Reason="", readiness=false. Elapsed: 133.078564ms
Oct  1 08:46:48.391: INFO: Pod "pod-subpath-test-preprovisionedpv-7jzn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.265003185s
Oct  1 08:46:50.524: INFO: Pod "pod-subpath-test-preprovisionedpv-7jzn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.397060304s
Oct  1 08:46:52.656: INFO: Pod "pod-subpath-test-preprovisionedpv-7jzn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.529067669s
Oct  1 08:46:54.788: INFO: Pod "pod-subpath-test-preprovisionedpv-7jzn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.661152299s
Oct  1 08:46:56.920: INFO: Pod "pod-subpath-test-preprovisionedpv-7jzn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.793121054s
STEP: Saw pod success
Oct  1 08:46:56.920: INFO: Pod "pod-subpath-test-preprovisionedpv-7jzn" satisfied condition "Succeeded or Failed"
Oct  1 08:46:57.051: INFO: Trying to get logs from node ip-172-20-35-235.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-7jzn container test-container-volume-preprovisionedpv-7jzn: <nil>
STEP: delete the pod
Oct  1 08:46:57.329: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-7jzn to disappear
Oct  1 08:46:57.460: INFO: Pod pod-subpath-test-preprovisionedpv-7jzn no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-7jzn
Oct  1 08:46:57.460: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-7jzn" in namespace "provisioning-5905"
... skipping 19 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support existing directory
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:202
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir-bindmounted] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing directory","total":-1,"completed":1,"skipped":0,"failed":0}

SSSSS
------------------------------
[BeforeEach] [sig-storage] PersistentVolumes-local 
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 60 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:188
    Two pods mounting a local volume one after the other
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:250
      should be able to write from pod1 and read from pod2
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:251
------------------------------
{"msg":"PASSED [sig-storage] PersistentVolumes-local  [Volume type: dir-link] Two pods mounting a local volume one after the other should be able to write from pod1 and read from pod2","total":-1,"completed":1,"skipped":2,"failed":0}

S
------------------------------
[BeforeEach] [sig-node] ConfigMap
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:46:39.426: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename configmap
STEP: Waiting for a default service account to be provisioned in namespace
[It] should be consumable via the environment [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating configMap configmap-3504/configmap-test-898e5c66-89d4-4259-b44e-e5c7a76e40a1
STEP: Creating a pod to test consume configMaps
Oct  1 08:46:40.359: INFO: Waiting up to 5m0s for pod "pod-configmaps-719a8525-f148-4f26-b0f0-e8f0f1a4fb35" in namespace "configmap-3504" to be "Succeeded or Failed"
Oct  1 08:46:40.491: INFO: Pod "pod-configmaps-719a8525-f148-4f26-b0f0-e8f0f1a4fb35": Phase="Pending", Reason="", readiness=false. Elapsed: 131.95331ms
Oct  1 08:46:42.623: INFO: Pod "pod-configmaps-719a8525-f148-4f26-b0f0-e8f0f1a4fb35": Phase="Pending", Reason="", readiness=false. Elapsed: 2.264275406s
Oct  1 08:46:44.755: INFO: Pod "pod-configmaps-719a8525-f148-4f26-b0f0-e8f0f1a4fb35": Phase="Pending", Reason="", readiness=false. Elapsed: 4.396472948s
Oct  1 08:46:46.888: INFO: Pod "pod-configmaps-719a8525-f148-4f26-b0f0-e8f0f1a4fb35": Phase="Pending", Reason="", readiness=false. Elapsed: 6.529054402s
Oct  1 08:46:49.020: INFO: Pod "pod-configmaps-719a8525-f148-4f26-b0f0-e8f0f1a4fb35": Phase="Pending", Reason="", readiness=false. Elapsed: 8.661618889s
Oct  1 08:46:51.153: INFO: Pod "pod-configmaps-719a8525-f148-4f26-b0f0-e8f0f1a4fb35": Phase="Pending", Reason="", readiness=false. Elapsed: 10.794091423s
Oct  1 08:46:53.295: INFO: Pod "pod-configmaps-719a8525-f148-4f26-b0f0-e8f0f1a4fb35": Phase="Pending", Reason="", readiness=false. Elapsed: 12.936564006s
Oct  1 08:46:55.430: INFO: Pod "pod-configmaps-719a8525-f148-4f26-b0f0-e8f0f1a4fb35": Phase="Pending", Reason="", readiness=false. Elapsed: 15.071136568s
Oct  1 08:46:57.562: INFO: Pod "pod-configmaps-719a8525-f148-4f26-b0f0-e8f0f1a4fb35": Phase="Pending", Reason="", readiness=false. Elapsed: 17.203781714s
Oct  1 08:46:59.695: INFO: Pod "pod-configmaps-719a8525-f148-4f26-b0f0-e8f0f1a4fb35": Phase="Pending", Reason="", readiness=false. Elapsed: 19.336505926s
Oct  1 08:47:01.830: INFO: Pod "pod-configmaps-719a8525-f148-4f26-b0f0-e8f0f1a4fb35": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.47186954s
STEP: Saw pod success
Oct  1 08:47:01.831: INFO: Pod "pod-configmaps-719a8525-f148-4f26-b0f0-e8f0f1a4fb35" satisfied condition "Succeeded or Failed"
Oct  1 08:47:01.962: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod pod-configmaps-719a8525-f148-4f26-b0f0-e8f0f1a4fb35 container env-test: <nil>
STEP: delete the pod
Oct  1 08:47:02.231: INFO: Waiting for pod pod-configmaps-719a8525-f148-4f26-b0f0-e8f0f1a4fb35 to disappear
Oct  1 08:47:02.363: INFO: Pod pod-configmaps-719a8525-f148-4f26-b0f0-e8f0f1a4fb35 no longer exists
[AfterEach] [sig-node] ConfigMap
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 4 lines ...
• [SLOW TEST:23.203 seconds]
[sig-node] ConfigMap
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/configmap.go:34
  should be consumable via the environment [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-node] ConfigMap should be consumable via the environment [NodeConformance] [Conformance]","total":-1,"completed":3,"skipped":10,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:02.643: INFO: Only supported for providers [azure] (not aws)
... skipping 95 lines ...
• [SLOW TEST:10.166 seconds]
[sig-apps] DisruptionController
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23
  evictions: enough pods, replicaSet, percentage => should allow an eviction
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/disruption.go:222
------------------------------
{"msg":"PASSED [sig-apps] DisruptionController evictions: enough pods, replicaSet, percentage =\u003e should allow an eviction","total":-1,"completed":2,"skipped":13,"failed":0}
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:05.253: INFO: Driver supports dynamic provisioning, skipping InlineVolume pattern
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 97 lines ...
      Driver local doesn't support ext4 -- skipping

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:178
------------------------------
S
------------------------------
{"msg":"PASSED [k8s.io] [sig-node] PreStop graceful pod terminated should wait until preStop hook completes the process","total":-1,"completed":1,"skipped":0,"failed":0}
[BeforeEach] [sig-instrumentation] Events API
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:47:03.328: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename events
STEP: Waiting for a default service account to be provisioned in namespace
... skipping 18 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:47:05.867: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "events-5644" for this suite.

•
------------------------------
{"msg":"PASSED [sig-instrumentation] Events API should ensure that an event can be fetched, patched, deleted, and listed [Conformance]","total":-1,"completed":2,"skipped":0,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:06.177: INFO: Driver local doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (block volmode)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 239 lines ...
STEP: Creating a kubernetes client
Oct  1 08:46:58.737: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volume-provisioning
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [sig-storage] Dynamic Provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/volume_provisioning.go:145
[It] should report an error and create no PV
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/volume_provisioning.go:778
STEP: creating a StorageClass
STEP: creating a claim object with a suffix for gluster dynamic provisioner
Oct  1 08:46:59.532: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Oct  1 08:47:05.800: INFO: deleting claim "volume-provisioning-6455"/"pvc-fjv4d"
Oct  1 08:47:05.939: INFO: deleting storage class volume-provisioning-6455-invalid-aws
... skipping 5 lines ...

• [SLOW TEST:7.606 seconds]
[sig-storage] Dynamic Provisioning
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  Invalid AWS KMS key
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/volume_provisioning.go:777
    should report an error and create no PV
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/volume_provisioning.go:778
------------------------------
{"msg":"PASSED [sig-storage] Dynamic Provisioning Invalid AWS KMS key should report an error and create no PV","total":-1,"completed":2,"skipped":7,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:06.351: INFO: Driver emptydir doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 147 lines ...
Oct  1 08:46:58.017: INFO: PersistentVolumeClaim pvc-t8lvt found but phase is Pending instead of Bound.
Oct  1 08:47:00.150: INFO: PersistentVolumeClaim pvc-t8lvt found and phase=Bound (4.397588309s)
Oct  1 08:47:00.150: INFO: Waiting up to 3m0s for PersistentVolume local-jgpc6 to have phase Bound
Oct  1 08:47:00.282: INFO: PersistentVolume local-jgpc6 found and phase=Bound (131.895066ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-8qj6
STEP: Creating a pod to test subpath
Oct  1 08:47:00.682: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-8qj6" in namespace "provisioning-3641" to be "Succeeded or Failed"
Oct  1 08:47:00.814: INFO: Pod "pod-subpath-test-preprovisionedpv-8qj6": Phase="Pending", Reason="", readiness=false. Elapsed: 131.853536ms
Oct  1 08:47:02.947: INFO: Pod "pod-subpath-test-preprovisionedpv-8qj6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.264853127s
Oct  1 08:47:05.080: INFO: Pod "pod-subpath-test-preprovisionedpv-8qj6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.397530608s
STEP: Saw pod success
Oct  1 08:47:05.080: INFO: Pod "pod-subpath-test-preprovisionedpv-8qj6" satisfied condition "Succeeded or Failed"
Oct  1 08:47:05.214: INFO: Trying to get logs from node ip-172-20-41-255.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-8qj6 container test-container-volume-preprovisionedpv-8qj6: <nil>
STEP: delete the pod
Oct  1 08:47:05.491: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-8qj6 to disappear
Oct  1 08:47:05.623: INFO: Pod pod-subpath-test-preprovisionedpv-8qj6 no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-8qj6
Oct  1 08:47:05.623: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-8qj6" in namespace "provisioning-3641"
... skipping 19 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support existing directory
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:202
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir-link-bindmounted] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing directory","total":-1,"completed":2,"skipped":10,"failed":0}

SSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:07.487: INFO: Driver hostPath doesn't support DynamicPV -- skipping
... skipping 99 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:47:07.897: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "svcaccounts-9756" for this suite.

•
------------------------------
{"msg":"PASSED [sig-auth] ServiceAccounts should run through the lifecycle of a ServiceAccount [Conformance]","total":-1,"completed":3,"skipped":24,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:08.187: INFO: Driver hostPath doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 45 lines ...
• [SLOW TEST:22.697 seconds]
[sig-api-machinery] Aggregator
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
  Should be able to support the 1.17 Sample API Server using the current Aggregator [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-api-machinery] Aggregator Should be able to support the 1.17 Sample API Server using the current Aggregator [Conformance]","total":-1,"completed":2,"skipped":21,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext3)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:10.037: INFO: Driver csi-hostpath doesn't support PreprovisionedPV -- skipping
... skipping 46 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:47:10.575: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "svcaccounts-9894" for this suite.

•
------------------------------
{"msg":"PASSED [sig-auth] ServiceAccounts should allow opting out of API token automount  [Conformance]","total":-1,"completed":3,"skipped":20,"failed":0}

SSSSSS
------------------------------
[BeforeEach] [sig-storage] PersistentVolumes GCEPD
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 260 lines ...
STEP: Building a namespace api object, basename security-context-test
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [k8s.io] Security Context
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/security_context.go:41
[It] should run with an image specified user ID
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/security_context.go:146
Oct  1 08:47:07.143: INFO: Waiting up to 5m0s for pod "implicit-nonroot-uid" in namespace "security-context-test-5959" to be "Succeeded or Failed"
Oct  1 08:47:07.280: INFO: Pod "implicit-nonroot-uid": Phase="Pending", Reason="", readiness=false. Elapsed: 136.743675ms
Oct  1 08:47:09.416: INFO: Pod "implicit-nonroot-uid": Phase="Pending", Reason="", readiness=false. Elapsed: 2.272598203s
Oct  1 08:47:11.551: INFO: Pod "implicit-nonroot-uid": Phase="Pending", Reason="", readiness=false. Elapsed: 4.408345219s
Oct  1 08:47:13.691: INFO: Pod "implicit-nonroot-uid": Phase="Pending", Reason="", readiness=false. Elapsed: 6.548052785s
Oct  1 08:47:15.827: INFO: Pod "implicit-nonroot-uid": Phase="Pending", Reason="", readiness=false. Elapsed: 8.684097759s
Oct  1 08:47:17.963: INFO: Pod "implicit-nonroot-uid": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.819933391s
Oct  1 08:47:17.963: INFO: Pod "implicit-nonroot-uid" satisfied condition "Succeeded or Failed"
[AfterEach] [k8s.io] Security Context
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:47:18.100: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "security-context-test-5959" for this suite.


... skipping 2 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  When creating a container with runAsNonRoot
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/security_context.go:99
    should run with an image specified user ID
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/security_context.go:146
------------------------------
{"msg":"PASSED [k8s.io] Security Context When creating a container with runAsNonRoot should run with an image specified user ID","total":-1,"completed":3,"skipped":28,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:18.396: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
... skipping 88 lines ...
[sig-storage] CSI Volumes
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  [Driver: csi-hostpath]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_volumes.go:39
    [Testpattern: Dynamic PV (immediate binding)] topology
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should fail to schedule a pod which has topologies that conflict with AllowedTopologies [BeforeEach]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Driver "csi-hostpath" does not support topology - skipping

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:97
------------------------------
... skipping 213 lines ...
• [SLOW TEST:44.246 seconds]
[sig-network] Services
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
  should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]","total":-1,"completed":2,"skipped":7,"failed":0}
[BeforeEach] [Testpattern: Inline-volume (ext4)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:20.483: INFO: Only supported for providers [azure] (not aws)
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 121 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:188
    One pod requesting one prebound PVC
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:205
      should be able to mount volume and write from pod1
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:234
------------------------------
{"msg":"PASSED [sig-storage] PersistentVolumes-local  [Volume type: dir-bindmounted] One pod requesting one prebound PVC should be able to mount volume and write from pod1","total":-1,"completed":2,"skipped":3,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:22.933: INFO: Driver hostPath doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (default fs)] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 141 lines ...
STEP: Looking for a node to schedule stateful set and pod
STEP: Creating pod with conflicting port in namespace statefulset-6024
STEP: Creating statefulset with conflicting port in namespace statefulset-6024
STEP: Waiting until pod test-pod will start running in namespace statefulset-6024
STEP: Waiting until stateful pod ss-0 will be recreated and deleted at least once in namespace statefulset-6024
Oct  1 08:47:07.080: INFO: Observed stateful pod in namespace: statefulset-6024, name: ss-0, uid: bd2e0aaa-85cf-447c-8473-2ae6d938aeae, status phase: Pending. Waiting for statefulset controller to delete.
Oct  1 08:47:07.807: INFO: Observed stateful pod in namespace: statefulset-6024, name: ss-0, uid: bd2e0aaa-85cf-447c-8473-2ae6d938aeae, status phase: Failed. Waiting for statefulset controller to delete.
Oct  1 08:47:07.822: INFO: Observed stateful pod in namespace: statefulset-6024, name: ss-0, uid: bd2e0aaa-85cf-447c-8473-2ae6d938aeae, status phase: Failed. Waiting for statefulset controller to delete.
Oct  1 08:47:07.842: INFO: Observed delete event for stateful pod ss-0 in namespace statefulset-6024
STEP: Removing pod with conflicting port in namespace statefulset-6024
STEP: Waiting when stateful pod ss-0 will be recreated in namespace statefulset-6024 and will be in running state
[AfterEach] [k8s.io] Basic StatefulSet functionality [StatefulSetBasic]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/statefulset.go:114
Oct  1 08:47:12.387: INFO: Deleting all statefulset in ns statefulset-6024
... skipping 11 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23
  [k8s.io] Basic StatefulSet functionality [StatefulSetBasic]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
    Should recreate evicted statefulset [Conformance]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-apps] StatefulSet [k8s.io] Basic StatefulSet functionality [StatefulSetBasic] Should recreate evicted statefulset [Conformance]","total":-1,"completed":3,"skipped":35,"failed":0}

SSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:23.884: INFO: Only supported for node OS distro [gci ubuntu custom] (not debian)
... skipping 41 lines ...
Oct  1 08:46:44.077: INFO: PersistentVolumeClaim pvc-46ds2 found but phase is Pending instead of Bound.
Oct  1 08:46:46.208: INFO: PersistentVolumeClaim pvc-46ds2 found and phase=Bound (2.261786415s)
Oct  1 08:46:46.208: INFO: Waiting up to 3m0s for PersistentVolume local-28pkl to have phase Bound
Oct  1 08:46:46.338: INFO: PersistentVolume local-28pkl found and phase=Bound (130.373627ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-q74c
STEP: Creating a pod to test atomic-volume-subpath
Oct  1 08:46:46.732: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-q74c" in namespace "provisioning-1576" to be "Succeeded or Failed"
Oct  1 08:46:46.862: INFO: Pod "pod-subpath-test-preprovisionedpv-q74c": Phase="Pending", Reason="", readiness=false. Elapsed: 130.388ms
Oct  1 08:46:49.000: INFO: Pod "pod-subpath-test-preprovisionedpv-q74c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.268776877s
Oct  1 08:46:51.131: INFO: Pod "pod-subpath-test-preprovisionedpv-q74c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.399711827s
Oct  1 08:46:53.276: INFO: Pod "pod-subpath-test-preprovisionedpv-q74c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.544124244s
Oct  1 08:46:55.409: INFO: Pod "pod-subpath-test-preprovisionedpv-q74c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.677776752s
Oct  1 08:46:57.540: INFO: Pod "pod-subpath-test-preprovisionedpv-q74c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.808482741s
... skipping 6 lines ...
Oct  1 08:47:12.478: INFO: Pod "pod-subpath-test-preprovisionedpv-q74c": Phase="Running", Reason="", readiness=true. Elapsed: 25.746760157s
Oct  1 08:47:14.609: INFO: Pod "pod-subpath-test-preprovisionedpv-q74c": Phase="Running", Reason="", readiness=true. Elapsed: 27.877397538s
Oct  1 08:47:16.740: INFO: Pod "pod-subpath-test-preprovisionedpv-q74c": Phase="Running", Reason="", readiness=true. Elapsed: 30.008037334s
Oct  1 08:47:18.873: INFO: Pod "pod-subpath-test-preprovisionedpv-q74c": Phase="Running", Reason="", readiness=true. Elapsed: 32.141140964s
Oct  1 08:47:21.004: INFO: Pod "pod-subpath-test-preprovisionedpv-q74c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.272396435s
STEP: Saw pod success
Oct  1 08:47:21.004: INFO: Pod "pod-subpath-test-preprovisionedpv-q74c" satisfied condition "Succeeded or Failed"
Oct  1 08:47:21.138: INFO: Trying to get logs from node ip-172-20-60-245.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-q74c container test-container-subpath-preprovisionedpv-q74c: <nil>
STEP: delete the pod
Oct  1 08:47:21.407: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-q74c to disappear
Oct  1 08:47:21.537: INFO: Pod pod-subpath-test-preprovisionedpv-q74c no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-q74c
Oct  1 08:47:21.537: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-q74c" in namespace "provisioning-1576"
... skipping 22 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support file as subpath [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:227
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: tmpfs] [Testpattern: Pre-provisioned PV (default fs)] subPath should support file as subpath [LinuxOnly]","total":-1,"completed":1,"skipped":0,"failed":0}

SSS
------------------------------
[BeforeEach] [sig-network] Conntrack
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 1803 lines ...
• [SLOW TEST:49.688 seconds]
[sig-network] Conntrack
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
  should be able to preserve UDP traffic when server pod cycles for a NodePort service
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/conntrack.go:128
------------------------------
{"msg":"PASSED [sig-network] Conntrack should be able to preserve UDP traffic when server pod cycles for a NodePort service","total":-1,"completed":1,"skipped":1,"failed":0}

SSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:24.339: INFO: Only supported for node OS distro [gci ubuntu custom] (not debian)
... skipping 41 lines ...
• [SLOW TEST:6.095 seconds]
[k8s.io] PrivilegedPod [NodeConformance]
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  should enable privileged commands [LinuxOnly]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/privileged.go:49
------------------------------
{"msg":"PASSED [k8s.io] PrivilegedPod [NodeConformance] should enable privileged commands [LinuxOnly]","total":-1,"completed":2,"skipped":7,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:24.837: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 74 lines ...
[It] should support non-existent path
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:191
Oct  1 08:47:19.604: INFO: In-tree plugin kubernetes.io/empty-dir is not migrated, not validating any metrics
Oct  1 08:47:19.604: INFO: Creating resource for inline volume
STEP: Creating pod pod-subpath-test-inlinevolume-9jzd
STEP: Creating a pod to test subpath
Oct  1 08:47:19.739: INFO: Waiting up to 5m0s for pod "pod-subpath-test-inlinevolume-9jzd" in namespace "provisioning-483" to be "Succeeded or Failed"
Oct  1 08:47:19.871: INFO: Pod "pod-subpath-test-inlinevolume-9jzd": Phase="Pending", Reason="", readiness=false. Elapsed: 132.593251ms
Oct  1 08:47:22.005: INFO: Pod "pod-subpath-test-inlinevolume-9jzd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.26596258s
Oct  1 08:47:24.138: INFO: Pod "pod-subpath-test-inlinevolume-9jzd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.398726358s
STEP: Saw pod success
Oct  1 08:47:24.138: INFO: Pod "pod-subpath-test-inlinevolume-9jzd" satisfied condition "Succeeded or Failed"
Oct  1 08:47:24.270: INFO: Trying to get logs from node ip-172-20-35-235.ap-northeast-1.compute.internal pod pod-subpath-test-inlinevolume-9jzd container test-container-volume-inlinevolume-9jzd: <nil>
STEP: delete the pod
Oct  1 08:47:24.560: INFO: Waiting for pod pod-subpath-test-inlinevolume-9jzd to disappear
Oct  1 08:47:24.692: INFO: Pod pod-subpath-test-inlinevolume-9jzd no longer exists
STEP: Deleting pod pod-subpath-test-inlinevolume-9jzd
Oct  1 08:47:24.692: INFO: Deleting pod "pod-subpath-test-inlinevolume-9jzd" in namespace "provisioning-483"
... skipping 12 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Inline-volume (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support non-existent path
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:191
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: emptydir] [Testpattern: Inline-volume (default fs)] subPath should support non-existent path","total":-1,"completed":1,"skipped":20,"failed":0}

S
------------------------------
[BeforeEach] [sig-network] Services
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 30 lines ...
• [SLOW TEST:30.374 seconds]
[sig-network] Services
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
  should be able to change the type from ClusterIP to ExternalName [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-network] Services should be able to change the type from ClusterIP to ExternalName [Conformance]","total":-1,"completed":3,"skipped":15,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:25.537: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 20 lines ...
[BeforeEach] [sig-apps] Job
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:47:10.875: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename job
STEP: Waiting for a default service account to be provisioned in namespace
[It] should run a job to completion when tasks sometimes fail and are locally restarted [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating a job
STEP: Ensuring job reaches completions
[AfterEach] [sig-apps] Job
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:47:25.804: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "job-7550" for this suite.


• [SLOW TEST:15.200 seconds]
[sig-apps] Job
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23
  should run a job to completion when tasks sometimes fail and are locally restarted [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-apps] Job should run a job to completion when tasks sometimes fail and are locally restarted [Conformance]","total":-1,"completed":4,"skipped":26,"failed":0}

SSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:26.101: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
... skipping 39 lines ...
Oct  1 08:47:14.079: INFO: PersistentVolumeClaim pvc-66l9k found but phase is Pending instead of Bound.
Oct  1 08:47:16.215: INFO: PersistentVolumeClaim pvc-66l9k found and phase=Bound (6.542272223s)
Oct  1 08:47:16.215: INFO: Waiting up to 3m0s for PersistentVolume local-tz6gt to have phase Bound
Oct  1 08:47:16.350: INFO: PersistentVolume local-tz6gt found and phase=Bound (135.235248ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-6xff
STEP: Creating a pod to test subpath
Oct  1 08:47:16.764: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-6xff" in namespace "provisioning-6915" to be "Succeeded or Failed"
Oct  1 08:47:16.902: INFO: Pod "pod-subpath-test-preprovisionedpv-6xff": Phase="Pending", Reason="", readiness=false. Elapsed: 137.852298ms
Oct  1 08:47:19.037: INFO: Pod "pod-subpath-test-preprovisionedpv-6xff": Phase="Pending", Reason="", readiness=false. Elapsed: 2.27343031s
Oct  1 08:47:21.173: INFO: Pod "pod-subpath-test-preprovisionedpv-6xff": Phase="Pending", Reason="", readiness=false. Elapsed: 4.409522494s
Oct  1 08:47:23.309: INFO: Pod "pod-subpath-test-preprovisionedpv-6xff": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.545330918s
STEP: Saw pod success
Oct  1 08:47:23.309: INFO: Pod "pod-subpath-test-preprovisionedpv-6xff" satisfied condition "Succeeded or Failed"
Oct  1 08:47:23.445: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-6xff container test-container-volume-preprovisionedpv-6xff: <nil>
STEP: delete the pod
Oct  1 08:47:23.723: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-6xff to disappear
Oct  1 08:47:23.859: INFO: Pod pod-subpath-test-preprovisionedpv-6xff no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-6xff
Oct  1 08:47:23.859: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-6xff" in namespace "provisioning-6915"
... skipping 22 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support non-existent path
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:191
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: tmpfs] [Testpattern: Pre-provisioned PV (default fs)] subPath should support non-existent path","total":-1,"completed":3,"skipped":20,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:26.632: INFO: Driver local doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 37 lines ...
• [SLOW TEST:13.173 seconds]
[sig-auth] Certificates API [Privileged:ClusterAdmin]
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/auth/framework.go:23
  should support building a client with a CSR
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/auth/certificates.go:55
------------------------------
{"msg":"PASSED [sig-auth] Certificates API [Privileged:ClusterAdmin] should support building a client with a CSR","total":-1,"completed":4,"skipped":21,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:27.349: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
... skipping 167 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/portforward.go:474
    that expects NO client request
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/portforward.go:484
      should support a client that connects, sends DATA, and disconnects
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/portforward.go:485
------------------------------
{"msg":"PASSED [sig-cli] Kubectl Port forwarding With a server listening on localhost that expects NO client request should support a client that connects, sends DATA, and disconnects","total":-1,"completed":3,"skipped":31,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:28.223: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 12 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:192

      Driver local doesn't support DynamicPV -- skipping

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:173
------------------------------
{"msg":"PASSED [sig-network] Ingress API should support creating Ingress API operations [Conformance]","total":-1,"completed":1,"skipped":1,"failed":0}
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:46:40.613: INFO: >>> kubeConfig: /root/.kube/config
... skipping 18 lines ...
Oct  1 08:47:14.196: INFO: PersistentVolumeClaim pvc-jf7vs found but phase is Pending instead of Bound.
Oct  1 08:47:16.332: INFO: PersistentVolumeClaim pvc-jf7vs found and phase=Bound (13.007305348s)
Oct  1 08:47:16.332: INFO: Waiting up to 3m0s for PersistentVolume local-48lqt to have phase Bound
Oct  1 08:47:16.467: INFO: PersistentVolume local-48lqt found and phase=Bound (135.18551ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-lmmq
STEP: Creating a pod to test subpath
Oct  1 08:47:16.878: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-lmmq" in namespace "provisioning-7946" to be "Succeeded or Failed"
Oct  1 08:47:17.014: INFO: Pod "pod-subpath-test-preprovisionedpv-lmmq": Phase="Pending", Reason="", readiness=false. Elapsed: 135.33848ms
Oct  1 08:47:19.149: INFO: Pod "pod-subpath-test-preprovisionedpv-lmmq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.27089422s
Oct  1 08:47:21.285: INFO: Pod "pod-subpath-test-preprovisionedpv-lmmq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.406365245s
Oct  1 08:47:23.420: INFO: Pod "pod-subpath-test-preprovisionedpv-lmmq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.542038879s
Oct  1 08:47:25.556: INFO: Pod "pod-subpath-test-preprovisionedpv-lmmq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.677919256s
STEP: Saw pod success
Oct  1 08:47:25.556: INFO: Pod "pod-subpath-test-preprovisionedpv-lmmq" satisfied condition "Succeeded or Failed"
Oct  1 08:47:25.692: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-lmmq container test-container-subpath-preprovisionedpv-lmmq: <nil>
STEP: delete the pod
Oct  1 08:47:25.971: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-lmmq to disappear
Oct  1 08:47:26.107: INFO: Pod pod-subpath-test-preprovisionedpv-lmmq no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-lmmq
Oct  1 08:47:26.107: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-lmmq" in namespace "provisioning-7946"
... skipping 22 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support readOnly file specified in the volumeMount [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:376
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: tmpfs] [Testpattern: Pre-provisioned PV (default fs)] subPath should support readOnly file specified in the volumeMount [LinuxOnly]","total":-1,"completed":2,"skipped":1,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:28.860: INFO: Only supported for node OS distro [gci ubuntu custom] (not debian)
... skipping 5 lines ...
[sig-storage] In-tree Volumes
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  [Driver: gluster]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Dynamic PV (delayed binding)] topology
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should fail to schedule a pod which has topologies that conflict with AllowedTopologies [BeforeEach]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Only supported for node OS distro [gci ubuntu custom] (not debian)

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/drivers/in_tree.go:265
------------------------------
... skipping 72 lines ...
• [SLOW TEST:9.271 seconds]
[sig-network] Services
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
  should release NodePorts on delete
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:1911
------------------------------
{"msg":"PASSED [sig-network] Services should release NodePorts on delete","total":-1,"completed":3,"skipped":12,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:29.796: INFO: Driver local doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 27 lines ...
[sig-storage] CSI Volumes
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  [Driver: csi-hostpath]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_volumes.go:39
    [Testpattern: Dynamic PV (delayed binding)] topology
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should fail to schedule a pod which has topologies that conflict with AllowedTopologies [BeforeEach]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Driver "csi-hostpath" does not support topology - skipping

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:97
------------------------------
... skipping 32 lines ...
Oct  1 08:47:02.464: INFO: PersistentVolume nfs-8q24b found and phase=Bound (128.063824ms)
Oct  1 08:47:02.592: INFO: Waiting up to 3m0s for PersistentVolumeClaims [pvc-nqxp5] to have phase Bound
Oct  1 08:47:02.721: INFO: PersistentVolumeClaim pvc-nqxp5 found and phase=Bound (128.949631ms)
STEP: Checking pod has write access to PersistentVolumes
Oct  1 08:47:02.863: INFO: Creating nfs test pod
Oct  1 08:47:02.992: INFO: Pod should terminate with exitcode 0 (success)
Oct  1 08:47:02.992: INFO: Waiting up to 5m0s for pod "pvc-tester-vfr9t" in namespace "pv-2569" to be "Succeeded or Failed"
Oct  1 08:47:03.120: INFO: Pod "pvc-tester-vfr9t": Phase="Pending", Reason="", readiness=false. Elapsed: 127.89659ms
Oct  1 08:47:05.248: INFO: Pod "pvc-tester-vfr9t": Phase="Pending", Reason="", readiness=false. Elapsed: 2.256465831s
Oct  1 08:47:07.378: INFO: Pod "pvc-tester-vfr9t": Phase="Pending", Reason="", readiness=false. Elapsed: 4.385878244s
Oct  1 08:47:09.510: INFO: Pod "pvc-tester-vfr9t": Phase="Pending", Reason="", readiness=false. Elapsed: 6.517979472s
Oct  1 08:47:11.638: INFO: Pod "pvc-tester-vfr9t": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.646388494s
STEP: Saw pod success
Oct  1 08:47:11.638: INFO: Pod "pvc-tester-vfr9t" satisfied condition "Succeeded or Failed"
Oct  1 08:47:11.638: INFO: Pod pvc-tester-vfr9t succeeded 
Oct  1 08:47:11.638: INFO: Deleting pod "pvc-tester-vfr9t" in namespace "pv-2569"
Oct  1 08:47:11.772: INFO: Wait up to 5m0s for pod "pvc-tester-vfr9t" to be fully deleted
Oct  1 08:47:12.028: INFO: Creating nfs test pod
Oct  1 08:47:12.170: INFO: Pod should terminate with exitcode 0 (success)
Oct  1 08:47:12.170: INFO: Waiting up to 5m0s for pod "pvc-tester-f9qkh" in namespace "pv-2569" to be "Succeeded or Failed"
Oct  1 08:47:12.298: INFO: Pod "pvc-tester-f9qkh": Phase="Pending", Reason="", readiness=false. Elapsed: 128.207371ms
Oct  1 08:47:14.426: INFO: Pod "pvc-tester-f9qkh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.256521835s
Oct  1 08:47:16.555: INFO: Pod "pvc-tester-f9qkh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.384824766s
Oct  1 08:47:18.683: INFO: Pod "pvc-tester-f9qkh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.513195253s
Oct  1 08:47:20.814: INFO: Pod "pvc-tester-f9qkh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.644296706s
STEP: Saw pod success
Oct  1 08:47:20.814: INFO: Pod "pvc-tester-f9qkh" satisfied condition "Succeeded or Failed"
Oct  1 08:47:20.814: INFO: Pod pvc-tester-f9qkh succeeded 
Oct  1 08:47:20.814: INFO: Deleting pod "pvc-tester-f9qkh" in namespace "pv-2569"
Oct  1 08:47:20.948: INFO: Wait up to 5m0s for pod "pvc-tester-f9qkh" to be fully deleted
STEP: Deleting PVCs to invoke reclaim policy
Oct  1 08:47:21.588: INFO: Deleting PVC pvc-nqxp5 to trigger reclamation of PV nfs-8q24b
Oct  1 08:47:21.588: INFO: Deleting PersistentVolumeClaim "pvc-nqxp5"
... skipping 31 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes.go:122
    with multiple PVs and PVCs all in same ns
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes.go:212
      should create 2 PVs and 4 PVCs: test write access
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes.go:233
------------------------------
{"msg":"PASSED [sig-storage] PersistentVolumes NFS with multiple PVs and PVCs all in same ns should create 2 PVs and 4 PVCs: test write access","total":-1,"completed":1,"skipped":4,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:31.927: INFO: Only supported for providers [azure] (not aws)
... skipping 42 lines ...
• [SLOW TEST:56.792 seconds]
[sig-api-machinery] ResourceQuota
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
  should create a ResourceQuota and capture the life of a custom resource.
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/resource_quota.go:568
------------------------------
{"msg":"PASSED [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a custom resource.","total":-1,"completed":1,"skipped":4,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
... skipping 57 lines ...
Oct  1 08:46:49.171: INFO: PersistentVolumeClaim csi-hostpathxhpg8 found but phase is Pending instead of Bound.
Oct  1 08:46:51.304: INFO: PersistentVolumeClaim csi-hostpathxhpg8 found but phase is Pending instead of Bound.
Oct  1 08:46:53.438: INFO: PersistentVolumeClaim csi-hostpathxhpg8 found but phase is Pending instead of Bound.
Oct  1 08:46:55.586: INFO: PersistentVolumeClaim csi-hostpathxhpg8 found and phase=Bound (12.953072441s)
STEP: Creating pod pod-subpath-test-dynamicpv-qz87
STEP: Creating a pod to test subpath
Oct  1 08:46:56.063: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qz87" in namespace "provisioning-8644" to be "Succeeded or Failed"
Oct  1 08:46:56.199: INFO: Pod "pod-subpath-test-dynamicpv-qz87": Phase="Pending", Reason="", readiness=false. Elapsed: 136.537084ms
Oct  1 08:46:58.333: INFO: Pod "pod-subpath-test-dynamicpv-qz87": Phase="Pending", Reason="", readiness=false. Elapsed: 2.26992135s
Oct  1 08:47:00.466: INFO: Pod "pod-subpath-test-dynamicpv-qz87": Phase="Pending", Reason="", readiness=false. Elapsed: 4.403670386s
Oct  1 08:47:02.600: INFO: Pod "pod-subpath-test-dynamicpv-qz87": Phase="Pending", Reason="", readiness=false. Elapsed: 6.537003085s
Oct  1 08:47:04.766: INFO: Pod "pod-subpath-test-dynamicpv-qz87": Phase="Pending", Reason="", readiness=false. Elapsed: 8.703357573s
Oct  1 08:47:06.900: INFO: Pod "pod-subpath-test-dynamicpv-qz87": Phase="Pending", Reason="", readiness=false. Elapsed: 10.837148794s
Oct  1 08:47:09.034: INFO: Pod "pod-subpath-test-dynamicpv-qz87": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.970838525s
STEP: Saw pod success
Oct  1 08:47:09.034: INFO: Pod "pod-subpath-test-dynamicpv-qz87" satisfied condition "Succeeded or Failed"
Oct  1 08:47:09.167: INFO: Trying to get logs from node ip-172-20-60-245.ap-northeast-1.compute.internal pod pod-subpath-test-dynamicpv-qz87 container test-container-volume-dynamicpv-qz87: <nil>
STEP: delete the pod
Oct  1 08:47:09.445: INFO: Waiting for pod pod-subpath-test-dynamicpv-qz87 to disappear
Oct  1 08:47:09.578: INFO: Pod pod-subpath-test-dynamicpv-qz87 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-qz87
Oct  1 08:47:09.578: INFO: Deleting pod "pod-subpath-test-dynamicpv-qz87" in namespace "provisioning-8644"
... skipping 55 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_volumes.go:39
    [Testpattern: Dynamic PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support existing directory
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:202
------------------------------
{"msg":"PASSED [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support existing directory","total":-1,"completed":1,"skipped":2,"failed":0}

SSS
------------------------------
[BeforeEach] [sig-storage] Projected downwardAPI
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 2 lines ...
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [sig-storage] Projected downwardAPI
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_downwardapi.go:41
[It] should provide node allocatable (cpu) as default cpu limit if the limit is not set [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating a pod to test downward API volume plugin
Oct  1 08:47:23.820: INFO: Waiting up to 5m0s for pod "downwardapi-volume-dd28a34e-3751-4abc-9d71-50fbebe952a2" in namespace "projected-3988" to be "Succeeded or Failed"
Oct  1 08:47:23.955: INFO: Pod "downwardapi-volume-dd28a34e-3751-4abc-9d71-50fbebe952a2": Phase="Pending", Reason="", readiness=false. Elapsed: 134.748952ms
Oct  1 08:47:26.092: INFO: Pod "downwardapi-volume-dd28a34e-3751-4abc-9d71-50fbebe952a2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.27181629s
Oct  1 08:47:28.227: INFO: Pod "downwardapi-volume-dd28a34e-3751-4abc-9d71-50fbebe952a2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.406234446s
Oct  1 08:47:30.362: INFO: Pod "downwardapi-volume-dd28a34e-3751-4abc-9d71-50fbebe952a2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.541834629s
Oct  1 08:47:32.507: INFO: Pod "downwardapi-volume-dd28a34e-3751-4abc-9d71-50fbebe952a2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.686360162s
Oct  1 08:47:34.642: INFO: Pod "downwardapi-volume-dd28a34e-3751-4abc-9d71-50fbebe952a2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.821277308s
STEP: Saw pod success
Oct  1 08:47:34.642: INFO: Pod "downwardapi-volume-dd28a34e-3751-4abc-9d71-50fbebe952a2" satisfied condition "Succeeded or Failed"
Oct  1 08:47:34.786: INFO: Trying to get logs from node ip-172-20-60-245.ap-northeast-1.compute.internal pod downwardapi-volume-dd28a34e-3751-4abc-9d71-50fbebe952a2 container client-container: <nil>
STEP: delete the pod
Oct  1 08:47:35.067: INFO: Waiting for pod downwardapi-volume-dd28a34e-3751-4abc-9d71-50fbebe952a2 to disappear
Oct  1 08:47:35.202: INFO: Pod downwardapi-volume-dd28a34e-3751-4abc-9d71-50fbebe952a2 no longer exists
[AfterEach] [sig-storage] Projected downwardAPI
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 4 lines ...
• [SLOW TEST:12.464 seconds]
[sig-storage] Projected downwardAPI
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_downwardapi.go:35
  should provide node allocatable (cpu) as default cpu limit if the limit is not set [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-storage] Projected downwardAPI should provide node allocatable (cpu) as default cpu limit if the limit is not set [NodeConformance] [Conformance]","total":-1,"completed":3,"skipped":17,"failed":0}

SSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 21 lines ...
Oct  1 08:47:14.375: INFO: PersistentVolumeClaim pvc-kqwjv found but phase is Pending instead of Bound.
Oct  1 08:47:16.511: INFO: PersistentVolumeClaim pvc-kqwjv found and phase=Bound (12.948389603s)
Oct  1 08:47:16.511: INFO: Waiting up to 3m0s for PersistentVolume local-v52r8 to have phase Bound
Oct  1 08:47:16.646: INFO: PersistentVolume local-v52r8 found and phase=Bound (134.415072ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-st4f
STEP: Creating a pod to test subpath
Oct  1 08:47:17.050: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-st4f" in namespace "provisioning-2780" to be "Succeeded or Failed"
Oct  1 08:47:17.185: INFO: Pod "pod-subpath-test-preprovisionedpv-st4f": Phase="Pending", Reason="", readiness=false. Elapsed: 135.096853ms
Oct  1 08:47:19.320: INFO: Pod "pod-subpath-test-preprovisionedpv-st4f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.269647778s
Oct  1 08:47:21.455: INFO: Pod "pod-subpath-test-preprovisionedpv-st4f": Phase="Pending", Reason="", readiness=false. Elapsed: 4.404707091s
Oct  1 08:47:23.590: INFO: Pod "pod-subpath-test-preprovisionedpv-st4f": Phase="Pending", Reason="", readiness=false. Elapsed: 6.539321666s
Oct  1 08:47:25.728: INFO: Pod "pod-subpath-test-preprovisionedpv-st4f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.677622871s
STEP: Saw pod success
Oct  1 08:47:25.728: INFO: Pod "pod-subpath-test-preprovisionedpv-st4f" satisfied condition "Succeeded or Failed"
Oct  1 08:47:25.863: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-st4f container test-container-subpath-preprovisionedpv-st4f: <nil>
STEP: delete the pod
Oct  1 08:47:26.144: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-st4f to disappear
Oct  1 08:47:26.279: INFO: Pod pod-subpath-test-preprovisionedpv-st4f no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-st4f
Oct  1 08:47:26.279: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-st4f" in namespace "provisioning-2780"
STEP: Creating pod pod-subpath-test-preprovisionedpv-st4f
STEP: Creating a pod to test subpath
Oct  1 08:47:26.549: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-st4f" in namespace "provisioning-2780" to be "Succeeded or Failed"
Oct  1 08:47:26.683: INFO: Pod "pod-subpath-test-preprovisionedpv-st4f": Phase="Pending", Reason="", readiness=false. Elapsed: 134.237961ms
Oct  1 08:47:28.818: INFO: Pod "pod-subpath-test-preprovisionedpv-st4f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.268969476s
Oct  1 08:47:30.953: INFO: Pod "pod-subpath-test-preprovisionedpv-st4f": Phase="Pending", Reason="", readiness=false. Elapsed: 4.4038147s
Oct  1 08:47:33.088: INFO: Pod "pod-subpath-test-preprovisionedpv-st4f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.538860708s
STEP: Saw pod success
Oct  1 08:47:33.088: INFO: Pod "pod-subpath-test-preprovisionedpv-st4f" satisfied condition "Succeeded or Failed"
Oct  1 08:47:33.222: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-st4f container test-container-subpath-preprovisionedpv-st4f: <nil>
STEP: delete the pod
Oct  1 08:47:33.508: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-st4f to disappear
Oct  1 08:47:33.643: INFO: Pod pod-subpath-test-preprovisionedpv-st4f no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-st4f
Oct  1 08:47:33.643: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-st4f" in namespace "provisioning-2780"
... skipping 22 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support existing directories when readOnly specified in the volumeSource
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:391
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: tmpfs] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing directories when readOnly specified in the volumeSource","total":-1,"completed":3,"skipped":17,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:36.398: INFO: Driver local doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (default fs)] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 21 lines ...
STEP: Building a namespace api object, basename projected
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 with FSGroup [LinuxOnly] [NodeFeature:FSGroup]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_configmap.go:110
STEP: Creating configMap with name projected-configmap-test-volume-map-3c2c61c6-cf37-488f-a59a-f58d1047822d
STEP: Creating a pod to test consume configMaps
Oct  1 08:47:29.158: INFO: Waiting up to 5m0s for pod "pod-projected-configmaps-3da74066-6743-46b3-866e-fcace1087219" in namespace "projected-261" to be "Succeeded or Failed"
Oct  1 08:47:29.291: INFO: Pod "pod-projected-configmaps-3da74066-6743-46b3-866e-fcace1087219": Phase="Pending", Reason="", readiness=false. Elapsed: 132.775152ms
Oct  1 08:47:31.422: INFO: Pod "pod-projected-configmaps-3da74066-6743-46b3-866e-fcace1087219": Phase="Pending", Reason="", readiness=false. Elapsed: 2.264302043s
Oct  1 08:47:33.556: INFO: Pod "pod-projected-configmaps-3da74066-6743-46b3-866e-fcace1087219": Phase="Pending", Reason="", readiness=false. Elapsed: 4.397556906s
Oct  1 08:47:35.687: INFO: Pod "pod-projected-configmaps-3da74066-6743-46b3-866e-fcace1087219": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.528573195s
STEP: Saw pod success
Oct  1 08:47:35.687: INFO: Pod "pod-projected-configmaps-3da74066-6743-46b3-866e-fcace1087219" satisfied condition "Succeeded or Failed"
Oct  1 08:47:35.817: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod pod-projected-configmaps-3da74066-6743-46b3-866e-fcace1087219 container agnhost-container: <nil>
STEP: delete the pod
Oct  1 08:47:36.086: INFO: Waiting for pod pod-projected-configmaps-3da74066-6743-46b3-866e-fcace1087219 to disappear
Oct  1 08:47:36.216: INFO: Pod pod-projected-configmaps-3da74066-6743-46b3-866e-fcace1087219 no longer exists
[AfterEach] [sig-storage] Projected configMap
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 4 lines ...
• [SLOW TEST:8.252 seconds]
[sig-storage] Projected configMap
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_configmap.go:36
  should be consumable from pods in volume with mappings as non-root with FSGroup [LinuxOnly] [NodeFeature:FSGroup]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_configmap.go:110
------------------------------
{"msg":"PASSED [sig-storage] Projected configMap should be consumable from pods in volume with mappings as non-root with FSGroup [LinuxOnly] [NodeFeature:FSGroup]","total":-1,"completed":4,"skipped":35,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:36.490: INFO: Driver local doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 142 lines ...
Oct  1 08:47:28.494: INFO: deployment status: v1.DeploymentStatus{ObservedGeneration:1, Replicas:1, UpdatedReplicas:1, ReadyReplicas:0, AvailableReplicas:0, UnavailableReplicas:1, Conditions:[]v1.DeploymentCondition{v1.DeploymentCondition{Type:"Available", Status:"False", LastUpdateTime:v1.Time{Time:time.Time{wall:0x0, ext:63768674848, loc:(*time.Location)(0x7984060)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63768674848, loc:(*time.Location)(0x7984060)}}, Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:v1.Time{Time:time.Time{wall:0x0, ext:63768674848, loc:(*time.Location)(0x7984060)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63768674848, loc:(*time.Location)(0x7984060)}}, Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"sample-webhook-deployment-6bd9446d55\" is progressing."}}, CollisionCount:(*int32)(nil)}
Oct  1 08:47:30.626: INFO: deployment status: v1.DeploymentStatus{ObservedGeneration:1, Replicas:1, UpdatedReplicas:1, ReadyReplicas:0, AvailableReplicas:0, UnavailableReplicas:1, Conditions:[]v1.DeploymentCondition{v1.DeploymentCondition{Type:"Available", Status:"False", LastUpdateTime:v1.Time{Time:time.Time{wall:0x0, ext:63768674848, loc:(*time.Location)(0x7984060)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63768674848, loc:(*time.Location)(0x7984060)}}, Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:v1.Time{Time:time.Time{wall:0x0, ext:63768674848, loc:(*time.Location)(0x7984060)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63768674848, loc:(*time.Location)(0x7984060)}}, Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"sample-webhook-deployment-6bd9446d55\" is progressing."}}, CollisionCount:(*int32)(nil)}
Oct  1 08:47:32.629: INFO: deployment status: v1.DeploymentStatus{ObservedGeneration:1, Replicas:1, UpdatedReplicas:1, ReadyReplicas:0, AvailableReplicas:0, UnavailableReplicas:1, Conditions:[]v1.DeploymentCondition{v1.DeploymentCondition{Type:"Available", Status:"False", LastUpdateTime:v1.Time{Time:time.Time{wall:0x0, ext:63768674848, loc:(*time.Location)(0x7984060)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63768674848, loc:(*time.Location)(0x7984060)}}, Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:v1.Time{Time:time.Time{wall:0x0, ext:63768674848, loc:(*time.Location)(0x7984060)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63768674848, loc:(*time.Location)(0x7984060)}}, Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"sample-webhook-deployment-6bd9446d55\" is progressing."}}, CollisionCount:(*int32)(nil)}
STEP: Deploying the webhook service
STEP: Verifying the service has paired with the endpoint
Oct  1 08:47:35.763: INFO: Waiting for amount of service:e2e-test-webhook endpoints to be 1
[It] should unconditionally reject operations on fail closed webhook [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Registering a webhook that server cannot talk to, with fail closed policy, via the AdmissionRegistration API
STEP: create a namespace for the webhook
STEP: create a configmap should be unconditionally rejected by the webhook
[AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:47:36.700: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "webhook-7368" for this suite.
... skipping 2 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:101


• [SLOW TEST:12.105 seconds]
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
  should unconditionally reject operations on fail closed webhook [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]","total":-1,"completed":4,"skipped":21,"failed":0}

S
------------------------------
[BeforeEach] [sig-storage] PV Protection
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 22 lines ...
Oct  1 08:47:38.264: INFO: AfterEach: Cleaning up test resources.
Oct  1 08:47:38.264: INFO: pvc is nil
Oct  1 08:47:38.264: INFO: Deleting PersistentVolume "hostpath-vkj69"

•
------------------------------
{"msg":"PASSED [sig-storage] PV Protection Verify \"immediate\" deletion of a PV that is not bound to a PVC","total":-1,"completed":5,"skipped":47,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:38.409: INFO: Driver hostPath doesn't support PreprovisionedPV -- skipping
... skipping 25 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/subpath.go:38
STEP: Setting up data
[It] should support subpaths with configmap pod with mountPath of existing file [LinuxOnly] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating pod pod-subpath-test-configmap-442z
STEP: Creating a pod to test atomic-volume-subpath
Oct  1 08:47:14.656: INFO: Waiting up to 5m0s for pod "pod-subpath-test-configmap-442z" in namespace "subpath-7664" to be "Succeeded or Failed"
Oct  1 08:47:14.789: INFO: Pod "pod-subpath-test-configmap-442z": Phase="Pending", Reason="", readiness=false. Elapsed: 133.092178ms
Oct  1 08:47:16.923: INFO: Pod "pod-subpath-test-configmap-442z": Phase="Running", Reason="", readiness=true. Elapsed: 2.266233767s
Oct  1 08:47:19.056: INFO: Pod "pod-subpath-test-configmap-442z": Phase="Running", Reason="", readiness=true. Elapsed: 4.399585392s
Oct  1 08:47:21.189: INFO: Pod "pod-subpath-test-configmap-442z": Phase="Running", Reason="", readiness=true. Elapsed: 6.532957678s
Oct  1 08:47:23.324: INFO: Pod "pod-subpath-test-configmap-442z": Phase="Running", Reason="", readiness=true. Elapsed: 8.667370911s
Oct  1 08:47:25.457: INFO: Pod "pod-subpath-test-configmap-442z": Phase="Running", Reason="", readiness=true. Elapsed: 10.800897624s
Oct  1 08:47:27.591: INFO: Pod "pod-subpath-test-configmap-442z": Phase="Running", Reason="", readiness=true. Elapsed: 12.934225809s
Oct  1 08:47:29.725: INFO: Pod "pod-subpath-test-configmap-442z": Phase="Running", Reason="", readiness=true. Elapsed: 15.068956391s
Oct  1 08:47:31.861: INFO: Pod "pod-subpath-test-configmap-442z": Phase="Running", Reason="", readiness=true. Elapsed: 17.204363831s
Oct  1 08:47:33.994: INFO: Pod "pod-subpath-test-configmap-442z": Phase="Running", Reason="", readiness=true. Elapsed: 19.338023031s
Oct  1 08:47:36.128: INFO: Pod "pod-subpath-test-configmap-442z": Phase="Running", Reason="", readiness=true. Elapsed: 21.471850128s
Oct  1 08:47:38.262: INFO: Pod "pod-subpath-test-configmap-442z": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.605275728s
STEP: Saw pod success
Oct  1 08:47:38.262: INFO: Pod "pod-subpath-test-configmap-442z" satisfied condition "Succeeded or Failed"
Oct  1 08:47:38.395: INFO: Trying to get logs from node ip-172-20-60-245.ap-northeast-1.compute.internal pod pod-subpath-test-configmap-442z container test-container-subpath-configmap-442z: <nil>
STEP: delete the pod
Oct  1 08:47:38.674: INFO: Waiting for pod pod-subpath-test-configmap-442z to disappear
Oct  1 08:47:38.807: INFO: Pod pod-subpath-test-configmap-442z no longer exists
STEP: Deleting pod pod-subpath-test-configmap-442z
Oct  1 08:47:38.807: INFO: Deleting pod "pod-subpath-test-configmap-442z" in namespace "subpath-7664"
... skipping 8 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  Atomic writer volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/subpath.go:34
    should support subpaths with configmap pod with mountPath of existing file [LinuxOnly] [Conformance]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-storage] Subpath Atomic writer volumes should support subpaths with configmap pod with mountPath of existing file [LinuxOnly] [Conformance]","total":-1,"completed":1,"skipped":6,"failed":0}

S
------------------------------
[BeforeEach] [k8s.io] Probing container
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 67 lines ...
• [SLOW TEST:12.869 seconds]
[sig-api-machinery] ResourceQuota
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
  should create a ResourceQuota and capture the life of a persistent volume claim. [sig-storage]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/resource_quota.go:466
------------------------------
{"msg":"PASSED [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a persistent volume claim. [sig-storage]","total":-1,"completed":5,"skipped":35,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:40.298: INFO: Driver local doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 114 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:188
    One pod requesting one prebound PVC
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:205
      should be able to mount volume and read from pod1
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:228
------------------------------
{"msg":"PASSED [sig-storage] PersistentVolumes-local  [Volume type: dir-bindmounted] One pod requesting one prebound PVC should be able to mount volume and read from pod1","total":-1,"completed":4,"skipped":43,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ntfs)][sig-windows] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:41.159: INFO: Driver local doesn't support ntfs -- skipping
... skipping 123 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:47:41.799: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "events-9603" for this suite.

•
------------------------------
{"msg":"PASSED [sig-api-machinery] Events should ensure that an event can be fetched, patched, deleted, and listed [Conformance]","total":-1,"completed":6,"skipped":38,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:42.080: INFO: Only supported for providers [vsphere] (not aws)
[AfterEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 35 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:47:43.033: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "tables-1134" for this suite.

•
------------------------------
{"msg":"PASSED [sig-api-machinery] Servers with support for Table transformation should return generic metadata details across all namespaces for nodes","total":-1,"completed":7,"skipped":39,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
... skipping 259 lines ...
• [SLOW TEST:8.985 seconds]
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
  should not be able to mutate or prevent deletion of webhook configuration objects [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should not be able to mutate or prevent deletion of webhook configuration objects [Conformance]","total":-1,"completed":2,"skipped":7,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:48.227: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 42 lines ...
• [SLOW TEST:22.655 seconds]
[k8s.io] Probing container
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  should be restarted with a local redirect http liveness probe
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/container_probe.go:270
------------------------------
{"msg":"PASSED [k8s.io] Probing container should be restarted with a local redirect http liveness probe","total":-1,"completed":5,"skipped":31,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:48.780: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 220 lines ...
Oct  1 08:47:43.264: INFO: PersistentVolumeClaim pvc-tzjbw found but phase is Pending instead of Bound.
Oct  1 08:47:45.395: INFO: PersistentVolumeClaim pvc-tzjbw found and phase=Bound (10.787320103s)
Oct  1 08:47:45.395: INFO: Waiting up to 3m0s for PersistentVolume local-xphp7 to have phase Bound
Oct  1 08:47:45.526: INFO: PersistentVolume local-xphp7 found and phase=Bound (130.994489ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-tkn9
STEP: Creating a pod to test subpath
Oct  1 08:47:45.919: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-tkn9" in namespace "provisioning-1175" to be "Succeeded or Failed"
Oct  1 08:47:46.050: INFO: Pod "pod-subpath-test-preprovisionedpv-tkn9": Phase="Pending", Reason="", readiness=false. Elapsed: 130.635986ms
Oct  1 08:47:48.180: INFO: Pod "pod-subpath-test-preprovisionedpv-tkn9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.261328346s
Oct  1 08:47:50.311: INFO: Pod "pod-subpath-test-preprovisionedpv-tkn9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.392183662s
Oct  1 08:47:52.442: INFO: Pod "pod-subpath-test-preprovisionedpv-tkn9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.522750808s
STEP: Saw pod success
Oct  1 08:47:52.442: INFO: Pod "pod-subpath-test-preprovisionedpv-tkn9" satisfied condition "Succeeded or Failed"
Oct  1 08:47:52.573: INFO: Trying to get logs from node ip-172-20-60-245.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-tkn9 container test-container-subpath-preprovisionedpv-tkn9: <nil>
STEP: delete the pod
Oct  1 08:47:52.841: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-tkn9 to disappear
Oct  1 08:47:52.971: INFO: Pod pod-subpath-test-preprovisionedpv-tkn9 no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-tkn9
Oct  1 08:47:52.971: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-tkn9" in namespace "provisioning-1175"
... skipping 19 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support readOnly directory specified in the volumeMount
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:361
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir] [Testpattern: Pre-provisioned PV (default fs)] subPath should support readOnly directory specified in the volumeMount","total":-1,"completed":2,"skipped":3,"failed":0}
[BeforeEach] [Testpattern: Inline-volume (ext3)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:54.786: INFO: Driver csi-hostpath doesn't support InlineVolume -- skipping
[AfterEach] [Testpattern: Inline-volume (ext3)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 120 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:154

      Driver hostPathSymlink doesn't support DynamicPV -- skipping

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:173
------------------------------
{"msg":"PASSED [k8s.io] Probing container should not be ready until startupProbe succeeds","total":-1,"completed":2,"skipped":5,"failed":0}
[BeforeEach] [sig-storage] PersistentVolumes-local 
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:47:39.822: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename persistent-local-volumes-test
STEP: Waiting for a default service account to be provisioned in namespace
... skipping 59 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:188
    Two pods mounting a local volume one after the other
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:250
      should be able to write from pod1 and read from pod2
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:251
------------------------------
{"msg":"PASSED [sig-storage] PersistentVolumes-local  [Volume type: tmpfs] Two pods mounting a local volume one after the other should be able to write from pod1 and read from pod2","total":-1,"completed":3,"skipped":5,"failed":0}

SSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:55.562: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
... skipping 26 lines ...
[sig-storage] In-tree Volumes
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  [Driver: cinder]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Dynamic PV (immediate binding)] topology
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should fail to schedule a pod which has topologies that conflict with AllowedTopologies [BeforeEach]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Only supported for providers [openstack] (not aws)

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/drivers/in_tree.go:1094
------------------------------
... skipping 141 lines ...
• [SLOW TEST:70.724 seconds]
[sig-storage] Projected configMap
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_configmap.go:36
  updates should be reflected in volume [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-storage] Projected configMap updates should be reflected in volume [NodeConformance] [Conformance]","total":-1,"completed":2,"skipped":10,"failed":0}

SSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ext3)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:47:58.616: INFO: Driver local doesn't support InlineVolume -- skipping
... skipping 263 lines ...
Oct  1 08:47:37.424: INFO: PersistentVolume nfs-mx65k found and phase=Bound (127.717269ms)
Oct  1 08:47:37.553: INFO: Waiting up to 3m0s for PersistentVolumeClaims [pvc-bnk4x] to have phase Bound
Oct  1 08:47:37.681: INFO: PersistentVolumeClaim pvc-bnk4x found and phase=Bound (127.771667ms)
STEP: Checking pod has write access to PersistentVolumes
Oct  1 08:47:37.815: INFO: Creating nfs test pod
Oct  1 08:47:37.945: INFO: Pod should terminate with exitcode 0 (success)
Oct  1 08:47:37.945: INFO: Waiting up to 5m0s for pod "pvc-tester-zznl7" in namespace "pv-3226" to be "Succeeded or Failed"
Oct  1 08:47:38.073: INFO: Pod "pvc-tester-zznl7": Phase="Pending", Reason="", readiness=false. Elapsed: 127.944414ms
Oct  1 08:47:40.202: INFO: Pod "pvc-tester-zznl7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.25710103s
Oct  1 08:47:42.340: INFO: Pod "pvc-tester-zznl7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.39527063s
STEP: Saw pod success
Oct  1 08:47:42.340: INFO: Pod "pvc-tester-zznl7" satisfied condition "Succeeded or Failed"
Oct  1 08:47:42.340: INFO: Pod pvc-tester-zznl7 succeeded 
Oct  1 08:47:42.340: INFO: Deleting pod "pvc-tester-zznl7" in namespace "pv-3226"
Oct  1 08:47:42.472: INFO: Wait up to 5m0s for pod "pvc-tester-zznl7" to be fully deleted
Oct  1 08:47:42.734: INFO: Creating nfs test pod
Oct  1 08:47:42.862: INFO: Pod should terminate with exitcode 0 (success)
Oct  1 08:47:42.862: INFO: Waiting up to 5m0s for pod "pvc-tester-n9rrc" in namespace "pv-3226" to be "Succeeded or Failed"
Oct  1 08:47:42.991: INFO: Pod "pvc-tester-n9rrc": Phase="Pending", Reason="", readiness=false. Elapsed: 128.060623ms
Oct  1 08:47:45.119: INFO: Pod "pvc-tester-n9rrc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.256979862s
STEP: Saw pod success
Oct  1 08:47:45.120: INFO: Pod "pvc-tester-n9rrc" satisfied condition "Succeeded or Failed"
Oct  1 08:47:45.120: INFO: Pod pvc-tester-n9rrc succeeded 
Oct  1 08:47:45.120: INFO: Deleting pod "pvc-tester-n9rrc" in namespace "pv-3226"
Oct  1 08:47:45.253: INFO: Wait up to 5m0s for pod "pvc-tester-n9rrc" to be fully deleted
Oct  1 08:47:45.509: INFO: Creating nfs test pod
Oct  1 08:47:45.637: INFO: Pod should terminate with exitcode 0 (success)
Oct  1 08:47:45.637: INFO: Waiting up to 5m0s for pod "pvc-tester-s8w92" in namespace "pv-3226" to be "Succeeded or Failed"
Oct  1 08:47:45.766: INFO: Pod "pvc-tester-s8w92": Phase="Pending", Reason="", readiness=false. Elapsed: 128.077861ms
Oct  1 08:47:47.894: INFO: Pod "pvc-tester-s8w92": Phase="Pending", Reason="", readiness=false. Elapsed: 2.256783085s
Oct  1 08:47:50.023: INFO: Pod "pvc-tester-s8w92": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.385168762s
STEP: Saw pod success
Oct  1 08:47:50.023: INFO: Pod "pvc-tester-s8w92" satisfied condition "Succeeded or Failed"
Oct  1 08:47:50.023: INFO: Pod pvc-tester-s8w92 succeeded 
Oct  1 08:47:50.023: INFO: Deleting pod "pvc-tester-s8w92" in namespace "pv-3226"
Oct  1 08:47:50.155: INFO: Wait up to 5m0s for pod "pvc-tester-s8w92" to be fully deleted
STEP: Deleting PVCs to invoke reclaim policy
Oct  1 08:47:50.543: INFO: Deleting PVC pvc-6cp7m to trigger reclamation of PV nfs-mknlq
Oct  1 08:47:50.543: INFO: Deleting PersistentVolumeClaim "pvc-6cp7m"
... skipping 170 lines ...
Oct  1 08:47:22.718: INFO: Waiting up to 5m0s for PersistentVolumeClaims [pvc-24kvv] to have phase Bound
Oct  1 08:47:22.850: INFO: PersistentVolumeClaim pvc-24kvv found and phase=Bound (131.635656ms)
STEP: Deleting the previously created pod
Oct  1 08:47:35.516: INFO: Deleting pod "pvc-volume-tester-4l22m" in namespace "csi-mock-volumes-9739"
Oct  1 08:47:35.658: INFO: Wait up to 5m0s for pod "pvc-volume-tester-4l22m" to be fully deleted
STEP: Checking CSI driver logs
Oct  1 08:47:40.055: INFO: Found NodeUnpublishVolume: {json: {"Method":"/csi.v1.Node/NodeUnpublishVolume","Request":{"volume_id":"4","target_path":"/var/lib/kubelet/pods/bdcfad41-d09b-4988-9e49-b469565e43ed/volumes/kubernetes.io~csi/pvc-3e6c32b6-cf60-4469-b969-bc6f2db9bec8/mount"},"Response":{},"Error":"","FullError":null} Method:NodeUnpublishVolume Request:{VolumeContext:map[]} FullError:{Code:OK Message:} Error:}
STEP: Deleting pod pvc-volume-tester-4l22m
Oct  1 08:47:40.055: INFO: Deleting pod "pvc-volume-tester-4l22m" in namespace "csi-mock-volumes-9739"
STEP: Deleting claim pvc-24kvv
Oct  1 08:47:40.451: INFO: Waiting up to 2m0s for PersistentVolume pvc-3e6c32b6-cf60-4469-b969-bc6f2db9bec8 to get deleted
Oct  1 08:47:40.582: INFO: PersistentVolume pvc-3e6c32b6-cf60-4469-b969-bc6f2db9bec8 was removed
STEP: Deleting storageclass csi-mock-volumes-9739-sc
... skipping 44 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  CSI workload information using mock driver
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_mock_volume.go:437
    should not be passed when podInfoOnMount=nil
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_mock_volume.go:487
------------------------------
{"msg":"PASSED [sig-storage] CSI mock volume CSI workload information using mock driver should not be passed when podInfoOnMount=nil","total":-1,"completed":2,"skipped":5,"failed":0}
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:03.834: INFO: Only supported for node OS distro [gci ubuntu custom] (not debian)
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 158 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should be able to unmount after the subpath directory is deleted [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:441
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir-bindmounted] [Testpattern: Pre-provisioned PV (default fs)] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly]","total":-1,"completed":2,"skipped":7,"failed":0}

SS
------------------------------
[BeforeEach] [k8s.io] [sig-node] AppArmor
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 56 lines ...
• [SLOW TEST:7.175 seconds]
[sig-apps] Job
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23
  should adopt matching orphans and release non-matching pods [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-apps] Job should adopt matching orphans and release non-matching pods [Conformance]","total":-1,"completed":3,"skipped":25,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ntfs)][sig-windows] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:05.846: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 127 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  storage capacity
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_mock_volume.go:881
    unlimited
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_mock_volume.go:934
------------------------------
{"msg":"PASSED [sig-storage] CSI mock volume storage capacity unlimited","total":-1,"completed":2,"skipped":21,"failed":0}

S
------------------------------
[BeforeEach] [sig-network] Services
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 79 lines ...
      Only supported for providers [gce gke] (not aws)

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/drivers/in_tree.go:1304
------------------------------
SSSS
------------------------------
{"msg":"PASSED [sig-storage] PersistentVolumes NFS with multiple PVs and PVCs all in same ns should create 3 PVs and 3 PVCs: test write access","total":-1,"completed":2,"skipped":7,"failed":0}
[BeforeEach] [sig-node] Downward API
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:48:03.281: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename downward-api
STEP: Waiting for a default service account to be provisioned in namespace
[It] should provide container's limits.cpu/memory and requests.cpu/memory as env vars [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating a pod to test downward api env vars
Oct  1 08:48:04.054: INFO: Waiting up to 5m0s for pod "downward-api-07e2e200-2cf4-4897-b510-64a57ab032bc" in namespace "downward-api-3213" to be "Succeeded or Failed"
Oct  1 08:48:04.188: INFO: Pod "downward-api-07e2e200-2cf4-4897-b510-64a57ab032bc": Phase="Pending", Reason="", readiness=false. Elapsed: 133.430303ms
Oct  1 08:48:06.332: INFO: Pod "downward-api-07e2e200-2cf4-4897-b510-64a57ab032bc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.277331295s
STEP: Saw pod success
Oct  1 08:48:06.332: INFO: Pod "downward-api-07e2e200-2cf4-4897-b510-64a57ab032bc" satisfied condition "Succeeded or Failed"
Oct  1 08:48:06.460: INFO: Trying to get logs from node ip-172-20-35-235.ap-northeast-1.compute.internal pod downward-api-07e2e200-2cf4-4897-b510-64a57ab032bc container dapi-container: <nil>
STEP: delete the pod
Oct  1 08:48:06.724: INFO: Waiting for pod downward-api-07e2e200-2cf4-4897-b510-64a57ab032bc to disappear
Oct  1 08:48:06.852: INFO: Pod downward-api-07e2e200-2cf4-4897-b510-64a57ab032bc no longer exists
[AfterEach] [sig-node] Downward API
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:48:06.852: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "downward-api-3213" for this suite.

•
------------------------------
{"msg":"PASSED [sig-node] Downward API should provide container's limits.cpu/memory and requests.cpu/memory as env vars [NodeConformance] [Conformance]","total":-1,"completed":3,"skipped":7,"failed":0}
[BeforeEach] [Testpattern: Inline-volume (ext3)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:07.120: INFO: Driver local doesn't support InlineVolume -- skipping
[AfterEach] [Testpattern: Inline-volume (ext3)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 221 lines ...
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [sig-storage] Downward API volume
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/downwardapi_volume.go:41
[It] should provide podname only [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating a pod to test downward API volume plugin
Oct  1 08:48:04.711: INFO: Waiting up to 5m0s for pod "downwardapi-volume-5dc4ddd5-2cb2-4684-9742-1be500b29b4e" in namespace "downward-api-885" to be "Succeeded or Failed"
Oct  1 08:48:04.850: INFO: Pod "downwardapi-volume-5dc4ddd5-2cb2-4684-9742-1be500b29b4e": Phase="Pending", Reason="", readiness=false. Elapsed: 139.392896ms
Oct  1 08:48:06.983: INFO: Pod "downwardapi-volume-5dc4ddd5-2cb2-4684-9742-1be500b29b4e": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.272300571s
STEP: Saw pod success
Oct  1 08:48:06.983: INFO: Pod "downwardapi-volume-5dc4ddd5-2cb2-4684-9742-1be500b29b4e" satisfied condition "Succeeded or Failed"
Oct  1 08:48:07.115: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod downwardapi-volume-5dc4ddd5-2cb2-4684-9742-1be500b29b4e container client-container: <nil>
STEP: delete the pod
Oct  1 08:48:07.395: INFO: Waiting for pod downwardapi-volume-5dc4ddd5-2cb2-4684-9742-1be500b29b4e to disappear
Oct  1 08:48:07.527: INFO: Pod downwardapi-volume-5dc4ddd5-2cb2-4684-9742-1be500b29b4e no longer exists
[AfterEach] [sig-storage] Downward API volume
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:48:07.527: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "downward-api-885" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] Downward API volume should provide podname only [NodeConformance] [Conformance]","total":-1,"completed":3,"skipped":18,"failed":0}
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:07.801: INFO: Driver local doesn't support InlineVolume -- skipping
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 55 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:48:08.276: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "tables-7533" for this suite.

•
------------------------------
{"msg":"PASSED [sig-api-machinery] Servers with support for Table transformation should return pod details","total":-1,"completed":4,"skipped":32,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ext4)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:08.548: INFO: Driver local doesn't support InlineVolume -- skipping
... skipping 167 lines ...
      Only supported for providers [azure] (not aws)

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/drivers/in_tree.go:1570
------------------------------
S
------------------------------
{"msg":"PASSED [sig-network] Services should check NodePort out-of-range","total":-1,"completed":3,"skipped":9,"failed":0}
[BeforeEach] [k8s.io] Security Context
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:48:06.058: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename security-context-test
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [k8s.io] Security Context
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/security_context.go:41
[It] should not allow privilege escalation when false [LinuxOnly] [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
Oct  1 08:48:06.875: INFO: Waiting up to 5m0s for pod "alpine-nnp-false-32aaf354-de47-46fd-adb2-0ad47707652f" in namespace "security-context-test-4287" to be "Succeeded or Failed"
Oct  1 08:48:07.010: INFO: Pod "alpine-nnp-false-32aaf354-de47-46fd-adb2-0ad47707652f": Phase="Pending", Reason="", readiness=false. Elapsed: 135.449536ms
Oct  1 08:48:09.146: INFO: Pod "alpine-nnp-false-32aaf354-de47-46fd-adb2-0ad47707652f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.271181241s
Oct  1 08:48:11.282: INFO: Pod "alpine-nnp-false-32aaf354-de47-46fd-adb2-0ad47707652f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.406764469s
Oct  1 08:48:11.282: INFO: Pod "alpine-nnp-false-32aaf354-de47-46fd-adb2-0ad47707652f" satisfied condition "Succeeded or Failed"
[AfterEach] [k8s.io] Security Context
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:48:11.419: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "security-context-test-4287" for this suite.


... skipping 2 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  when creating containers with AllowPrivilegeEscalation
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/security_context.go:291
    should not allow privilege escalation when false [LinuxOnly] [NodeConformance] [Conformance]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [k8s.io] Security Context when creating containers with AllowPrivilegeEscalation should not allow privilege escalation when false [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":4,"skipped":9,"failed":0}
[BeforeEach] [Testpattern: Inline-volume (default fs)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:11.701: INFO: Only supported for providers [openstack] (not aws)
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 138 lines ...
[BeforeEach] [k8s.io] Pod Container lifecycle
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/node/pods.go:446
[It] should not create extra sandbox if all containers are done
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/node/pods.go:450
STEP: creating the pod that should always exit 0
STEP: submitting the pod to kubernetes
Oct  1 08:48:05.347: INFO: Waiting up to 5m0s for pod "pod-always-succeed8a456fea-21a4-4da3-91f2-d892a5b2346b" in namespace "pods-7283" to be "Succeeded or Failed"
Oct  1 08:48:05.481: INFO: Pod "pod-always-succeed8a456fea-21a4-4da3-91f2-d892a5b2346b": Phase="Pending", Reason="", readiness=false. Elapsed: 134.074927ms
Oct  1 08:48:07.616: INFO: Pod "pod-always-succeed8a456fea-21a4-4da3-91f2-d892a5b2346b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.268961673s
Oct  1 08:48:09.751: INFO: Pod "pod-always-succeed8a456fea-21a4-4da3-91f2-d892a5b2346b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.40478072s
STEP: Saw pod success
Oct  1 08:48:09.752: INFO: Pod "pod-always-succeed8a456fea-21a4-4da3-91f2-d892a5b2346b" satisfied condition "Succeeded or Failed"
STEP: Getting events about the pod
STEP: Checking events about the pod
STEP: deleting the pod
[AfterEach] [k8s.io] [sig-node] Pods Extended
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:48:12.025: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
... skipping 5 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  [k8s.io] Pod Container lifecycle
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
    should not create extra sandbox if all containers are done
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/node/pods.go:450
------------------------------
{"msg":"PASSED [k8s.io] [sig-node] Pods Extended [k8s.io] Pod Container lifecycle should not create extra sandbox if all containers are done","total":-1,"completed":4,"skipped":39,"failed":0}

SSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:12.324: INFO: Only supported for providers [gce gke] (not aws)
... skipping 91 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:48:15.106: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "networkpolicies-9084" for this suite.

•
------------------------------
{"msg":"PASSED [sig-network] NetworkPolicy API should support creating NetworkPolicy API operations","total":-1,"completed":5,"skipped":31,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:15.396: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 130 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  CSI FSGroupPolicy [LinuxOnly]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_mock_volume.go:1410
    should modify fsGroup if fsGroupPolicy=default
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_mock_volume.go:1434
------------------------------
{"msg":"PASSED [sig-storage] CSI mock volume CSI FSGroupPolicy [LinuxOnly] should modify fsGroup if fsGroupPolicy=default","total":-1,"completed":2,"skipped":17,"failed":0}

SSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:16.537: INFO: Driver hostPathSymlink doesn't support DynamicPV -- skipping
... skipping 32 lines ...
Oct  1 08:47:34.061: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9959-aws-scs45gg
STEP: creating a claim
Oct  1 08:47:34.194: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-lsrp
STEP: Creating a pod to test subpath
Oct  1 08:47:34.597: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-lsrp" in namespace "provisioning-9959" to be "Succeeded or Failed"
Oct  1 08:47:34.733: INFO: Pod "pod-subpath-test-dynamicpv-lsrp": Phase="Pending", Reason="", readiness=false. Elapsed: 136.273441ms
Oct  1 08:47:36.867: INFO: Pod "pod-subpath-test-dynamicpv-lsrp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.269704598s
Oct  1 08:47:39.001: INFO: Pod "pod-subpath-test-dynamicpv-lsrp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.404201563s
Oct  1 08:47:41.134: INFO: Pod "pod-subpath-test-dynamicpv-lsrp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.537521277s
Oct  1 08:47:43.269: INFO: Pod "pod-subpath-test-dynamicpv-lsrp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.671978046s
Oct  1 08:47:45.403: INFO: Pod "pod-subpath-test-dynamicpv-lsrp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.805862123s
Oct  1 08:47:47.536: INFO: Pod "pod-subpath-test-dynamicpv-lsrp": Phase="Pending", Reason="", readiness=false. Elapsed: 12.939296082s
Oct  1 08:47:49.669: INFO: Pod "pod-subpath-test-dynamicpv-lsrp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.072399514s
STEP: Saw pod success
Oct  1 08:47:49.669: INFO: Pod "pod-subpath-test-dynamicpv-lsrp" satisfied condition "Succeeded or Failed"
Oct  1 08:47:49.802: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod pod-subpath-test-dynamicpv-lsrp container test-container-subpath-dynamicpv-lsrp: <nil>
STEP: delete the pod
Oct  1 08:47:50.076: INFO: Waiting for pod pod-subpath-test-dynamicpv-lsrp to disappear
Oct  1 08:47:50.212: INFO: Pod pod-subpath-test-dynamicpv-lsrp no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-lsrp
Oct  1 08:47:50.212: INFO: Deleting pod "pod-subpath-test-dynamicpv-lsrp" in namespace "provisioning-9959"
... skipping 22 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Dynamic PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support existing single file [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:216
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: aws] [Testpattern: Dynamic PV (default fs)] subPath should support existing single file [LinuxOnly]","total":-1,"completed":2,"skipped":5,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:17.113: INFO: Driver local doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 68 lines ...
• [SLOW TEST:10.220 seconds]
[sig-network] DNS
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
  should support configurable pod resolv.conf
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns.go:457
------------------------------
{"msg":"PASSED [sig-network] DNS should support configurable pod resolv.conf","total":-1,"completed":4,"skipped":24,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:18.080: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 52 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:48:18.368: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "security-context-test-9213" for this suite.

•
------------------------------
{"msg":"PASSED [k8s.io] Security Context When creating a container with runAsNonRoot should not run without a specified user ID","total":-1,"completed":6,"skipped":36,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:18.667: INFO: Driver local doesn't support InlineVolume -- skipping
... skipping 191 lines ...
Oct  1 08:47:30.483: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3889-aws-scrhz5j
STEP: creating a claim
Oct  1 08:47:30.614: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-m5f2
STEP: Creating a pod to test subpath
Oct  1 08:47:31.005: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-m5f2" in namespace "provisioning-3889" to be "Succeeded or Failed"
Oct  1 08:47:31.135: INFO: Pod "pod-subpath-test-dynamicpv-m5f2": Phase="Pending", Reason="", readiness=false. Elapsed: 129.461139ms
Oct  1 08:47:33.264: INFO: Pod "pod-subpath-test-dynamicpv-m5f2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.258692919s
Oct  1 08:47:35.393: INFO: Pod "pod-subpath-test-dynamicpv-m5f2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.387780575s
Oct  1 08:47:37.524: INFO: Pod "pod-subpath-test-dynamicpv-m5f2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.518487042s
Oct  1 08:47:39.653: INFO: Pod "pod-subpath-test-dynamicpv-m5f2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.647684922s
Oct  1 08:47:41.782: INFO: Pod "pod-subpath-test-dynamicpv-m5f2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.776664706s
Oct  1 08:47:43.911: INFO: Pod "pod-subpath-test-dynamicpv-m5f2": Phase="Pending", Reason="", readiness=false. Elapsed: 12.905653259s
Oct  1 08:47:46.040: INFO: Pod "pod-subpath-test-dynamicpv-m5f2": Phase="Pending", Reason="", readiness=false. Elapsed: 15.034840468s
Oct  1 08:47:48.170: INFO: Pod "pod-subpath-test-dynamicpv-m5f2": Phase="Pending", Reason="", readiness=false. Elapsed: 17.164162258s
Oct  1 08:47:50.299: INFO: Pod "pod-subpath-test-dynamicpv-m5f2": Phase="Pending", Reason="", readiness=false. Elapsed: 19.293344262s
Oct  1 08:47:52.428: INFO: Pod "pod-subpath-test-dynamicpv-m5f2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.422534196s
STEP: Saw pod success
Oct  1 08:47:52.428: INFO: Pod "pod-subpath-test-dynamicpv-m5f2" satisfied condition "Succeeded or Failed"
Oct  1 08:47:52.559: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod pod-subpath-test-dynamicpv-m5f2 container test-container-subpath-dynamicpv-m5f2: <nil>
STEP: delete the pod
Oct  1 08:47:52.823: INFO: Waiting for pod pod-subpath-test-dynamicpv-m5f2 to disappear
Oct  1 08:47:52.953: INFO: Pod pod-subpath-test-dynamicpv-m5f2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-m5f2
Oct  1 08:47:52.954: INFO: Deleting pod "pod-subpath-test-dynamicpv-m5f2" in namespace "provisioning-3889"
... skipping 22 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Dynamic PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support readOnly file specified in the volumeMount [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:376
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: aws] [Testpattern: Dynamic PV (default fs)] subPath should support readOnly file specified in the volumeMount [LinuxOnly]","total":-1,"completed":4,"skipped":21,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:19.816: INFO: Driver hostPathSymlink doesn't support PreprovisionedPV -- skipping
... skipping 56 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:48:20.220: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "replication-controller-3412" for this suite.

•
------------------------------
{"msg":"PASSED [sig-apps] ReplicationController should release no longer matching pods [Conformance]","total":-1,"completed":7,"skipped":60,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:20.531: INFO: Only supported for providers [azure] (not aws)
... skipping 40 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/runtime.go:41
    when running a container with a new image
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/runtime.go:266
      should be able to pull from private registry with secret [NodeConformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/runtime.go:393
------------------------------
{"msg":"PASSED [k8s.io] Container Runtime blackbox test when running a container with a new image should be able to pull from private registry with secret [NodeConformance]","total":-1,"completed":5,"skipped":55,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 21 lines ...
Oct  1 08:48:13.542: INFO: PersistentVolumeClaim pvc-2r7sw found but phase is Pending instead of Bound.
Oct  1 08:48:15.676: INFO: PersistentVolumeClaim pvc-2r7sw found and phase=Bound (15.072925233s)
Oct  1 08:48:15.676: INFO: Waiting up to 3m0s for PersistentVolume local-2pl8r to have phase Bound
Oct  1 08:48:15.810: INFO: PersistentVolume local-2pl8r found and phase=Bound (133.414157ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-44bv
STEP: Creating a pod to test subpath
Oct  1 08:48:16.211: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-44bv" in namespace "provisioning-9088" to be "Succeeded or Failed"
Oct  1 08:48:16.362: INFO: Pod "pod-subpath-test-preprovisionedpv-44bv": Phase="Pending", Reason="", readiness=false. Elapsed: 150.330023ms
Oct  1 08:48:18.496: INFO: Pod "pod-subpath-test-preprovisionedpv-44bv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.285027623s
STEP: Saw pod success
Oct  1 08:48:18.497: INFO: Pod "pod-subpath-test-preprovisionedpv-44bv" satisfied condition "Succeeded or Failed"
Oct  1 08:48:18.631: INFO: Trying to get logs from node ip-172-20-41-255.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-44bv container test-container-subpath-preprovisionedpv-44bv: <nil>
STEP: delete the pod
Oct  1 08:48:18.921: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-44bv to disappear
Oct  1 08:48:19.055: INFO: Pod pod-subpath-test-preprovisionedpv-44bv no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-44bv
Oct  1 08:48:19.055: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-44bv" in namespace "provisioning-9088"
... skipping 21 lines ...
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support existing single file [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:216
------------------------------
S
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir-link] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing single file [LinuxOnly]","total":-1,"completed":3,"skipped":11,"failed":0}

SSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ext4)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:20.983: INFO: Only supported for node OS distro [gci ubuntu custom] (not debian)
... skipping 73 lines ...
• [SLOW TEST:25.462 seconds]
[k8s.io] Probing container
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  with readiness probe should not be ready before initial delay and never restart [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [k8s.io] Probing container with readiness probe should not be ready before initial delay and never restart [NodeConformance] [Conformance]","total":-1,"completed":4,"skipped":16,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:21.086: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 63 lines ...
Oct  1 08:47:43.932: INFO: PersistentVolumeClaim pvc-gvxv7 found but phase is Pending instead of Bound.
Oct  1 08:47:46.063: INFO: PersistentVolumeClaim pvc-gvxv7 found and phase=Bound (6.523510103s)
Oct  1 08:47:46.063: INFO: Waiting up to 3m0s for PersistentVolume aws-gjx5s to have phase Bound
Oct  1 08:47:46.194: INFO: PersistentVolume aws-gjx5s found and phase=Bound (130.931963ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-7k5d
STEP: Creating a pod to test exec-volume-test
Oct  1 08:47:46.587: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-7k5d" in namespace "volume-2717" to be "Succeeded or Failed"
Oct  1 08:47:46.718: INFO: Pod "exec-volume-test-preprovisionedpv-7k5d": Phase="Pending", Reason="", readiness=false. Elapsed: 130.826194ms
Oct  1 08:47:48.849: INFO: Pod "exec-volume-test-preprovisionedpv-7k5d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.262147006s
Oct  1 08:47:50.980: INFO: Pod "exec-volume-test-preprovisionedpv-7k5d": Phase="Pending", Reason="", readiness=false. Elapsed: 4.393319503s
Oct  1 08:47:53.111: INFO: Pod "exec-volume-test-preprovisionedpv-7k5d": Phase="Pending", Reason="", readiness=false. Elapsed: 6.524435685s
Oct  1 08:47:55.243: INFO: Pod "exec-volume-test-preprovisionedpv-7k5d": Phase="Pending", Reason="", readiness=false. Elapsed: 8.655706645s
Oct  1 08:47:57.374: INFO: Pod "exec-volume-test-preprovisionedpv-7k5d": Phase="Pending", Reason="", readiness=false. Elapsed: 10.787247536s
Oct  1 08:47:59.505: INFO: Pod "exec-volume-test-preprovisionedpv-7k5d": Phase="Pending", Reason="", readiness=false. Elapsed: 12.918148115s
Oct  1 08:48:01.637: INFO: Pod "exec-volume-test-preprovisionedpv-7k5d": Phase="Pending", Reason="", readiness=false. Elapsed: 15.050232595s
Oct  1 08:48:03.770: INFO: Pod "exec-volume-test-preprovisionedpv-7k5d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.183153809s
STEP: Saw pod success
Oct  1 08:48:03.770: INFO: Pod "exec-volume-test-preprovisionedpv-7k5d" satisfied condition "Succeeded or Failed"
Oct  1 08:48:03.901: INFO: Trying to get logs from node ip-172-20-60-245.ap-northeast-1.compute.internal pod exec-volume-test-preprovisionedpv-7k5d container exec-container-preprovisionedpv-7k5d: <nil>
STEP: delete the pod
Oct  1 08:48:04.189: INFO: Waiting for pod exec-volume-test-preprovisionedpv-7k5d to disappear
Oct  1 08:48:04.328: INFO: Pod exec-volume-test-preprovisionedpv-7k5d no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-7k5d
Oct  1 08:48:04.328: INFO: Deleting pod "exec-volume-test-preprovisionedpv-7k5d" in namespace "volume-2717"
STEP: Deleting pv and pvc
Oct  1 08:48:04.467: INFO: Deleting PersistentVolumeClaim "pvc-gvxv7"
Oct  1 08:48:04.599: INFO: Deleting PersistentVolume "aws-gjx5s"
Oct  1 08:48:05.014: INFO: Couldn't delete PD "aws://ap-northeast-1a/vol-0a5219216384eec08", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a5219216384eec08 is currently attached to i-029bd822c8d7a82f8
	status code: 400, request id: 4b0535fa-c7e9-42b4-aebc-ab1fd9d26d33
Oct  1 08:48:10.697: INFO: Couldn't delete PD "aws://ap-northeast-1a/vol-0a5219216384eec08", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a5219216384eec08 is currently attached to i-029bd822c8d7a82f8
	status code: 400, request id: e5f7432b-8c70-4681-ae4c-50c415a3a4ac
Oct  1 08:48:16.454: INFO: Couldn't delete PD "aws://ap-northeast-1a/vol-0a5219216384eec08", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a5219216384eec08 is currently attached to i-029bd822c8d7a82f8
	status code: 400, request id: dfed379c-bbdc-43de-b2e2-736a4bd860dc
Oct  1 08:48:22.193: INFO: Successfully deleted PD "aws://ap-northeast-1a/vol-0a5219216384eec08".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:48:22.194: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2717" for this suite.
... skipping 6 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] volumes
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should allow exec of files on the volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:192
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: aws] [Testpattern: Pre-provisioned PV (default fs)] volumes should allow exec of files on the volume","total":-1,"completed":5,"skipped":22,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:22.468: INFO: Only supported for providers [gce gke] (not aws)
[AfterEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 46 lines ...
[It] should support existing single file [LinuxOnly]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:216
Oct  1 08:48:18.777: INFO: In-tree plugin kubernetes.io/empty-dir is not migrated, not validating any metrics
Oct  1 08:48:18.777: INFO: Creating resource for inline volume
STEP: Creating pod pod-subpath-test-inlinevolume-t489
STEP: Creating a pod to test subpath
Oct  1 08:48:18.917: INFO: Waiting up to 5m0s for pod "pod-subpath-test-inlinevolume-t489" in namespace "provisioning-1807" to be "Succeeded or Failed"
Oct  1 08:48:19.049: INFO: Pod "pod-subpath-test-inlinevolume-t489": Phase="Pending", Reason="", readiness=false. Elapsed: 132.430079ms
Oct  1 08:48:21.183: INFO: Pod "pod-subpath-test-inlinevolume-t489": Phase="Pending", Reason="", readiness=false. Elapsed: 2.266048025s
Oct  1 08:48:23.315: INFO: Pod "pod-subpath-test-inlinevolume-t489": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.398450869s
STEP: Saw pod success
Oct  1 08:48:23.315: INFO: Pod "pod-subpath-test-inlinevolume-t489" satisfied condition "Succeeded or Failed"
Oct  1 08:48:23.447: INFO: Trying to get logs from node ip-172-20-35-235.ap-northeast-1.compute.internal pod pod-subpath-test-inlinevolume-t489 container test-container-subpath-inlinevolume-t489: <nil>
STEP: delete the pod
Oct  1 08:48:23.722: INFO: Waiting for pod pod-subpath-test-inlinevolume-t489 to disappear
Oct  1 08:48:23.853: INFO: Pod pod-subpath-test-inlinevolume-t489 no longer exists
STEP: Deleting pod pod-subpath-test-inlinevolume-t489
Oct  1 08:48:23.853: INFO: Deleting pod "pod-subpath-test-inlinevolume-t489" in namespace "provisioning-1807"
... skipping 12 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Inline-volume (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support existing single file [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:216
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: emptydir] [Testpattern: Inline-volume (default fs)] subPath should support existing single file [LinuxOnly]","total":-1,"completed":5,"skipped":28,"failed":0}
[BeforeEach] [Testpattern: Inline-volume (ext4)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:24.391: INFO: Driver emptydir doesn't support ext4 -- skipping
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 152 lines ...
Oct  1 08:48:21.174: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename emptydir
STEP: Waiting for a default service account to be provisioned in namespace
[It] should support (root,0777,default) [LinuxOnly] [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating a pod to test emptydir 0777 on node default medium
Oct  1 08:48:21.975: INFO: Waiting up to 5m0s for pod "pod-e18e4c5c-8801-4f06-9664-4e56fb2403d0" in namespace "emptydir-1342" to be "Succeeded or Failed"
Oct  1 08:48:22.111: INFO: Pod "pod-e18e4c5c-8801-4f06-9664-4e56fb2403d0": Phase="Pending", Reason="", readiness=false. Elapsed: 135.958745ms
Oct  1 08:48:24.243: INFO: Pod "pod-e18e4c5c-8801-4f06-9664-4e56fb2403d0": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.268644654s
STEP: Saw pod success
Oct  1 08:48:24.243: INFO: Pod "pod-e18e4c5c-8801-4f06-9664-4e56fb2403d0" satisfied condition "Succeeded or Failed"
Oct  1 08:48:24.375: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod pod-e18e4c5c-8801-4f06-9664-4e56fb2403d0 container test-container: <nil>
STEP: delete the pod
Oct  1 08:48:24.650: INFO: Waiting for pod pod-e18e4c5c-8801-4f06-9664-4e56fb2403d0 to disappear
Oct  1 08:48:24.783: INFO: Pod pod-e18e4c5c-8801-4f06-9664-4e56fb2403d0 no longer exists
[AfterEach] [sig-storage] EmptyDir volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:48:24.783: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "emptydir-1342" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] EmptyDir volumes should support (root,0777,default) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":5,"skipped":27,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:25.066: INFO: Only supported for node OS distro [gci ubuntu custom] (not debian)
... skipping 38 lines ...
Oct  1 08:48:13.069: INFO: PersistentVolumeClaim pvc-gkgkd found but phase is Pending instead of Bound.
Oct  1 08:48:15.198: INFO: PersistentVolumeClaim pvc-gkgkd found and phase=Bound (2.256997693s)
Oct  1 08:48:15.198: INFO: Waiting up to 3m0s for PersistentVolume local-wn6wl to have phase Bound
Oct  1 08:48:15.326: INFO: PersistentVolume local-wn6wl found and phase=Bound (128.110092ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-b76c
STEP: Creating a pod to test subpath
Oct  1 08:48:15.712: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-b76c" in namespace "provisioning-7032" to be "Succeeded or Failed"
Oct  1 08:48:15.840: INFO: Pod "pod-subpath-test-preprovisionedpv-b76c": Phase="Pending", Reason="", readiness=false. Elapsed: 128.334307ms
Oct  1 08:48:17.970: INFO: Pod "pod-subpath-test-preprovisionedpv-b76c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.257600734s
Oct  1 08:48:20.105: INFO: Pod "pod-subpath-test-preprovisionedpv-b76c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.393304122s
STEP: Saw pod success
Oct  1 08:48:20.105: INFO: Pod "pod-subpath-test-preprovisionedpv-b76c" satisfied condition "Succeeded or Failed"
Oct  1 08:48:20.234: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-b76c container test-container-subpath-preprovisionedpv-b76c: <nil>
STEP: delete the pod
Oct  1 08:48:20.500: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-b76c to disappear
Oct  1 08:48:20.630: INFO: Pod pod-subpath-test-preprovisionedpv-b76c no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-b76c
Oct  1 08:48:20.630: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-b76c" in namespace "provisioning-7032"
STEP: Creating pod pod-subpath-test-preprovisionedpv-b76c
STEP: Creating a pod to test subpath
Oct  1 08:48:20.890: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-b76c" in namespace "provisioning-7032" to be "Succeeded or Failed"
Oct  1 08:48:21.019: INFO: Pod "pod-subpath-test-preprovisionedpv-b76c": Phase="Pending", Reason="", readiness=false. Elapsed: 129.199777ms
Oct  1 08:48:23.149: INFO: Pod "pod-subpath-test-preprovisionedpv-b76c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.258682299s
STEP: Saw pod success
Oct  1 08:48:23.149: INFO: Pod "pod-subpath-test-preprovisionedpv-b76c" satisfied condition "Succeeded or Failed"
Oct  1 08:48:23.278: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-b76c container test-container-subpath-preprovisionedpv-b76c: <nil>
STEP: delete the pod
Oct  1 08:48:23.542: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-b76c to disappear
Oct  1 08:48:23.670: INFO: Pod pod-subpath-test-preprovisionedpv-b76c no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-b76c
Oct  1 08:48:23.670: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-b76c" in namespace "provisioning-7032"
... skipping 19 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support existing directories when readOnly specified in the volumeSource
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:391
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing directories when readOnly specified in the volumeSource","total":-1,"completed":5,"skipped":51,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:25.470: INFO: Only supported for providers [openstack] (not aws)
[AfterEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 155 lines ...
Oct  1 08:48:14.677: INFO: PersistentVolumeClaim pvc-jwmm6 found but phase is Pending instead of Bound.
Oct  1 08:48:16.813: INFO: PersistentVolumeClaim pvc-jwmm6 found and phase=Bound (6.557255254s)
Oct  1 08:48:16.813: INFO: Waiting up to 3m0s for PersistentVolume local-7g6nh to have phase Bound
Oct  1 08:48:16.948: INFO: PersistentVolume local-7g6nh found and phase=Bound (135.030367ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-ktnj
STEP: Creating a pod to test subpath
Oct  1 08:48:17.357: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-ktnj" in namespace "provisioning-2245" to be "Succeeded or Failed"
Oct  1 08:48:17.492: INFO: Pod "pod-subpath-test-preprovisionedpv-ktnj": Phase="Pending", Reason="", readiness=false. Elapsed: 134.999944ms
Oct  1 08:48:19.628: INFO: Pod "pod-subpath-test-preprovisionedpv-ktnj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.270648796s
Oct  1 08:48:21.763: INFO: Pod "pod-subpath-test-preprovisionedpv-ktnj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.405714833s
Oct  1 08:48:23.898: INFO: Pod "pod-subpath-test-preprovisionedpv-ktnj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.540606872s
STEP: Saw pod success
Oct  1 08:48:23.898: INFO: Pod "pod-subpath-test-preprovisionedpv-ktnj" satisfied condition "Succeeded or Failed"
Oct  1 08:48:24.032: INFO: Trying to get logs from node ip-172-20-35-235.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-ktnj container test-container-subpath-preprovisionedpv-ktnj: <nil>
STEP: delete the pod
Oct  1 08:48:24.310: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-ktnj to disappear
Oct  1 08:48:24.445: INFO: Pod pod-subpath-test-preprovisionedpv-ktnj no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-ktnj
Oct  1 08:48:24.445: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-ktnj" in namespace "provisioning-2245"
... skipping 19 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support existing single file [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:216
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing single file [LinuxOnly]","total":-1,"completed":4,"skipped":29,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext3)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:26.308: INFO: Driver hostPath doesn't support PreprovisionedPV -- skipping
... skipping 86 lines ...
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] when FSGroup is specified [LinuxOnly] [NodeFeature:FSGroup]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/empty_dir.go:50
[It] volume on tmpfs should have the correct mode using FSGroup
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/empty_dir.go:75
STEP: Creating a pod to test emptydir volume type on tmpfs
Oct  1 08:48:21.848: INFO: Waiting up to 5m0s for pod "pod-33eca2f2-9e98-42f5-b81c-c73a656d3613" in namespace "emptydir-2275" to be "Succeeded or Failed"
Oct  1 08:48:21.981: INFO: Pod "pod-33eca2f2-9e98-42f5-b81c-c73a656d3613": Phase="Pending", Reason="", readiness=false. Elapsed: 132.916894ms
Oct  1 08:48:24.114: INFO: Pod "pod-33eca2f2-9e98-42f5-b81c-c73a656d3613": Phase="Pending", Reason="", readiness=false. Elapsed: 2.266689862s
Oct  1 08:48:26.261: INFO: Pod "pod-33eca2f2-9e98-42f5-b81c-c73a656d3613": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.413633653s
STEP: Saw pod success
Oct  1 08:48:26.261: INFO: Pod "pod-33eca2f2-9e98-42f5-b81c-c73a656d3613" satisfied condition "Succeeded or Failed"
Oct  1 08:48:26.405: INFO: Trying to get logs from node ip-172-20-35-235.ap-northeast-1.compute.internal pod pod-33eca2f2-9e98-42f5-b81c-c73a656d3613 container test-container: <nil>
STEP: delete the pod
Oct  1 08:48:26.678: INFO: Waiting for pod pod-33eca2f2-9e98-42f5-b81c-c73a656d3613 to disappear
Oct  1 08:48:26.812: INFO: Pod pod-33eca2f2-9e98-42f5-b81c-c73a656d3613 no longer exists
[AfterEach] [sig-storage] EmptyDir volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 6 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/empty_dir.go:45
  when FSGroup is specified [LinuxOnly] [NodeFeature:FSGroup]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/empty_dir.go:48
    volume on tmpfs should have the correct mode using FSGroup
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/empty_dir.go:75
------------------------------
{"msg":"PASSED [sig-storage] EmptyDir volumes when FSGroup is specified [LinuxOnly] [NodeFeature:FSGroup] volume on tmpfs should have the correct mode using FSGroup","total":-1,"completed":4,"skipped":17,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:27.104: INFO: Driver emptydir doesn't support DynamicPV -- skipping
... skipping 105 lines ...
• [SLOW TEST:61.226 seconds]
[k8s.io] Probing container
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  with readiness probe that fails should never be ready and never restart [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [k8s.io] Probing container with readiness probe that fails should never be ready and never restart [NodeConformance] [Conformance]","total":-1,"completed":4,"skipped":23,"failed":0}
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:27.883: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 88 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/framework.go:23
  Update Demo
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:297
    should create and stop a replication controller  [Conformance]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","total":-1,"completed":3,"skipped":12,"failed":0}

S
------------------------------
[BeforeEach] [sig-storage] CSI mock volume
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 44 lines ...
Oct  1 08:47:24.565: INFO: waiting for CSIDriver csi-mock-csi-mock-volumes-2335 to register on node ip-172-20-60-245.ap-northeast-1.compute.internal
STEP: Creating pod
Oct  1 08:47:30.243: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Oct  1 08:47:30.381: INFO: Waiting up to 5m0s for PersistentVolumeClaims [pvc-42mpb] to have phase Bound
Oct  1 08:47:30.517: INFO: PersistentVolumeClaim pvc-42mpb found and phase=Bound (135.700842ms)
STEP: checking for CSIInlineVolumes feature
Oct  1 08:47:53.475: INFO: Error getting logs for pod inline-volume-vxc56: the server rejected our request for an unknown reason (get pods inline-volume-vxc56)
Oct  1 08:47:53.753: INFO: Deleting pod "inline-volume-vxc56" in namespace "csi-mock-volumes-2335"
Oct  1 08:47:53.890: INFO: Wait up to 5m0s for pod "inline-volume-vxc56" to be fully deleted
STEP: Deleting the previously created pod
Oct  1 08:48:08.162: INFO: Deleting pod "pvc-volume-tester-66kxp" in namespace "csi-mock-volumes-2335"
Oct  1 08:48:08.300: INFO: Wait up to 5m0s for pod "pvc-volume-tester-66kxp" to be fully deleted
STEP: Checking CSI driver logs
Oct  1 08:48:14.720: INFO: Found volume attribute csi.storage.k8s.io/pod.namespace: csi-mock-volumes-2335
Oct  1 08:48:14.720: INFO: Found volume attribute csi.storage.k8s.io/pod.uid: fc955385-c951-48b5-a1e8-af8a2d155833
Oct  1 08:48:14.720: INFO: Found volume attribute csi.storage.k8s.io/serviceAccount.name: default
Oct  1 08:48:14.720: INFO: Found volume attribute csi.storage.k8s.io/ephemeral: false
Oct  1 08:48:14.720: INFO: Found volume attribute csi.storage.k8s.io/pod.name: pvc-volume-tester-66kxp
Oct  1 08:48:14.720: INFO: Found NodeUnpublishVolume: {json: {"Method":"/csi.v1.Node/NodeUnpublishVolume","Request":{"volume_id":"4","target_path":"/var/lib/kubelet/pods/fc955385-c951-48b5-a1e8-af8a2d155833/volumes/kubernetes.io~csi/pvc-15862966-b63b-45f0-93f8-4a6e47fa89b1/mount"},"Response":{},"Error":"","FullError":null} Method:NodeUnpublishVolume Request:{VolumeContext:map[]} FullError:{Code:OK Message:} Error:}
STEP: Deleting pod pvc-volume-tester-66kxp
Oct  1 08:48:14.720: INFO: Deleting pod "pvc-volume-tester-66kxp" in namespace "csi-mock-volumes-2335"
STEP: Deleting claim pvc-42mpb
Oct  1 08:48:15.136: INFO: Waiting up to 2m0s for PersistentVolume pvc-15862966-b63b-45f0-93f8-4a6e47fa89b1 to get deleted
Oct  1 08:48:15.272: INFO: PersistentVolume pvc-15862966-b63b-45f0-93f8-4a6e47fa89b1 was removed
STEP: Deleting storageclass csi-mock-volumes-2335-sc
... skipping 44 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  CSI workload information using mock driver
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_mock_volume.go:437
    should be passed when podInfoOnMount=true
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_mock_volume.go:487
------------------------------
{"msg":"PASSED [sig-storage] CSI mock volume CSI workload information using mock driver should be passed when podInfoOnMount=true","total":-1,"completed":4,"skipped":33,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:32.688: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 137 lines ...
• [SLOW TEST:10.228 seconds]
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
  should mutate custom resource [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource [Conformance]","total":-1,"completed":6,"skipped":58,"failed":0}

SS
------------------------------
{"msg":"PASSED [sig-storage] PersistentVolumes-local  [Volume type: dir-link] One pod requesting one prebound PVC should be able to mount volume and write from pod1","total":-1,"completed":3,"skipped":21,"failed":0}
[BeforeEach] [k8s.io] InitContainer [NodeConformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:47:47.093: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename init-container
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [k8s.io] InitContainer [NodeConformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/init_container.go:162
[It] should not start app containers if init containers fail on a RestartAlways pod [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: creating the pod
Oct  1 08:47:47.771: INFO: PodSpec: initContainers in spec.initContainers
Oct  1 08:48:37.192: INFO: init container has failed twice: &v1.Pod{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:v1.ObjectMeta{Name:"pod-init-54e29402-c38c-42f1-8981-dabf5df02b46", GenerateName:"", Namespace:"init-container-9152", SelfLink:"", UID:"0ea2f44f-b9f9-46e0-9e4f-05571337f679", ResourceVersion:"6837", Generation:0, CreationTimestamp:v1.Time{Time:time.Time{wall:0x0, ext:63768674867, loc:(*time.Location)(0x7984060)}}, DeletionTimestamp:(*v1.Time)(nil), DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string{"name":"foo", "time":"771736248"}, Annotations:map[string]string(nil), OwnerReferences:[]v1.OwnerReference(nil), Finalizers:[]string(nil), ClusterName:"", ManagedFields:[]v1.ManagedFieldsEntry{v1.ManagedFieldsEntry{Manager:"e2e.test", Operation:"Update", APIVersion:"v1", Time:(*v1.Time)(0xc00353c060), FieldsType:"FieldsV1", FieldsV1:(*v1.FieldsV1)(0xc00353c080)}, v1.ManagedFieldsEntry{Manager:"kubelet", Operation:"Update", APIVersion:"v1", Time:(*v1.Time)(0xc00353c0a0), FieldsType:"FieldsV1", FieldsV1:(*v1.FieldsV1)(0xc00353c0c0)}}}, Spec:v1.PodSpec{Volumes:[]v1.Volume{v1.Volume{Name:"default-token-ndh8w", VolumeSource:v1.VolumeSource{HostPath:(*v1.HostPathVolumeSource)(nil), EmptyDir:(*v1.EmptyDirVolumeSource)(nil), GCEPersistentDisk:(*v1.GCEPersistentDiskVolumeSource)(nil), AWSElasticBlockStore:(*v1.AWSElasticBlockStoreVolumeSource)(nil), GitRepo:(*v1.GitRepoVolumeSource)(nil), Secret:(*v1.SecretVolumeSource)(0xc003fb4000), NFS:(*v1.NFSVolumeSource)(nil), ISCSI:(*v1.ISCSIVolumeSource)(nil), Glusterfs:(*v1.GlusterfsVolumeSource)(nil), PersistentVolumeClaim:(*v1.PersistentVolumeClaimVolumeSource)(nil), RBD:(*v1.RBDVolumeSource)(nil), FlexVolume:(*v1.FlexVolumeSource)(nil), Cinder:(*v1.CinderVolumeSource)(nil), CephFS:(*v1.CephFSVolumeSource)(nil), Flocker:(*v1.FlockerVolumeSource)(nil), DownwardAPI:(*v1.DownwardAPIVolumeSource)(nil), FC:(*v1.FCVolumeSource)(nil), AzureFile:(*v1.AzureFileVolumeSource)(nil), ConfigMap:(*v1.ConfigMapVolumeSource)(nil), VsphereVolume:(*v1.VsphereVirtualDiskVolumeSource)(nil), Quobyte:(*v1.QuobyteVolumeSource)(nil), AzureDisk:(*v1.AzureDiskVolumeSource)(nil), PhotonPersistentDisk:(*v1.PhotonPersistentDiskVolumeSource)(nil), Projected:(*v1.ProjectedVolumeSource)(nil), PortworxVolume:(*v1.PortworxVolumeSource)(nil), ScaleIO:(*v1.ScaleIOVolumeSource)(nil), StorageOS:(*v1.StorageOSVolumeSource)(nil), CSI:(*v1.CSIVolumeSource)(nil), Ephemeral:(*v1.EphemeralVolumeSource)(nil)}}}, InitContainers:[]v1.Container{v1.Container{Name:"init1", Image:"docker.io/library/busybox:1.29", Command:[]string{"/bin/false"}, Args:[]string(nil), WorkingDir:"", Ports:[]v1.ContainerPort(nil), EnvFrom:[]v1.EnvFromSource(nil), Env:[]v1.EnvVar(nil), Resources:v1.ResourceRequirements{Limits:v1.ResourceList(nil), Requests:v1.ResourceList(nil)}, VolumeMounts:[]v1.VolumeMount{v1.VolumeMount{Name:"default-token-ndh8w", ReadOnly:true, MountPath:"/var/run/secrets/kubernetes.io/serviceaccount", SubPath:"", MountPropagation:(*v1.MountPropagationMode)(nil), SubPathExpr:""}}, VolumeDevices:[]v1.VolumeDevice(nil), LivenessProbe:(*v1.Probe)(nil), ReadinessProbe:(*v1.Probe)(nil), StartupProbe:(*v1.Probe)(nil), Lifecycle:(*v1.Lifecycle)(nil), TerminationMessagePath:"/dev/termination-log", TerminationMessagePolicy:"File", ImagePullPolicy:"IfNotPresent", SecurityContext:(*v1.SecurityContext)(nil), Stdin:false, StdinOnce:false, TTY:false}, v1.Container{Name:"init2", Image:"docker.io/library/busybox:1.29", Command:[]string{"/bin/true"}, Args:[]string(nil), WorkingDir:"", Ports:[]v1.ContainerPort(nil), EnvFrom:[]v1.EnvFromSource(nil), Env:[]v1.EnvVar(nil), Resources:v1.ResourceRequirements{Limits:v1.ResourceList(nil), Requests:v1.ResourceList(nil)}, VolumeMounts:[]v1.VolumeMount{v1.VolumeMount{Name:"default-token-ndh8w", ReadOnly:true, MountPath:"/var/run/secrets/kubernetes.io/serviceaccount", SubPath:"", MountPropagation:(*v1.MountPropagationMode)(nil), SubPathExpr:""}}, VolumeDevices:[]v1.VolumeDevice(nil), LivenessProbe:(*v1.Probe)(nil), ReadinessProbe:(*v1.Probe)(nil), StartupProbe:(*v1.Probe)(nil), Lifecycle:(*v1.Lifecycle)(nil), TerminationMessagePath:"/dev/termination-log", TerminationMessagePolicy:"File", ImagePullPolicy:"IfNotPresent", SecurityContext:(*v1.SecurityContext)(nil), Stdin:false, StdinOnce:false, TTY:false}}, Containers:[]v1.Container{v1.Container{Name:"run1", Image:"k8s.gcr.io/pause:3.2", Command:[]string(nil), Args:[]string(nil), WorkingDir:"", Ports:[]v1.ContainerPort(nil), EnvFrom:[]v1.EnvFromSource(nil), Env:[]v1.EnvVar(nil), Resources:v1.ResourceRequirements{Limits:v1.ResourceList{"cpu":resource.Quantity{i:resource.int64Amount{value:100, scale:-3}, d:resource.infDecAmount{Dec:(*inf.Dec)(nil)}, s:"100m", Format:"DecimalSI"}}, Requests:v1.ResourceList{"cpu":resource.Quantity{i:resource.int64Amount{value:100, scale:-3}, d:resource.infDecAmount{Dec:(*inf.Dec)(nil)}, s:"100m", Format:"DecimalSI"}}}, VolumeMounts:[]v1.VolumeMount{v1.VolumeMount{Name:"default-token-ndh8w", ReadOnly:true, MountPath:"/var/run/secrets/kubernetes.io/serviceaccount", SubPath:"", MountPropagation:(*v1.MountPropagationMode)(nil), SubPathExpr:""}}, VolumeDevices:[]v1.VolumeDevice(nil), LivenessProbe:(*v1.Probe)(nil), ReadinessProbe:(*v1.Probe)(nil), StartupProbe:(*v1.Probe)(nil), Lifecycle:(*v1.Lifecycle)(nil), TerminationMessagePath:"/dev/termination-log", TerminationMessagePolicy:"File", ImagePullPolicy:"IfNotPresent", SecurityContext:(*v1.SecurityContext)(nil), Stdin:false, StdinOnce:false, TTY:false}}, EphemeralContainers:[]v1.EphemeralContainer(nil), RestartPolicy:"Always", TerminationGracePeriodSeconds:(*int64)(0xc00337c098), ActiveDeadlineSeconds:(*int64)(nil), DNSPolicy:"ClusterFirst", NodeSelector:map[string]string(nil), ServiceAccountName:"default", DeprecatedServiceAccount:"default", AutomountServiceAccountToken:(*bool)(nil), NodeName:"ip-172-20-35-235.ap-northeast-1.compute.internal", HostNetwork:false, HostPID:false, HostIPC:false, ShareProcessNamespace:(*bool)(nil), SecurityContext:(*v1.PodSecurityContext)(0xc002330000), ImagePullSecrets:[]v1.LocalObjectReference(nil), Hostname:"", Subdomain:"", Affinity:(*v1.Affinity)(nil), SchedulerName:"default-scheduler", Tolerations:[]v1.Toleration{v1.Toleration{Key:"node.kubernetes.io/not-ready", Operator:"Exists", Value:"", Effect:"NoExecute", TolerationSeconds:(*int64)(0xc00337c110)}, v1.Toleration{Key:"node.kubernetes.io/unreachable", Operator:"Exists", Value:"", Effect:"NoExecute", TolerationSeconds:(*int64)(0xc00337c130)}}, HostAliases:[]v1.HostAlias(nil), PriorityClassName:"", Priority:(*int32)(0xc00337c138), DNSConfig:(*v1.PodDNSConfig)(nil), ReadinessGates:[]v1.PodReadinessGate(nil), RuntimeClassName:(*string)(nil), EnableServiceLinks:(*bool)(0xc00337c13c), PreemptionPolicy:(*v1.PreemptionPolicy)(0xc003fba050), Overhead:v1.ResourceList(nil), TopologySpreadConstraints:[]v1.TopologySpreadConstraint(nil), SetHostnameAsFQDN:(*bool)(nil)}, Status:v1.PodStatus{Phase:"Pending", Conditions:[]v1.PodCondition{v1.PodCondition{Type:"Initialized", Status:"False", LastProbeTime:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63768674867, loc:(*time.Location)(0x7984060)}}, Reason:"ContainersNotInitialized", Message:"containers with incomplete status: [init1 init2]"}, v1.PodCondition{Type:"Ready", Status:"False", LastProbeTime:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63768674867, loc:(*time.Location)(0x7984060)}}, Reason:"ContainersNotReady", Message:"containers with unready status: [run1]"}, v1.PodCondition{Type:"ContainersReady", Status:"False", LastProbeTime:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63768674867, loc:(*time.Location)(0x7984060)}}, Reason:"ContainersNotReady", Message:"containers with unready status: [run1]"}, v1.PodCondition{Type:"PodScheduled", Status:"True", LastProbeTime:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63768674867, loc:(*time.Location)(0x7984060)}}, Reason:"", Message:""}}, Message:"", Reason:"", NominatedNodeName:"", HostIP:"172.20.35.235", PodIP:"100.96.3.34", PodIPs:[]v1.PodIP{v1.PodIP{IP:"100.96.3.34"}}, StartTime:(*v1.Time)(0xc00353c0e0), InitContainerStatuses:[]v1.ContainerStatus{v1.ContainerStatus{Name:"init1", State:v1.ContainerState{Waiting:(*v1.ContainerStateWaiting)(nil), Running:(*v1.ContainerStateRunning)(0xc00353c120), Terminated:(*v1.ContainerStateTerminated)(nil)}, LastTerminationState:v1.ContainerState{Waiting:(*v1.ContainerStateWaiting)(nil), Running:(*v1.ContainerStateRunning)(nil), Terminated:(*v1.ContainerStateTerminated)(0xc0023300e0)}, Ready:false, RestartCount:3, Image:"docker.io/library/busybox:1.29", ImageID:"docker.io/library/busybox@sha256:8ccbac733d19c0dd4d70b4f0c1e12245b5fa3ad24758a11035ee505c629c0796", ContainerID:"containerd://01e87d2e616250d11566694f78ecc98c45720744fd7eddb5ee25e2580c2d1b37", Started:(*bool)(nil)}, v1.ContainerStatus{Name:"init2", State:v1.ContainerState{Waiting:(*v1.ContainerStateWaiting)(0xc00353c140), Running:(*v1.ContainerStateRunning)(nil), Terminated:(*v1.ContainerStateTerminated)(nil)}, LastTerminationState:v1.ContainerState{Waiting:(*v1.ContainerStateWaiting)(nil), Running:(*v1.ContainerStateRunning)(nil), Terminated:(*v1.ContainerStateTerminated)(nil)}, Ready:false, RestartCount:0, Image:"docker.io/library/busybox:1.29", ImageID:"", ContainerID:"", Started:(*bool)(nil)}}, ContainerStatuses:[]v1.ContainerStatus{v1.ContainerStatus{Name:"run1", State:v1.ContainerState{Waiting:(*v1.ContainerStateWaiting)(0xc00353c100), Running:(*v1.ContainerStateRunning)(nil), Terminated:(*v1.ContainerStateTerminated)(nil)}, LastTerminationState:v1.ContainerState{Waiting:(*v1.ContainerStateWaiting)(nil), Running:(*v1.ContainerStateRunning)(nil), Terminated:(*v1.ContainerStateTerminated)(nil)}, Ready:false, RestartCount:0, Image:"k8s.gcr.io/pause:3.2", ImageID:"", ContainerID:"", Started:(*bool)(0xc00337c1bf)}}, QOSClass:"Burstable", EphemeralContainerStatuses:[]v1.ContainerStatus(nil)}}
[AfterEach] [k8s.io] InitContainer [NodeConformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:48:37.192: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "init-container-9152" for this suite.


• [SLOW TEST:50.373 seconds]
[k8s.io] InitContainer [NodeConformance]
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  should not start app containers if init containers fail on a RestartAlways pod [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [k8s.io] InitContainer [NodeConformance] should not start app containers if init containers fail on a RestartAlways pod [Conformance]","total":-1,"completed":4,"skipped":21,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:37.482: INFO: Driver hostPathSymlink doesn't support DynamicPV -- skipping
... skipping 71 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:48:37.587: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "secrets-7370" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] Secrets should be immutable if `immutable` field is set","total":-1,"completed":7,"skipped":60,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:37.865: INFO: Only supported for providers [vsphere] (not aws)
... skipping 156 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      Verify if offline PVC expansion works
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:169
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: aws] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand Verify if offline PVC expansion works","total":-1,"completed":4,"skipped":26,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:38.410: INFO: Driver local doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 77 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:48:38.879: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "kubectl-8283" for this suite.

•
------------------------------
{"msg":"PASSED [sig-cli] Kubectl client Kubectl create quota should create a quota with scopes","total":-1,"completed":5,"skipped":27,"failed":0}
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:39.160: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 427 lines ...
Oct  1 08:48:28.573: INFO: PersistentVolumeClaim pvc-h9z2z found but phase is Pending instead of Bound.
Oct  1 08:48:30.704: INFO: PersistentVolumeClaim pvc-h9z2z found and phase=Bound (4.393623785s)
Oct  1 08:48:30.704: INFO: Waiting up to 3m0s for PersistentVolume local-5hrbz to have phase Bound
Oct  1 08:48:30.833: INFO: PersistentVolume local-5hrbz found and phase=Bound (129.09891ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-c8rt
STEP: Creating a pod to test subpath
Oct  1 08:48:31.221: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-c8rt" in namespace "provisioning-670" to be "Succeeded or Failed"
Oct  1 08:48:31.352: INFO: Pod "pod-subpath-test-preprovisionedpv-c8rt": Phase="Pending", Reason="", readiness=false. Elapsed: 131.084397ms
Oct  1 08:48:33.482: INFO: Pod "pod-subpath-test-preprovisionedpv-c8rt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.260297539s
Oct  1 08:48:35.611: INFO: Pod "pod-subpath-test-preprovisionedpv-c8rt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.389432128s
STEP: Saw pod success
Oct  1 08:48:35.611: INFO: Pod "pod-subpath-test-preprovisionedpv-c8rt" satisfied condition "Succeeded or Failed"
Oct  1 08:48:35.740: INFO: Trying to get logs from node ip-172-20-41-255.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-c8rt container test-container-subpath-preprovisionedpv-c8rt: <nil>
STEP: delete the pod
Oct  1 08:48:36.039: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-c8rt to disappear
Oct  1 08:48:36.169: INFO: Pod pod-subpath-test-preprovisionedpv-c8rt no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-c8rt
Oct  1 08:48:36.169: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-c8rt" in namespace "provisioning-670"
... skipping 26 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support readOnly file specified in the volumeMount [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:376
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: blockfs] [Testpattern: Pre-provisioned PV (default fs)] subPath should support readOnly file specified in the volumeMount [LinuxOnly]","total":-1,"completed":5,"skipped":39,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:40.648: INFO: Driver local doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 19 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 with mappings [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating configMap with name configmap-test-volume-map-4479bf25-5680-4ce5-80cb-171da232ce29
STEP: Creating a pod to test consume configMaps
Oct  1 08:48:39.372: INFO: Waiting up to 5m0s for pod "pod-configmaps-db086977-3ad1-4d36-90b5-d852f29ddb9a" in namespace "configmap-8696" to be "Succeeded or Failed"
Oct  1 08:48:39.504: INFO: Pod "pod-configmaps-db086977-3ad1-4d36-90b5-d852f29ddb9a": Phase="Pending", Reason="", readiness=false. Elapsed: 131.58998ms
Oct  1 08:48:41.637: INFO: Pod "pod-configmaps-db086977-3ad1-4d36-90b5-d852f29ddb9a": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.265227546s
STEP: Saw pod success
Oct  1 08:48:41.637: INFO: Pod "pod-configmaps-db086977-3ad1-4d36-90b5-d852f29ddb9a" satisfied condition "Succeeded or Failed"
Oct  1 08:48:41.770: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod pod-configmaps-db086977-3ad1-4d36-90b5-d852f29ddb9a container agnhost-container: <nil>
STEP: delete the pod
Oct  1 08:48:42.048: INFO: Waiting for pod pod-configmaps-db086977-3ad1-4d36-90b5-d852f29ddb9a to disappear
Oct  1 08:48:42.180: INFO: Pod pod-configmaps-db086977-3ad1-4d36-90b5-d852f29ddb9a no longer exists
[AfterEach] [sig-storage] ConfigMap
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:48:42.180: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "configmap-8696" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume with mappings [NodeConformance] [Conformance]","total":-1,"completed":5,"skipped":33,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:42.456: INFO: Driver local doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 83 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:188
    Two pods mounting a local volume at the same time
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:244
      should be able to write from pod1 and read from pod2
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:245
------------------------------
{"msg":"PASSED [sig-storage] PersistentVolumes-local  [Volume type: dir-bindmounted] Two pods mounting a local volume at the same time should be able to write from pod1 and read from pod2","total":-1,"completed":6,"skipped":59,"failed":0}

SSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:45.754: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 23 lines ...
Oct  1 08:48:27.893: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
[It] should support non-existent path
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:191
Oct  1 08:48:28.575: INFO: In-tree plugin kubernetes.io/host-path is not migrated, not validating any metrics
Oct  1 08:48:28.850: INFO: Waiting up to 5m0s for pod "hostpath-symlink-prep-provisioning-1603" in namespace "provisioning-1603" to be "Succeeded or Failed"
Oct  1 08:48:28.987: INFO: Pod "hostpath-symlink-prep-provisioning-1603": Phase="Pending", Reason="", readiness=false. Elapsed: 136.013414ms
Oct  1 08:48:31.123: INFO: Pod "hostpath-symlink-prep-provisioning-1603": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.272074948s
STEP: Saw pod success
Oct  1 08:48:31.123: INFO: Pod "hostpath-symlink-prep-provisioning-1603" satisfied condition "Succeeded or Failed"
Oct  1 08:48:31.123: INFO: Deleting pod "hostpath-symlink-prep-provisioning-1603" in namespace "provisioning-1603"
Oct  1 08:48:31.264: INFO: Wait up to 5m0s for pod "hostpath-symlink-prep-provisioning-1603" to be fully deleted
Oct  1 08:48:31.400: INFO: Creating resource for inline volume
STEP: Creating pod pod-subpath-test-inlinevolume-cbfp
STEP: Creating a pod to test subpath
Oct  1 08:48:31.547: INFO: Waiting up to 5m0s for pod "pod-subpath-test-inlinevolume-cbfp" in namespace "provisioning-1603" to be "Succeeded or Failed"
Oct  1 08:48:31.683: INFO: Pod "pod-subpath-test-inlinevolume-cbfp": Phase="Pending", Reason="", readiness=false. Elapsed: 136.186648ms
Oct  1 08:48:33.819: INFO: Pod "pod-subpath-test-inlinevolume-cbfp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.27249326s
Oct  1 08:48:35.955: INFO: Pod "pod-subpath-test-inlinevolume-cbfp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.408564595s
STEP: Saw pod success
Oct  1 08:48:35.955: INFO: Pod "pod-subpath-test-inlinevolume-cbfp" satisfied condition "Succeeded or Failed"
Oct  1 08:48:36.100: INFO: Trying to get logs from node ip-172-20-41-255.ap-northeast-1.compute.internal pod pod-subpath-test-inlinevolume-cbfp container test-container-volume-inlinevolume-cbfp: <nil>
STEP: delete the pod
Oct  1 08:48:36.385: INFO: Waiting for pod pod-subpath-test-inlinevolume-cbfp to disappear
Oct  1 08:48:36.521: INFO: Pod pod-subpath-test-inlinevolume-cbfp no longer exists
STEP: Deleting pod pod-subpath-test-inlinevolume-cbfp
Oct  1 08:48:36.521: INFO: Deleting pod "pod-subpath-test-inlinevolume-cbfp" in namespace "provisioning-1603"
STEP: Deleting pod
Oct  1 08:48:36.657: INFO: Deleting pod "pod-subpath-test-inlinevolume-cbfp" in namespace "provisioning-1603"
Oct  1 08:48:36.937: INFO: Waiting up to 5m0s for pod "hostpath-symlink-prep-provisioning-1603" in namespace "provisioning-1603" to be "Succeeded or Failed"
Oct  1 08:48:37.072: INFO: Pod "hostpath-symlink-prep-provisioning-1603": Phase="Pending", Reason="", readiness=false. Elapsed: 135.383529ms
Oct  1 08:48:39.208: INFO: Pod "hostpath-symlink-prep-provisioning-1603": Phase="Pending", Reason="", readiness=false. Elapsed: 2.270881947s
Oct  1 08:48:41.346: INFO: Pod "hostpath-symlink-prep-provisioning-1603": Phase="Pending", Reason="", readiness=false. Elapsed: 4.409362082s
Oct  1 08:48:43.483: INFO: Pod "hostpath-symlink-prep-provisioning-1603": Phase="Pending", Reason="", readiness=false. Elapsed: 6.546051007s
Oct  1 08:48:45.619: INFO: Pod "hostpath-symlink-prep-provisioning-1603": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.681864124s
STEP: Saw pod success
Oct  1 08:48:45.619: INFO: Pod "hostpath-symlink-prep-provisioning-1603" satisfied condition "Succeeded or Failed"
Oct  1 08:48:45.619: INFO: Deleting pod "hostpath-symlink-prep-provisioning-1603" in namespace "provisioning-1603"
Oct  1 08:48:45.759: INFO: Wait up to 5m0s for pod "hostpath-symlink-prep-provisioning-1603" to be fully deleted
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:48:45.895: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "provisioning-1603" for this suite.
... skipping 19 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/subpath.go:38
STEP: Setting up data
[It] should support subpaths with configmap pod [LinuxOnly] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating pod pod-subpath-test-configmap-tfjl
STEP: Creating a pod to test atomic-volume-subpath
Oct  1 08:48:23.547: INFO: Waiting up to 5m0s for pod "pod-subpath-test-configmap-tfjl" in namespace "subpath-7228" to be "Succeeded or Failed"
Oct  1 08:48:23.678: INFO: Pod "pod-subpath-test-configmap-tfjl": Phase="Pending", Reason="", readiness=false. Elapsed: 130.892521ms
Oct  1 08:48:25.809: INFO: Pod "pod-subpath-test-configmap-tfjl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.261944119s
Oct  1 08:48:27.941: INFO: Pod "pod-subpath-test-configmap-tfjl": Phase="Running", Reason="", readiness=true. Elapsed: 4.393308758s
Oct  1 08:48:30.073: INFO: Pod "pod-subpath-test-configmap-tfjl": Phase="Running", Reason="", readiness=true. Elapsed: 6.525301224s
Oct  1 08:48:32.205: INFO: Pod "pod-subpath-test-configmap-tfjl": Phase="Running", Reason="", readiness=true. Elapsed: 8.657880774s
Oct  1 08:48:34.343: INFO: Pod "pod-subpath-test-configmap-tfjl": Phase="Running", Reason="", readiness=true. Elapsed: 10.795276042s
Oct  1 08:48:36.474: INFO: Pod "pod-subpath-test-configmap-tfjl": Phase="Running", Reason="", readiness=true. Elapsed: 12.926613078s
Oct  1 08:48:38.605: INFO: Pod "pod-subpath-test-configmap-tfjl": Phase="Running", Reason="", readiness=true. Elapsed: 15.057542939s
Oct  1 08:48:40.736: INFO: Pod "pod-subpath-test-configmap-tfjl": Phase="Running", Reason="", readiness=true. Elapsed: 17.188831858s
Oct  1 08:48:42.867: INFO: Pod "pod-subpath-test-configmap-tfjl": Phase="Running", Reason="", readiness=true. Elapsed: 19.319957773s
Oct  1 08:48:44.999: INFO: Pod "pod-subpath-test-configmap-tfjl": Phase="Running", Reason="", readiness=true. Elapsed: 21.451613893s
Oct  1 08:48:47.130: INFO: Pod "pod-subpath-test-configmap-tfjl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.583182092s
STEP: Saw pod success
Oct  1 08:48:47.130: INFO: Pod "pod-subpath-test-configmap-tfjl" satisfied condition "Succeeded or Failed"
Oct  1 08:48:47.262: INFO: Trying to get logs from node ip-172-20-35-235.ap-northeast-1.compute.internal pod pod-subpath-test-configmap-tfjl container test-container-subpath-configmap-tfjl: <nil>
STEP: delete the pod
Oct  1 08:48:47.536: INFO: Waiting for pod pod-subpath-test-configmap-tfjl to disappear
Oct  1 08:48:47.671: INFO: Pod pod-subpath-test-configmap-tfjl no longer exists
STEP: Deleting pod pod-subpath-test-configmap-tfjl
Oct  1 08:48:47.671: INFO: Deleting pod "pod-subpath-test-configmap-tfjl" in namespace "subpath-7228"
... skipping 8 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  Atomic writer volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/subpath.go:34
    should support subpaths with configmap pod [LinuxOnly] [Conformance]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-storage] Subpath Atomic writer volumes should support subpaths with configmap pod [LinuxOnly] [Conformance]","total":-1,"completed":6,"skipped":26,"failed":0}

SSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:48.107: INFO: Driver supports dynamic provisioning, skipping InlineVolume pattern
... skipping 57 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:48:48.116: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "svcaccounts-6139" for this suite.

•
------------------------------
{"msg":"PASSED [sig-auth] ServiceAccounts should guarantee kube-root-ca.crt exist in any namespace","total":-1,"completed":7,"skipped":75,"failed":0}
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:48.396: INFO: Driver supports dynamic provisioning, skipping InlineVolume pattern
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 210 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_volumes.go:39
    [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should resize volume when PVC is edited while pod is using it
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:241
------------------------------
{"msg":"PASSED [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand should resize volume when PVC is edited while pod is using it","total":-1,"completed":6,"skipped":49,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ext4)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:48.655: INFO: Only supported for node OS distro [gci ubuntu custom] (not debian)
... skipping 51 lines ...
[It] should support existing single file [LinuxOnly]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:216
Oct  1 08:48:43.126: INFO: In-tree plugin kubernetes.io/host-path is not migrated, not validating any metrics
Oct  1 08:48:43.259: INFO: Creating resource for inline volume
STEP: Creating pod pod-subpath-test-inlinevolume-z9j2
STEP: Creating a pod to test subpath
Oct  1 08:48:43.394: INFO: Waiting up to 5m0s for pod "pod-subpath-test-inlinevolume-z9j2" in namespace "provisioning-7348" to be "Succeeded or Failed"
Oct  1 08:48:43.527: INFO: Pod "pod-subpath-test-inlinevolume-z9j2": Phase="Pending", Reason="", readiness=false. Elapsed: 133.110042ms
Oct  1 08:48:45.660: INFO: Pod "pod-subpath-test-inlinevolume-z9j2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.266617094s
Oct  1 08:48:47.797: INFO: Pod "pod-subpath-test-inlinevolume-z9j2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.403052488s
STEP: Saw pod success
Oct  1 08:48:47.797: INFO: Pod "pod-subpath-test-inlinevolume-z9j2" satisfied condition "Succeeded or Failed"
Oct  1 08:48:47.932: INFO: Trying to get logs from node ip-172-20-41-255.ap-northeast-1.compute.internal pod pod-subpath-test-inlinevolume-z9j2 container test-container-subpath-inlinevolume-z9j2: <nil>
STEP: delete the pod
Oct  1 08:48:48.206: INFO: Waiting for pod pod-subpath-test-inlinevolume-z9j2 to disappear
Oct  1 08:48:48.337: INFO: Pod pod-subpath-test-inlinevolume-z9j2 no longer exists
STEP: Deleting pod pod-subpath-test-inlinevolume-z9j2
Oct  1 08:48:48.337: INFO: Deleting pod "pod-subpath-test-inlinevolume-z9j2" in namespace "provisioning-7348"
... skipping 12 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Inline-volume (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support existing single file [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:216
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: hostPath] [Testpattern: Inline-volume (default fs)] subPath should support existing single file [LinuxOnly]","total":-1,"completed":6,"skipped":34,"failed":0}

S
------------------------------
[BeforeEach] [sig-storage] Secrets
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:48:40.656: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename secrets
STEP: Waiting for a default service account to be provisioned in namespace
[It] should be consumable from pods in volume [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating secret with name secret-test-407902b4-f3ca-4083-867d-236b37b72fd7
STEP: Creating a pod to test consume secrets
Oct  1 08:48:41.575: INFO: Waiting up to 5m0s for pod "pod-secrets-bd6d92c7-01c2-44b8-99e7-86187b3722cc" in namespace "secrets-6820" to be "Succeeded or Failed"
Oct  1 08:48:41.704: INFO: Pod "pod-secrets-bd6d92c7-01c2-44b8-99e7-86187b3722cc": Phase="Pending", Reason="", readiness=false. Elapsed: 128.761275ms
Oct  1 08:48:43.833: INFO: Pod "pod-secrets-bd6d92c7-01c2-44b8-99e7-86187b3722cc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.257770133s
Oct  1 08:48:45.962: INFO: Pod "pod-secrets-bd6d92c7-01c2-44b8-99e7-86187b3722cc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.386642126s
Oct  1 08:48:48.091: INFO: Pod "pod-secrets-bd6d92c7-01c2-44b8-99e7-86187b3722cc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.515972039s
STEP: Saw pod success
Oct  1 08:48:48.091: INFO: Pod "pod-secrets-bd6d92c7-01c2-44b8-99e7-86187b3722cc" satisfied condition "Succeeded or Failed"
Oct  1 08:48:48.220: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod pod-secrets-bd6d92c7-01c2-44b8-99e7-86187b3722cc container secret-volume-test: <nil>
STEP: delete the pod
Oct  1 08:48:48.489: INFO: Waiting for pod pod-secrets-bd6d92c7-01c2-44b8-99e7-86187b3722cc to disappear
Oct  1 08:48:48.636: INFO: Pod pod-secrets-bd6d92c7-01c2-44b8-99e7-86187b3722cc no longer exists
[AfterEach] [sig-storage] Secrets
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 4 lines ...
• [SLOW TEST:8.241 seconds]
[sig-storage] Secrets
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/secrets_volume.go:36
  should be consumable from pods in volume [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-storage] Secrets should be consumable from pods in volume [NodeConformance] [Conformance]","total":-1,"completed":6,"skipped":40,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext3)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:48.914: INFO: Only supported for providers [vsphere] (not aws)
... skipping 102 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should not mount / map unused volumes in a pod [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:347
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: tmpfs] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]","total":-1,"completed":6,"skipped":37,"failed":0}

SSSSS
------------------------------
[BeforeEach] [sig-api-machinery] server version
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 12 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:48:49.270: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "server-version-7520" for this suite.

•
------------------------------
{"msg":"PASSED [sig-api-machinery] server version should find the server version [Conformance]","total":-1,"completed":8,"skipped":85,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:49.554: INFO: Driver local doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 11 lines ...
      Driver local doesn't support DynamicPV -- skipping

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:173
------------------------------
SSSS
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: hostPathSymlink] [Testpattern: Inline-volume (default fs)] subPath should support non-existent path","total":-1,"completed":5,"skipped":25,"failed":0}
[BeforeEach] [sig-cli] Kubectl client
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:48:46.177: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename kubectl
STEP: Waiting for a default service account to be provisioned in namespace
... skipping 15 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:48:50.760: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "kubectl-5128" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: block] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]","total":-1,"completed":8,"skipped":54,"failed":0}
[BeforeEach] [sig-cli] Kubectl Port forwarding
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:48:40.540: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename port-forwarding
STEP: Waiting for a default service account to be provisioned in namespace
... skipping 29 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/portforward.go:452
    that expects a client request
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/portforward.go:453
      should support a client that connects, sends NO DATA, and disconnects
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/portforward.go:454
------------------------------
{"msg":"PASSED [sig-cli] Kubectl Port forwarding With a server listening on 0.0.0.0 that expects a client request should support a client that connects, sends NO DATA, and disconnects","total":-1,"completed":9,"skipped":54,"failed":0}

SSS
------------------------------
[BeforeEach] [k8s.io] Kubelet
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 8 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:48:51.468: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "kubelet-test-4056" for this suite.

•
------------------------------
{"msg":"PASSED [k8s.io] Kubelet when scheduling a busybox command in a pod should print the output to logs [NodeConformance] [Conformance]","total":-1,"completed":7,"skipped":37,"failed":0}

SS
------------------------------
[BeforeEach] [sig-storage] CSI mock volume
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 41 lines ...
Oct  1 08:48:11.708: INFO: creating *v1.CSIDriver: csi-mock-csi-mock-volumes-5984
Oct  1 08:48:11.841: INFO: creating *v1.StatefulSet: csi-mock-volumes-5984-5593/csi-mockplugin-attacher
Oct  1 08:48:11.975: INFO: waiting up to 4m0s for CSIDriver "csi-mock-csi-mock-volumes-5984"
Oct  1 08:48:12.107: INFO: waiting for CSIDriver csi-mock-csi-mock-volumes-5984 to register on node ip-172-20-60-245.ap-northeast-1.compute.internal
STEP: Creating pod
STEP: checking for CSIInlineVolumes feature
Oct  1 08:48:20.176: INFO: Error getting logs for pod inline-volume-6w9w6: the server rejected our request for an unknown reason (get pods inline-volume-6w9w6)
Oct  1 08:48:20.317: INFO: Deleting pod "inline-volume-6w9w6" in namespace "csi-mock-volumes-5984"
Oct  1 08:48:20.455: INFO: Wait up to 5m0s for pod "inline-volume-6w9w6" to be fully deleted
STEP: Deleting the previously created pod
Oct  1 08:48:32.721: INFO: Deleting pod "pvc-volume-tester-q2ws4" in namespace "csi-mock-volumes-5984"
Oct  1 08:48:32.855: INFO: Wait up to 5m0s for pod "pvc-volume-tester-q2ws4" to be fully deleted
STEP: Checking CSI driver logs
Oct  1 08:48:35.258: INFO: Found volume attribute csi.storage.k8s.io/pod.namespace: csi-mock-volumes-5984
Oct  1 08:48:35.258: INFO: Found volume attribute csi.storage.k8s.io/pod.uid: 83a03337-192b-4a36-9cb3-ae627d3747f6
Oct  1 08:48:35.258: INFO: Found volume attribute csi.storage.k8s.io/serviceAccount.name: default
Oct  1 08:48:35.258: INFO: Found volume attribute csi.storage.k8s.io/ephemeral: true
Oct  1 08:48:35.258: INFO: Found volume attribute csi.storage.k8s.io/pod.name: pvc-volume-tester-q2ws4
Oct  1 08:48:35.258: INFO: Found NodeUnpublishVolume: {json: {"Method":"/csi.v1.Node/NodeUnpublishVolume","Request":{"volume_id":"csi-886a4b504a74a182faac6da3b853ccbea93b4ba36d51c4d162e0f8f815f1a476","target_path":"/var/lib/kubelet/pods/83a03337-192b-4a36-9cb3-ae627d3747f6/volumes/kubernetes.io~csi/my-volume/mount"},"Response":{},"Error":"","FullError":null} Method:NodeUnpublishVolume Request:{VolumeContext:map[]} FullError:{Code:OK Message:} Error:}
STEP: Deleting pod pvc-volume-tester-q2ws4
Oct  1 08:48:35.258: INFO: Deleting pod "pvc-volume-tester-q2ws4" in namespace "csi-mock-volumes-5984"
STEP: Cleaning up resources
STEP: deleting the test namespace: csi-mock-volumes-5984
STEP: Waiting for namespaces [csi-mock-volumes-5984] to vanish
STEP: uninstalling csi mock driver
... skipping 40 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  CSI workload information using mock driver
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_mock_volume.go:437
    contain ephemeral=true when using inline volume
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_mock_volume.go:487
------------------------------
{"msg":"PASSED [sig-storage] CSI mock volume CSI workload information using mock driver contain ephemeral=true when using inline volume","total":-1,"completed":3,"skipped":34,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:52.610: INFO: Only supported for node OS distro [gci ubuntu custom] (not debian)
... skipping 24 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 with mappings and Item mode set [LinuxOnly] [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating configMap with name configmap-test-volume-map-2ec4d402-1412-47a1-9c72-d129e0a51cc0
STEP: Creating a pod to test consume configMaps
Oct  1 08:48:49.861: INFO: Waiting up to 5m0s for pod "pod-configmaps-c8720ce7-ef6e-4865-8909-9458e250b777" in namespace "configmap-8283" to be "Succeeded or Failed"
Oct  1 08:48:49.993: INFO: Pod "pod-configmaps-c8720ce7-ef6e-4865-8909-9458e250b777": Phase="Pending", Reason="", readiness=false. Elapsed: 131.064625ms
Oct  1 08:48:52.127: INFO: Pod "pod-configmaps-c8720ce7-ef6e-4865-8909-9458e250b777": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.265013608s
STEP: Saw pod success
Oct  1 08:48:52.127: INFO: Pod "pod-configmaps-c8720ce7-ef6e-4865-8909-9458e250b777" satisfied condition "Succeeded or Failed"
Oct  1 08:48:52.255: INFO: Trying to get logs from node ip-172-20-60-245.ap-northeast-1.compute.internal pod pod-configmaps-c8720ce7-ef6e-4865-8909-9458e250b777 container agnhost-container: <nil>
STEP: delete the pod
Oct  1 08:48:52.537: INFO: Waiting for pod pod-configmaps-c8720ce7-ef6e-4865-8909-9458e250b777 to disappear
Oct  1 08:48:52.666: INFO: Pod pod-configmaps-c8720ce7-ef6e-4865-8909-9458e250b777 no longer exists
[AfterEach] [sig-storage] ConfigMap
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:48:52.666: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "configmap-8283" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume with mappings and Item mode set [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":7,"skipped":51,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:52.935: INFO: Driver local doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 2 lines ...
[sig-storage] In-tree Volumes
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  [Driver: local][LocalVolumeType: block]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Dynamic PV (immediate binding)] topology
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should fail to schedule a pod which has topologies that conflict with AllowedTopologies [BeforeEach]
      /workspace/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/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:173
------------------------------
... skipping 12 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:48:54.276: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "health-2076" for this suite.

•
------------------------------
{"msg":"PASSED [sig-api-machinery] health handlers should contain necessary checks","total":-1,"completed":8,"skipped":52,"failed":0}
[BeforeEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:54.551: INFO: Driver local doesn't support ext4 -- skipping
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 57 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/portforward.go:452
    that expects a client request
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/portforward.go:453
      should support a client that connects, sends DATA, and disconnects
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/portforward.go:457
------------------------------
{"msg":"PASSED [sig-cli] Kubectl Port forwarding With a server listening on 0.0.0.0 that expects a client request should support a client that connects, sends DATA, and disconnects","total":-1,"completed":6,"skipped":64,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:56.621: INFO: Only supported for providers [azure] (not aws)
... skipping 29 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:48:56.394: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "configmap-1121" for this suite.

•SSS
------------------------------
{"msg":"PASSED [sig-storage] ConfigMap should be immutable if `immutable` field is set","total":-1,"completed":9,"skipped":54,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:56.660: INFO: Driver hostPathSymlink doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 129 lines ...
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] when FSGroup is specified [LinuxOnly] [NodeFeature:FSGroup]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/empty_dir.go:50
[It] volume on default medium should have the correct mode using FSGroup
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/empty_dir.go:71
STEP: Creating a pod to test emptydir volume type on node default medium
Oct  1 08:48:52.227: INFO: Waiting up to 5m0s for pod "pod-e06ccf4f-3c48-4f42-8ae0-dc89ca36197d" in namespace "emptydir-3265" to be "Succeeded or Failed"
Oct  1 08:48:52.359: INFO: Pod "pod-e06ccf4f-3c48-4f42-8ae0-dc89ca36197d": Phase="Pending", Reason="", readiness=false. Elapsed: 132.141206ms
Oct  1 08:48:54.492: INFO: Pod "pod-e06ccf4f-3c48-4f42-8ae0-dc89ca36197d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.265119141s
Oct  1 08:48:56.625: INFO: Pod "pod-e06ccf4f-3c48-4f42-8ae0-dc89ca36197d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.397786046s
STEP: Saw pod success
Oct  1 08:48:56.625: INFO: Pod "pod-e06ccf4f-3c48-4f42-8ae0-dc89ca36197d" satisfied condition "Succeeded or Failed"
Oct  1 08:48:56.757: INFO: Trying to get logs from node ip-172-20-60-245.ap-northeast-1.compute.internal pod pod-e06ccf4f-3c48-4f42-8ae0-dc89ca36197d container test-container: <nil>
STEP: delete the pod
Oct  1 08:48:57.029: INFO: Waiting for pod pod-e06ccf4f-3c48-4f42-8ae0-dc89ca36197d to disappear
Oct  1 08:48:57.162: INFO: Pod pod-e06ccf4f-3c48-4f42-8ae0-dc89ca36197d no longer exists
[AfterEach] [sig-storage] EmptyDir volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 6 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/empty_dir.go:45
  when FSGroup is specified [LinuxOnly] [NodeFeature:FSGroup]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/empty_dir.go:48
    volume on default medium should have the correct mode using FSGroup
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/empty_dir.go:71
------------------------------
{"msg":"PASSED [sig-storage] EmptyDir volumes when FSGroup is specified [LinuxOnly] [NodeFeature:FSGroup] volume on default medium should have the correct mode using FSGroup","total":-1,"completed":10,"skipped":57,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:57.438: INFO: Driver local doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 45 lines ...
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] when FSGroup is specified [LinuxOnly] [NodeFeature:FSGroup]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/empty_dir.go:50
[It] files with FSGroup ownership should support (root,0644,tmpfs)
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/empty_dir.go:67
STEP: Creating a pod to test emptydir 0644 on tmpfs
Oct  1 08:48:52.551: INFO: Waiting up to 5m0s for pod "pod-9b07b572-30b1-4b94-bd48-52659ceeee3c" in namespace "emptydir-4521" to be "Succeeded or Failed"
Oct  1 08:48:52.682: INFO: Pod "pod-9b07b572-30b1-4b94-bd48-52659ceeee3c": Phase="Pending", Reason="", readiness=false. Elapsed: 130.846167ms
Oct  1 08:48:54.814: INFO: Pod "pod-9b07b572-30b1-4b94-bd48-52659ceeee3c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.262877348s
Oct  1 08:48:56.946: INFO: Pod "pod-9b07b572-30b1-4b94-bd48-52659ceeee3c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.39483078s
STEP: Saw pod success
Oct  1 08:48:56.946: INFO: Pod "pod-9b07b572-30b1-4b94-bd48-52659ceeee3c" satisfied condition "Succeeded or Failed"
Oct  1 08:48:57.077: INFO: Trying to get logs from node ip-172-20-60-245.ap-northeast-1.compute.internal pod pod-9b07b572-30b1-4b94-bd48-52659ceeee3c container test-container: <nil>
STEP: delete the pod
Oct  1 08:48:57.348: INFO: Waiting for pod pod-9b07b572-30b1-4b94-bd48-52659ceeee3c to disappear
Oct  1 08:48:57.479: INFO: Pod pod-9b07b572-30b1-4b94-bd48-52659ceeee3c no longer exists
[AfterEach] [sig-storage] EmptyDir volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 16 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:48:56.686: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename topology
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to schedule a pod which has topologies that conflict with AllowedTopologies
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Oct  1 08:48:57.507: INFO: found topology map[failure-domain.beta.kubernetes.io/zone:ap-northeast-1a]
Oct  1 08:48:57.507: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct  1 08:48:57.507: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[sig-storage] In-tree Volumes
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  [Driver: aws]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Dynamic PV (delayed binding)] topology
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should fail to schedule a pod which has topologies that conflict with AllowedTopologies [It]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 116 lines ...
Oct  1 08:48:52.623: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename security-context
STEP: Waiting for a default service account to be provisioned in namespace
[It] should support pod.Spec.SecurityContext.SupplementalGroups [LinuxOnly]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/node/security_context.go:69
STEP: Creating a pod to test pod.Spec.SecurityContext.SupplementalGroups
Oct  1 08:48:53.428: INFO: Waiting up to 5m0s for pod "security-context-20f31507-fbf7-458f-8be6-e7a73d47dda2" in namespace "security-context-1340" to be "Succeeded or Failed"
Oct  1 08:48:53.565: INFO: Pod "security-context-20f31507-fbf7-458f-8be6-e7a73d47dda2": Phase="Pending", Reason="", readiness=false. Elapsed: 136.624122ms
Oct  1 08:48:55.698: INFO: Pod "security-context-20f31507-fbf7-458f-8be6-e7a73d47dda2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.26947663s
Oct  1 08:48:57.830: INFO: Pod "security-context-20f31507-fbf7-458f-8be6-e7a73d47dda2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.402249177s
STEP: Saw pod success
Oct  1 08:48:57.830: INFO: Pod "security-context-20f31507-fbf7-458f-8be6-e7a73d47dda2" satisfied condition "Succeeded or Failed"
Oct  1 08:48:57.963: INFO: Trying to get logs from node ip-172-20-60-245.ap-northeast-1.compute.internal pod security-context-20f31507-fbf7-458f-8be6-e7a73d47dda2 container test-container: <nil>
STEP: delete the pod
Oct  1 08:48:58.235: INFO: Waiting for pod security-context-20f31507-fbf7-458f-8be6-e7a73d47dda2 to disappear
Oct  1 08:48:58.368: INFO: Pod security-context-20f31507-fbf7-458f-8be6-e7a73d47dda2 no longer exists
[AfterEach] [k8s.io] [sig-node] Security Context
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 4 lines ...
• [SLOW TEST:6.015 seconds]
[k8s.io] [sig-node] Security Context
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  should support pod.Spec.SecurityContext.SupplementalGroups [LinuxOnly]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/node/security_context.go:69
------------------------------
{"msg":"PASSED [k8s.io] [sig-node] Security Context should support pod.Spec.SecurityContext.SupplementalGroups [LinuxOnly]","total":-1,"completed":4,"skipped":39,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:58.656: INFO: Driver supports dynamic provisioning, skipping InlineVolume pattern
... skipping 81 lines ...
• [SLOW TEST:10.168 seconds]
[sig-scheduling] LimitRange
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/framework.go:40
  should create a LimitRange with defaults and ensure pod has those defaults applied. [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-scheduling] LimitRange should create a LimitRange with defaults and ensure pod has those defaults applied. [Conformance]","total":-1,"completed":7,"skipped":54,"failed":0}

SSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:48:58.876: INFO: Only supported for node OS distro [gci ubuntu custom] (not debian)
... skipping 48 lines ...
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [sig-storage] Downward API volume
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/downwardapi_volume.go:41
[It] should set mode on item file [LinuxOnly] [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating a pod to test downward API volume plugin
Oct  1 08:48:49.683: INFO: Waiting up to 5m0s for pod "downwardapi-volume-222c2ce6-2fed-4710-a9f6-184aa5d3e376" in namespace "downward-api-2289" to be "Succeeded or Failed"
Oct  1 08:48:49.815: INFO: Pod "downwardapi-volume-222c2ce6-2fed-4710-a9f6-184aa5d3e376": Phase="Pending", Reason="", readiness=false. Elapsed: 132.065941ms
Oct  1 08:48:51.962: INFO: Pod "downwardapi-volume-222c2ce6-2fed-4710-a9f6-184aa5d3e376": Phase="Pending", Reason="", readiness=false. Elapsed: 2.278625762s
Oct  1 08:48:54.096: INFO: Pod "downwardapi-volume-222c2ce6-2fed-4710-a9f6-184aa5d3e376": Phase="Pending", Reason="", readiness=false. Elapsed: 4.412502468s
Oct  1 08:48:56.228: INFO: Pod "downwardapi-volume-222c2ce6-2fed-4710-a9f6-184aa5d3e376": Phase="Pending", Reason="", readiness=false. Elapsed: 6.5450749s
Oct  1 08:48:58.361: INFO: Pod "downwardapi-volume-222c2ce6-2fed-4710-a9f6-184aa5d3e376": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.67776533s
STEP: Saw pod success
Oct  1 08:48:58.361: INFO: Pod "downwardapi-volume-222c2ce6-2fed-4710-a9f6-184aa5d3e376" satisfied condition "Succeeded or Failed"
Oct  1 08:48:58.495: INFO: Trying to get logs from node ip-172-20-35-235.ap-northeast-1.compute.internal pod downwardapi-volume-222c2ce6-2fed-4710-a9f6-184aa5d3e376 container client-container: <nil>
STEP: delete the pod
Oct  1 08:48:58.781: INFO: Waiting for pod downwardapi-volume-222c2ce6-2fed-4710-a9f6-184aa5d3e376 to disappear
Oct  1 08:48:58.915: INFO: Pod downwardapi-volume-222c2ce6-2fed-4710-a9f6-184aa5d3e376 no longer exists
[AfterEach] [sig-storage] Downward API volume
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 4 lines ...
• [SLOW TEST:10.295 seconds]
[sig-storage] Downward API volume
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/downwardapi_volume.go:36
  should set mode on item file [LinuxOnly] [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-storage] Downward API volume should set mode on item file [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":7,"skipped":35,"failed":0}

S
------------------------------
{"msg":"PASSED [sig-cli] Kubectl client Kubectl diff should check if kubectl diff finds a difference for Deployments [Conformance]","total":-1,"completed":6,"skipped":25,"failed":0}
[BeforeEach] [sig-apps] Job
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:48:51.044: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename job
STEP: Waiting for a default service account to be provisioned in namespace
[It] should run a job to completion when tasks sometimes fail and are not locally restarted
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/job.go:117
STEP: Looking for a node to schedule job pod
STEP: Creating a job
STEP: Ensuring job reaches completions
[AfterEach] [sig-apps] Job
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:49:00.140: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "job-3904" for this suite.


• [SLOW TEST:9.369 seconds]
[sig-apps] Job
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23
  should run a job to completion when tasks sometimes fail and are not locally restarted
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/job.go:117
------------------------------
{"msg":"PASSED [sig-apps] Job should run a job to completion when tasks sometimes fail and are not locally restarted","total":-1,"completed":7,"skipped":25,"failed":0}

SSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:00.443: INFO: Only supported for providers [azure] (not aws)
... skipping 573 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
  version v1
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/proxy.go:59
    should proxy through a service and a pod  [Conformance]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-network] Proxy version v1 should proxy through a service and a pod  [Conformance]","total":-1,"completed":5,"skipped":34,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:00.732: INFO: Only supported for providers [gce gke] (not aws)
[AfterEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 42 lines ...
STEP: Building a namespace api object, basename security-context-test
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [k8s.io] Security Context
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/security_context.go:41
[It] should run the container with uid 0 [LinuxOnly] [NodeConformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/security_context.go:94
Oct  1 08:48:58.833: INFO: Waiting up to 5m0s for pod "busybox-user-0-8ff1c109-3954-4d9d-b35c-38ce184e5b22" in namespace "security-context-test-6865" to be "Succeeded or Failed"
Oct  1 08:48:58.968: INFO: Pod "busybox-user-0-8ff1c109-3954-4d9d-b35c-38ce184e5b22": Phase="Pending", Reason="", readiness=false. Elapsed: 135.299544ms
Oct  1 08:49:01.108: INFO: Pod "busybox-user-0-8ff1c109-3954-4d9d-b35c-38ce184e5b22": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.275342516s
Oct  1 08:49:01.108: INFO: Pod "busybox-user-0-8ff1c109-3954-4d9d-b35c-38ce184e5b22" satisfied condition "Succeeded or Failed"
[AfterEach] [k8s.io] Security Context
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:49:01.108: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "security-context-test-6865" for this suite.

•
------------------------------
{"msg":"PASSED [k8s.io] Security Context When creating a container with runAsUser should run the container with uid 0 [LinuxOnly] [NodeConformance]","total":-1,"completed":7,"skipped":95,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:01.406: INFO: Driver emptydir doesn't support DynamicPV -- skipping
... skipping 23 lines ...
Oct  1 08:48:56.699: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename downward-api
STEP: Waiting for a default service account to be provisioned in namespace
[It] should provide host IP as an env var [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating a pod to test downward api env vars
Oct  1 08:48:57.479: INFO: Waiting up to 5m0s for pod "downward-api-3a0ff3b2-d3f4-4ac5-b7f2-d68b32f61776" in namespace "downward-api-5798" to be "Succeeded or Failed"
Oct  1 08:48:57.609: INFO: Pod "downward-api-3a0ff3b2-d3f4-4ac5-b7f2-d68b32f61776": Phase="Pending", Reason="", readiness=false. Elapsed: 129.642048ms
Oct  1 08:48:59.738: INFO: Pod "downward-api-3a0ff3b2-d3f4-4ac5-b7f2-d68b32f61776": Phase="Pending", Reason="", readiness=false. Elapsed: 2.258648477s
Oct  1 08:49:01.873: INFO: Pod "downward-api-3a0ff3b2-d3f4-4ac5-b7f2-d68b32f61776": Phase="Pending", Reason="", readiness=false. Elapsed: 4.393786587s
Oct  1 08:49:04.007: INFO: Pod "downward-api-3a0ff3b2-d3f4-4ac5-b7f2-d68b32f61776": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.527742781s
STEP: Saw pod success
Oct  1 08:49:04.007: INFO: Pod "downward-api-3a0ff3b2-d3f4-4ac5-b7f2-d68b32f61776" satisfied condition "Succeeded or Failed"
Oct  1 08:49:04.141: INFO: Trying to get logs from node ip-172-20-35-235.ap-northeast-1.compute.internal pod downward-api-3a0ff3b2-d3f4-4ac5-b7f2-d68b32f61776 container dapi-container: <nil>
STEP: delete the pod
Oct  1 08:49:04.416: INFO: Waiting for pod downward-api-3a0ff3b2-d3f4-4ac5-b7f2-d68b32f61776 to disappear
Oct  1 08:49:04.545: INFO: Pod downward-api-3a0ff3b2-d3f4-4ac5-b7f2-d68b32f61776 no longer exists
[AfterEach] [sig-node] Downward API
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 4 lines ...
• [SLOW TEST:8.106 seconds]
[sig-node] Downward API
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/downward_api.go:34
  should provide host IP as an env var [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-node] Downward API should provide host IP as an env var [NodeConformance] [Conformance]","total":-1,"completed":10,"skipped":61,"failed":0}

SSS
------------------------------
{"msg":"PASSED [sig-storage] EmptyDir volumes when FSGroup is specified [LinuxOnly] [NodeFeature:FSGroup] files with FSGroup ownership should support (root,0644,tmpfs)","total":-1,"completed":8,"skipped":39,"failed":0}
[BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:48:57.754: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename webhook
STEP: Waiting for a default service account to be provisioned in namespace
... skipping 61 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:49:05.616: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "deployment-4288" for this suite.

•
------------------------------
{"msg":"PASSED [sig-apps] Deployment RecreateDeployment should delete old pods and create new ones [Conformance]","total":-1,"completed":8,"skipped":98,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:05.917: INFO: Only supported for providers [gce gke] (not aws)
... skipping 104 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/framework.go:23
  Kubectl logs
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:1389
    should be able to retrieve and filter logs  [Conformance]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-cli] Kubectl client Kubectl logs should be able to retrieve and filter logs  [Conformance]","total":-1,"completed":7,"skipped":42,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:05.965: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 28 lines ...
[It] should allow exec of files on the volume
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:192
Oct  1 08:48:59.354: INFO: In-tree plugin kubernetes.io/empty-dir is not migrated, not validating any metrics
Oct  1 08:48:59.354: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-8sgn
STEP: Creating a pod to test exec-volume-test
Oct  1 08:48:59.489: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-8sgn" in namespace "volume-6571" to be "Succeeded or Failed"
Oct  1 08:48:59.622: INFO: Pod "exec-volume-test-inlinevolume-8sgn": Phase="Pending", Reason="", readiness=false. Elapsed: 132.809996ms
Oct  1 08:49:01.755: INFO: Pod "exec-volume-test-inlinevolume-8sgn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.266071039s
Oct  1 08:49:03.888: INFO: Pod "exec-volume-test-inlinevolume-8sgn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.398781293s
Oct  1 08:49:06.021: INFO: Pod "exec-volume-test-inlinevolume-8sgn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.531621369s
STEP: Saw pod success
Oct  1 08:49:06.021: INFO: Pod "exec-volume-test-inlinevolume-8sgn" satisfied condition "Succeeded or Failed"
Oct  1 08:49:06.153: INFO: Trying to get logs from node ip-172-20-35-235.ap-northeast-1.compute.internal pod exec-volume-test-inlinevolume-8sgn container exec-container-inlinevolume-8sgn: <nil>
STEP: delete the pod
Oct  1 08:49:06.426: INFO: Waiting for pod exec-volume-test-inlinevolume-8sgn to disappear
Oct  1 08:49:06.558: INFO: Pod exec-volume-test-inlinevolume-8sgn no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-8sgn
Oct  1 08:49:06.558: INFO: Deleting pod "exec-volume-test-inlinevolume-8sgn" in namespace "volume-6571"
... skipping 10 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Inline-volume (default fs)] volumes
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should allow exec of files on the volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:192
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: emptydir] [Testpattern: Inline-volume (default fs)] volumes should allow exec of files on the volume","total":-1,"completed":5,"skipped":46,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
[BeforeEach] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand
... skipping 125 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_volumes.go:39
    [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      Verify if offline PVC expansion works
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:169
------------------------------
{"msg":"PASSED [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand Verify if offline PVC expansion works","total":-1,"completed":4,"skipped":22,"failed":0}

SSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 5 lines ...
[It] should support non-existent path
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:191
Oct  1 08:49:01.426: INFO: In-tree plugin kubernetes.io/host-path is not migrated, not validating any metrics
Oct  1 08:49:01.564: INFO: Creating resource for inline volume
STEP: Creating pod pod-subpath-test-inlinevolume-k65s
STEP: Creating a pod to test subpath
Oct  1 08:49:01.712: INFO: Waiting up to 5m0s for pod "pod-subpath-test-inlinevolume-k65s" in namespace "provisioning-7793" to be "Succeeded or Failed"
Oct  1 08:49:01.847: INFO: Pod "pod-subpath-test-inlinevolume-k65s": Phase="Pending", Reason="", readiness=false. Elapsed: 135.792122ms
Oct  1 08:49:04.005: INFO: Pod "pod-subpath-test-inlinevolume-k65s": Phase="Pending", Reason="", readiness=false. Elapsed: 2.293096979s
Oct  1 08:49:06.137: INFO: Pod "pod-subpath-test-inlinevolume-k65s": Phase="Pending", Reason="", readiness=false. Elapsed: 4.425326095s
Oct  1 08:49:08.270: INFO: Pod "pod-subpath-test-inlinevolume-k65s": Phase="Pending", Reason="", readiness=false. Elapsed: 6.557822079s
Oct  1 08:49:10.404: INFO: Pod "pod-subpath-test-inlinevolume-k65s": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.692620453s
STEP: Saw pod success
Oct  1 08:49:10.404: INFO: Pod "pod-subpath-test-inlinevolume-k65s" satisfied condition "Succeeded or Failed"
Oct  1 08:49:10.538: INFO: Trying to get logs from node ip-172-20-35-235.ap-northeast-1.compute.internal pod pod-subpath-test-inlinevolume-k65s container test-container-volume-inlinevolume-k65s: <nil>
STEP: delete the pod
Oct  1 08:49:10.816: INFO: Waiting for pod pod-subpath-test-inlinevolume-k65s to disappear
Oct  1 08:49:10.949: INFO: Pod pod-subpath-test-inlinevolume-k65s no longer exists
STEP: Deleting pod pod-subpath-test-inlinevolume-k65s
Oct  1 08:49:10.949: INFO: Deleting pod "pod-subpath-test-inlinevolume-k65s" in namespace "provisioning-7793"
... skipping 12 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Inline-volume (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support non-existent path
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:191
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: hostPath] [Testpattern: Inline-volume (default fs)] subPath should support non-existent path","total":-1,"completed":6,"skipped":37,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:11.490: INFO: Driver emptydir doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 35 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  when scheduling a read only busybox container
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/kubelet.go:188
    should not write to root filesystem [LinuxOnly] [NodeConformance] [Conformance]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [k8s.io] Kubelet when scheduling a read only busybox container should not write to root filesystem [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":8,"skipped":50,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:11.630: INFO: Driver csi-hostpath doesn't support ntfs -- skipping
... skipping 93 lines ...
[sig-storage] In-tree Volumes
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  [Driver: hostPathSymlink]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Dynamic PV (delayed binding)] topology
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should fail to schedule a pod which has topologies that conflict with AllowedTopologies [BeforeEach]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Driver hostPathSymlink doesn't support DynamicPV -- skipping

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:173
------------------------------
... skipping 178 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_volumes.go:39
    [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should create read/write inline ephemeral volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/ephemeral.go:167
------------------------------
{"msg":"PASSED [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral should create read/write inline ephemeral volume","total":-1,"completed":2,"skipped":27,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:14.436: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 84 lines ...
• [SLOW TEST:9.751 seconds]
[k8s.io] InitContainer [NodeConformance]
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  should invoke init containers on a RestartAlways pod [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [k8s.io] InitContainer [NodeConformance] should invoke init containers on a RestartAlways pod [Conformance]","total":-1,"completed":6,"skipped":47,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:16.742: INFO: Driver local doesn't support InlineVolume -- skipping
... skipping 53 lines ...
STEP: verifying the pod is in kubernetes
STEP: updating the pod
Oct  1 08:49:12.088: INFO: Successfully updated pod "pod-update-activedeadlineseconds-79071bb4-dc45-44fd-9b8e-0edf921ce9f7"
Oct  1 08:49:12.088: INFO: Waiting up to 5m0s for pod "pod-update-activedeadlineseconds-79071bb4-dc45-44fd-9b8e-0edf921ce9f7" in namespace "pods-9894" to be "terminated due to deadline exceeded"
Oct  1 08:49:12.223: INFO: Pod "pod-update-activedeadlineseconds-79071bb4-dc45-44fd-9b8e-0edf921ce9f7": Phase="Running", Reason="", readiness=true. Elapsed: 135.646792ms
Oct  1 08:49:14.359: INFO: Pod "pod-update-activedeadlineseconds-79071bb4-dc45-44fd-9b8e-0edf921ce9f7": Phase="Running", Reason="", readiness=true. Elapsed: 2.271548747s
Oct  1 08:49:16.532: INFO: Pod "pod-update-activedeadlineseconds-79071bb4-dc45-44fd-9b8e-0edf921ce9f7": Phase="Failed", Reason="DeadlineExceeded", readiness=false. Elapsed: 4.443973928s
Oct  1 08:49:16.532: INFO: Pod "pod-update-activedeadlineseconds-79071bb4-dc45-44fd-9b8e-0edf921ce9f7" satisfied condition "terminated due to deadline exceeded"
[AfterEach] [k8s.io] Pods
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:49:16.532: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "pods-9894" for this suite.


• [SLOW TEST:10.945 seconds]
[k8s.io] Pods
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  should allow activeDeadlineSeconds to be updated [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [k8s.io] Pods should allow activeDeadlineSeconds to be updated [NodeConformance] [Conformance]","total":-1,"completed":9,"skipped":102,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:16.888: INFO: Only supported for providers [gce gke] (not aws)
[AfterEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 112 lines ...
STEP: Building a namespace api object, basename secrets
STEP: Waiting for a default service account to be provisioned in namespace
[It] should be consumable from pods in volume with mappings and Item Mode set [LinuxOnly] [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating secret with name secret-test-map-c66c39dd-4607-4866-9f58-dbd79bf6e9f9
STEP: Creating a pod to test consume secrets
Oct  1 08:49:11.111: INFO: Waiting up to 5m0s for pod "pod-secrets-777829a0-ef21-42ca-b231-f0b566aecba2" in namespace "secrets-9800" to be "Succeeded or Failed"
Oct  1 08:49:11.246: INFO: Pod "pod-secrets-777829a0-ef21-42ca-b231-f0b566aecba2": Phase="Pending", Reason="", readiness=false. Elapsed: 134.658769ms
Oct  1 08:49:13.397: INFO: Pod "pod-secrets-777829a0-ef21-42ca-b231-f0b566aecba2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.286003016s
Oct  1 08:49:15.534: INFO: Pod "pod-secrets-777829a0-ef21-42ca-b231-f0b566aecba2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.422863839s
Oct  1 08:49:17.669: INFO: Pod "pod-secrets-777829a0-ef21-42ca-b231-f0b566aecba2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.558222783s
STEP: Saw pod success
Oct  1 08:49:17.670: INFO: Pod "pod-secrets-777829a0-ef21-42ca-b231-f0b566aecba2" satisfied condition "Succeeded or Failed"
Oct  1 08:49:17.804: INFO: Trying to get logs from node ip-172-20-60-245.ap-northeast-1.compute.internal pod pod-secrets-777829a0-ef21-42ca-b231-f0b566aecba2 container secret-volume-test: <nil>
STEP: delete the pod
Oct  1 08:49:18.112: INFO: Waiting for pod pod-secrets-777829a0-ef21-42ca-b231-f0b566aecba2 to disappear
Oct  1 08:49:18.247: INFO: Pod pod-secrets-777829a0-ef21-42ca-b231-f0b566aecba2 no longer exists
[AfterEach] [sig-storage] Secrets
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 4 lines ...
• [SLOW TEST:8.459 seconds]
[sig-storage] Secrets
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/secrets_volume.go:36
  should be consumable from pods in volume with mappings and Item Mode set [LinuxOnly] [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-storage] Secrets should be consumable from pods in volume with mappings and Item Mode set [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":5,"skipped":27,"failed":0}

SSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:18.641: INFO: Only supported for providers [vsphere] (not aws)
... skipping 60 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:49:18.649: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "replication-controller-2804" for this suite.

•
------------------------------
{"msg":"PASSED [sig-apps] ReplicationController should surface a failure condition on a common issue like exceeded quota [Conformance]","total":-1,"completed":10,"skipped":111,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:18.935: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 47 lines ...
STEP: Building a namespace api object, basename projected
STEP: Waiting for a default service account to be provisioned in namespace
[It] should be consumable from pods in volume with mappings [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating configMap with name projected-configmap-test-volume-map-24c33b38-70fa-4274-ad51-9bc0de165d81
STEP: Creating a pod to test consume configMaps
Oct  1 08:49:15.493: INFO: Waiting up to 5m0s for pod "pod-projected-configmaps-f9b6b024-5d8f-451c-afa9-09285f444b11" in namespace "projected-8913" to be "Succeeded or Failed"
Oct  1 08:49:15.650: INFO: Pod "pod-projected-configmaps-f9b6b024-5d8f-451c-afa9-09285f444b11": Phase="Pending", Reason="", readiness=false. Elapsed: 156.164444ms
Oct  1 08:49:17.783: INFO: Pod "pod-projected-configmaps-f9b6b024-5d8f-451c-afa9-09285f444b11": Phase="Pending", Reason="", readiness=false. Elapsed: 2.289501997s
Oct  1 08:49:19.917: INFO: Pod "pod-projected-configmaps-f9b6b024-5d8f-451c-afa9-09285f444b11": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.423520895s
STEP: Saw pod success
Oct  1 08:49:19.917: INFO: Pod "pod-projected-configmaps-f9b6b024-5d8f-451c-afa9-09285f444b11" satisfied condition "Succeeded or Failed"
Oct  1 08:49:20.051: INFO: Trying to get logs from node ip-172-20-60-245.ap-northeast-1.compute.internal pod pod-projected-configmaps-f9b6b024-5d8f-451c-afa9-09285f444b11 container agnhost-container: <nil>
STEP: delete the pod
Oct  1 08:49:20.333: INFO: Waiting for pod pod-projected-configmaps-f9b6b024-5d8f-451c-afa9-09285f444b11 to disappear
Oct  1 08:49:20.466: INFO: Pod pod-projected-configmaps-f9b6b024-5d8f-451c-afa9-09285f444b11 no longer exists
[AfterEach] [sig-storage] Projected configMap
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 4 lines ...
• [SLOW TEST:6.227 seconds]
[sig-storage] Projected configMap
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_configmap.go:36
  should be consumable from pods in volume with mappings [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-storage] Projected configMap should be consumable from pods in volume with mappings [NodeConformance] [Conformance]","total":-1,"completed":3,"skipped":47,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
... skipping 102 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:188
    Two pods mounting a local volume one after the other
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:250
      should be able to write from pod1 and read from pod2
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:251
------------------------------
{"msg":"PASSED [sig-storage] PersistentVolumes-local  [Volume type: dir] Two pods mounting a local volume one after the other should be able to write from pod1 and read from pod2","total":-1,"completed":8,"skipped":59,"failed":0}

SS
------------------------------
[BeforeEach] [sig-network] Networking
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 115 lines ...
Oct  1 08:49:16.774: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename security-context
STEP: Waiting for a default service account to be provisioned in namespace
[It] should support container.SecurityContext.RunAsUser [LinuxOnly]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/node/security_context.go:103
STEP: Creating a pod to test pod.Spec.SecurityContext.RunAsUser
Oct  1 08:49:17.590: INFO: Waiting up to 5m0s for pod "security-context-72813ee5-13c1-4a72-81f9-14f588a4d3ae" in namespace "security-context-3116" to be "Succeeded or Failed"
Oct  1 08:49:17.723: INFO: Pod "security-context-72813ee5-13c1-4a72-81f9-14f588a4d3ae": Phase="Pending", Reason="", readiness=false. Elapsed: 132.337868ms
Oct  1 08:49:19.857: INFO: Pod "security-context-72813ee5-13c1-4a72-81f9-14f588a4d3ae": Phase="Pending", Reason="", readiness=false. Elapsed: 2.266771647s
Oct  1 08:49:21.991: INFO: Pod "security-context-72813ee5-13c1-4a72-81f9-14f588a4d3ae": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.400440514s
STEP: Saw pod success
Oct  1 08:49:21.991: INFO: Pod "security-context-72813ee5-13c1-4a72-81f9-14f588a4d3ae" satisfied condition "Succeeded or Failed"
Oct  1 08:49:22.123: INFO: Trying to get logs from node ip-172-20-60-245.ap-northeast-1.compute.internal pod security-context-72813ee5-13c1-4a72-81f9-14f588a4d3ae container test-container: <nil>
STEP: delete the pod
Oct  1 08:49:22.394: INFO: Waiting for pod security-context-72813ee5-13c1-4a72-81f9-14f588a4d3ae to disappear
Oct  1 08:49:22.528: INFO: Pod security-context-72813ee5-13c1-4a72-81f9-14f588a4d3ae no longer exists
[AfterEach] [k8s.io] [sig-node] Security Context
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 4 lines ...
• [SLOW TEST:6.021 seconds]
[k8s.io] [sig-node] Security Context
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  should support container.SecurityContext.RunAsUser [LinuxOnly]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/node/security_context.go:103
------------------------------
{"msg":"PASSED [k8s.io] [sig-node] Security Context should support container.SecurityContext.RunAsUser [LinuxOnly]","total":-1,"completed":7,"skipped":51,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:22.803: INFO: Driver local doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 153 lines ...
      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:833
------------------------------
SSS
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir-link-bindmounted] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]","total":-1,"completed":4,"skipped":13,"failed":0}
[BeforeEach] [sig-storage] EmptyDir volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:49:22.378: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename emptydir
STEP: Waiting for a default service account to be provisioned in namespace
... skipping 3 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:49:23.045: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "emptydir-5093" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] EmptyDir volumes pod should support memory backed volumes of specified size","total":-1,"completed":5,"skipped":13,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:23.326: INFO: Only supported for providers [gce gke] (not aws)
... skipping 42 lines ...
• [SLOW TEST:19.856 seconds]
[k8s.io] Pods
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  should be submitted and removed [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [k8s.io] Pods should be submitted and removed [NodeConformance] [Conformance]","total":-1,"completed":11,"skipped":64,"failed":0}

S
------------------------------
[BeforeEach] [sig-api-machinery] Garbage collector
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 16 lines ...
• [SLOW TEST:52.827 seconds]
[sig-api-machinery] Garbage collector
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
  should support orphan deletion of custom resources
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/garbage_collector.go:1055
------------------------------
{"msg":"PASSED [sig-api-machinery] Garbage collector should support orphan deletion of custom resources","total":-1,"completed":5,"skipped":46,"failed":0}

S
------------------------------
[BeforeEach] [sig-apps] Deployment
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 47 lines ...
• [SLOW TEST:26.993 seconds]
[sig-apps] Deployment
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23
  deployment should support rollover [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-apps] Deployment deployment should support rollover [Conformance]","total":-1,"completed":8,"skipped":76,"failed":0}

SS
------------------------------
[BeforeEach] [sig-storage] Projected configMap
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:49:22.845: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename projected
STEP: Waiting for a default service account to be provisioned in namespace
[It] should be consumable from pods in volume with mappings and Item mode set [LinuxOnly] [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating configMap with name projected-configmap-test-volume-map-97a4babb-554d-41a6-ad4f-6feea064efb3
STEP: Creating a pod to test consume configMaps
Oct  1 08:49:23.783: INFO: Waiting up to 5m0s for pod "pod-projected-configmaps-de0815da-c794-4b2e-a85d-471ce9478ede" in namespace "projected-6386" to be "Succeeded or Failed"
Oct  1 08:49:23.915: INFO: Pod "pod-projected-configmaps-de0815da-c794-4b2e-a85d-471ce9478ede": Phase="Pending", Reason="", readiness=false. Elapsed: 132.045269ms
Oct  1 08:49:26.052: INFO: Pod "pod-projected-configmaps-de0815da-c794-4b2e-a85d-471ce9478ede": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.269082296s
STEP: Saw pod success
Oct  1 08:49:26.052: INFO: Pod "pod-projected-configmaps-de0815da-c794-4b2e-a85d-471ce9478ede" satisfied condition "Succeeded or Failed"
Oct  1 08:49:26.207: INFO: Trying to get logs from node ip-172-20-41-255.ap-northeast-1.compute.internal pod pod-projected-configmaps-de0815da-c794-4b2e-a85d-471ce9478ede container agnhost-container: <nil>
STEP: delete the pod
Oct  1 08:49:26.485: INFO: Waiting for pod pod-projected-configmaps-de0815da-c794-4b2e-a85d-471ce9478ede to disappear
Oct  1 08:49:26.617: INFO: Pod pod-projected-configmaps-de0815da-c794-4b2e-a85d-471ce9478ede no longer exists
[AfterEach] [sig-storage] Projected configMap
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:49:26.617: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "projected-6386" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] Projected configMap should be consumable from pods in volume with mappings and Item mode set [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":8,"skipped":60,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:26.901: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 76 lines ...
• [SLOW TEST:8.873 seconds]
[sig-apps] Deployment
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23
  test Deployment ReplicaSet orphaning and adoption regarding controllerRef
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/deployment.go:132
------------------------------
{"msg":"PASSED [sig-apps] Deployment test Deployment ReplicaSet orphaning and adoption regarding controllerRef","total":-1,"completed":11,"skipped":116,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:27.841: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
... skipping 24 lines ...
STEP: Building a namespace api object, basename secrets
STEP: Waiting for a default service account to be provisioned in namespace
[It] should be consumable from pods in volume with mappings [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating secret with name secret-test-map-3bc80287-c5cf-40d6-9557-9ce6b5eaa866
STEP: Creating a pod to test consume secrets
Oct  1 08:49:25.601: INFO: Waiting up to 5m0s for pod "pod-secrets-2f5756ab-b9d9-4d4b-9513-c30ddfe86054" in namespace "secrets-6944" to be "Succeeded or Failed"
Oct  1 08:49:25.735: INFO: Pod "pod-secrets-2f5756ab-b9d9-4d4b-9513-c30ddfe86054": Phase="Pending", Reason="", readiness=false. Elapsed: 134.170147ms
Oct  1 08:49:27.864: INFO: Pod "pod-secrets-2f5756ab-b9d9-4d4b-9513-c30ddfe86054": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.26325027s
STEP: Saw pod success
Oct  1 08:49:27.864: INFO: Pod "pod-secrets-2f5756ab-b9d9-4d4b-9513-c30ddfe86054" satisfied condition "Succeeded or Failed"
Oct  1 08:49:27.995: INFO: Trying to get logs from node ip-172-20-41-255.ap-northeast-1.compute.internal pod pod-secrets-2f5756ab-b9d9-4d4b-9513-c30ddfe86054 container secret-volume-test: <nil>
STEP: delete the pod
Oct  1 08:49:28.277: INFO: Waiting for pod pod-secrets-2f5756ab-b9d9-4d4b-9513-c30ddfe86054 to disappear
Oct  1 08:49:28.406: INFO: Pod pod-secrets-2f5756ab-b9d9-4d4b-9513-c30ddfe86054 no longer exists
[AfterEach] [sig-storage] Secrets
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:49:28.406: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "secrets-6944" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] Secrets should be consumable from pods in volume with mappings [NodeConformance] [Conformance]","total":-1,"completed":12,"skipped":65,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:28.688: INFO: Driver local doesn't support InlineVolume -- skipping
... skipping 55 lines ...
Oct  1 08:48:21.232: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2004-aws-scrfx7s
STEP: creating a claim
Oct  1 08:48:21.369: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-bhm6
STEP: Creating a pod to test subpath
Oct  1 08:48:21.779: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-bhm6" in namespace "provisioning-2004" to be "Succeeded or Failed"
Oct  1 08:48:21.914: INFO: Pod "pod-subpath-test-dynamicpv-bhm6": Phase="Pending", Reason="", readiness=false. Elapsed: 135.109172ms
Oct  1 08:48:24.050: INFO: Pod "pod-subpath-test-dynamicpv-bhm6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.270453882s
Oct  1 08:48:26.187: INFO: Pod "pod-subpath-test-dynamicpv-bhm6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.407425752s
Oct  1 08:48:28.323: INFO: Pod "pod-subpath-test-dynamicpv-bhm6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.543354046s
Oct  1 08:48:30.459: INFO: Pod "pod-subpath-test-dynamicpv-bhm6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.679588221s
Oct  1 08:48:32.603: INFO: Pod "pod-subpath-test-dynamicpv-bhm6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.82355896s
... skipping 6 lines ...
Oct  1 08:48:47.615: INFO: Pod "pod-subpath-test-dynamicpv-bhm6": Phase="Pending", Reason="", readiness=false. Elapsed: 25.835438726s
Oct  1 08:48:49.751: INFO: Pod "pod-subpath-test-dynamicpv-bhm6": Phase="Pending", Reason="", readiness=false. Elapsed: 27.971499291s
Oct  1 08:48:51.888: INFO: Pod "pod-subpath-test-dynamicpv-bhm6": Phase="Pending", Reason="", readiness=false. Elapsed: 30.108547038s
Oct  1 08:48:54.024: INFO: Pod "pod-subpath-test-dynamicpv-bhm6": Phase="Pending", Reason="", readiness=false. Elapsed: 32.244627707s
Oct  1 08:48:56.163: INFO: Pod "pod-subpath-test-dynamicpv-bhm6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.383886109s
STEP: Saw pod success
Oct  1 08:48:56.163: INFO: Pod "pod-subpath-test-dynamicpv-bhm6" satisfied condition "Succeeded or Failed"
Oct  1 08:48:56.299: INFO: Trying to get logs from node ip-172-20-35-235.ap-northeast-1.compute.internal pod pod-subpath-test-dynamicpv-bhm6 container test-container-subpath-dynamicpv-bhm6: <nil>
STEP: delete the pod
Oct  1 08:48:56.584: INFO: Waiting for pod pod-subpath-test-dynamicpv-bhm6 to disappear
Oct  1 08:48:56.719: INFO: Pod pod-subpath-test-dynamicpv-bhm6 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-bhm6
Oct  1 08:48:56.719: INFO: Deleting pod "pod-subpath-test-dynamicpv-bhm6" in namespace "provisioning-2004"
STEP: Creating pod pod-subpath-test-dynamicpv-bhm6
STEP: Creating a pod to test subpath
Oct  1 08:48:56.997: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-bhm6" in namespace "provisioning-2004" to be "Succeeded or Failed"
Oct  1 08:48:57.133: INFO: Pod "pod-subpath-test-dynamicpv-bhm6": Phase="Pending", Reason="", readiness=false. Elapsed: 135.441647ms
Oct  1 08:48:59.269: INFO: Pod "pod-subpath-test-dynamicpv-bhm6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.271042472s
Oct  1 08:49:01.406: INFO: Pod "pod-subpath-test-dynamicpv-bhm6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.408932053s
Oct  1 08:49:03.543: INFO: Pod "pod-subpath-test-dynamicpv-bhm6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.545411534s
Oct  1 08:49:05.679: INFO: Pod "pod-subpath-test-dynamicpv-bhm6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.681489105s
Oct  1 08:49:07.817: INFO: Pod "pod-subpath-test-dynamicpv-bhm6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.819031901s
Oct  1 08:49:09.952: INFO: Pod "pod-subpath-test-dynamicpv-bhm6": Phase="Pending", Reason="", readiness=false. Elapsed: 12.954434232s
Oct  1 08:49:12.088: INFO: Pod "pod-subpath-test-dynamicpv-bhm6": Phase="Pending", Reason="", readiness=false. Elapsed: 15.090390124s
Oct  1 08:49:14.256: INFO: Pod "pod-subpath-test-dynamicpv-bhm6": Phase="Pending", Reason="", readiness=false. Elapsed: 17.258659398s
Oct  1 08:49:16.419: INFO: Pod "pod-subpath-test-dynamicpv-bhm6": Phase="Pending", Reason="", readiness=false. Elapsed: 19.421968705s
Oct  1 08:49:18.609: INFO: Pod "pod-subpath-test-dynamicpv-bhm6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.611590197s
STEP: Saw pod success
Oct  1 08:49:18.609: INFO: Pod "pod-subpath-test-dynamicpv-bhm6" satisfied condition "Succeeded or Failed"
Oct  1 08:49:18.745: INFO: Trying to get logs from node ip-172-20-35-235.ap-northeast-1.compute.internal pod pod-subpath-test-dynamicpv-bhm6 container test-container-subpath-dynamicpv-bhm6: <nil>
STEP: delete the pod
Oct  1 08:49:19.025: INFO: Waiting for pod pod-subpath-test-dynamicpv-bhm6 to disappear
Oct  1 08:49:19.160: INFO: Pod pod-subpath-test-dynamicpv-bhm6 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-bhm6
Oct  1 08:49:19.160: INFO: Deleting pod "pod-subpath-test-dynamicpv-bhm6" in namespace "provisioning-2004"
... skipping 19 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Dynamic PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support existing directories when readOnly specified in the volumeSource
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:391
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: aws] [Testpattern: Dynamic PV (default fs)] subPath should support existing directories when readOnly specified in the volumeSource","total":-1,"completed":8,"skipped":64,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (ext4)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:30.676: INFO: Driver emptydir doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (ext4)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 151 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:49:30.826: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "discovery-1115" for this suite.

•
------------------------------
{"msg":"PASSED [sig-api-machinery] Discovery should validate PreferredVersion for each APIGroup [Conformance]","total":-1,"completed":9,"skipped":63,"failed":0}

S
------------------------------
{"msg":"PASSED [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] Simple CustomResourceDefinition listing custom resource definition objects works  [Conformance]","total":-1,"completed":9,"skipped":60,"failed":0}
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:49:19.421: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
[It] should support existing directories when readOnly specified in the volumeSource
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:391
Oct  1 08:49:20.085: INFO: In-tree plugin kubernetes.io/host-path is not migrated, not validating any metrics
Oct  1 08:49:20.356: INFO: Waiting up to 5m0s for pod "hostpath-symlink-prep-provisioning-4002" in namespace "provisioning-4002" to be "Succeeded or Failed"
Oct  1 08:49:20.489: INFO: Pod "hostpath-symlink-prep-provisioning-4002": Phase="Pending", Reason="", readiness=false. Elapsed: 132.528366ms
Oct  1 08:49:22.622: INFO: Pod "hostpath-symlink-prep-provisioning-4002": Phase="Pending", Reason="", readiness=false. Elapsed: 2.26534303s
Oct  1 08:49:24.754: INFO: Pod "hostpath-symlink-prep-provisioning-4002": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.397498902s
STEP: Saw pod success
Oct  1 08:49:24.754: INFO: Pod "hostpath-symlink-prep-provisioning-4002" satisfied condition "Succeeded or Failed"
Oct  1 08:49:24.754: INFO: Deleting pod "hostpath-symlink-prep-provisioning-4002" in namespace "provisioning-4002"
Oct  1 08:49:24.889: INFO: Wait up to 5m0s for pod "hostpath-symlink-prep-provisioning-4002" to be fully deleted
Oct  1 08:49:25.021: INFO: Creating resource for inline volume
Oct  1 08:49:25.021: INFO: Driver hostPathSymlink on volume type InlineVolume doesn't support readOnly source
STEP: Deleting pod
Oct  1 08:49:25.022: INFO: Deleting pod "pod-subpath-test-inlinevolume-sbvd" in namespace "provisioning-4002"
Oct  1 08:49:25.287: INFO: Waiting up to 5m0s for pod "hostpath-symlink-prep-provisioning-4002" in namespace "provisioning-4002" to be "Succeeded or Failed"
Oct  1 08:49:25.419: INFO: Pod "hostpath-symlink-prep-provisioning-4002": Phase="Pending", Reason="", readiness=false. Elapsed: 131.597274ms
Oct  1 08:49:27.554: INFO: Pod "hostpath-symlink-prep-provisioning-4002": Phase="Pending", Reason="", readiness=false. Elapsed: 2.267029342s
Oct  1 08:49:29.688: INFO: Pod "hostpath-symlink-prep-provisioning-4002": Phase="Pending", Reason="", readiness=false. Elapsed: 4.401393442s
Oct  1 08:49:31.820: INFO: Pod "hostpath-symlink-prep-provisioning-4002": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.533386535s
STEP: Saw pod success
Oct  1 08:49:31.820: INFO: Pod "hostpath-symlink-prep-provisioning-4002" satisfied condition "Succeeded or Failed"
Oct  1 08:49:31.820: INFO: Deleting pod "hostpath-symlink-prep-provisioning-4002" in namespace "provisioning-4002"
Oct  1 08:49:31.957: INFO: Wait up to 5m0s for pod "hostpath-symlink-prep-provisioning-4002" to be fully deleted
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:49:32.089: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "provisioning-4002" for this suite.
... skipping 116 lines ...
• [SLOW TEST:20.485 seconds]
[k8s.io] Pods
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  should support pod readiness gates [NodeFeature:PodReadinessGate]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/pods.go:778
------------------------------
{"msg":"PASSED [k8s.io] Pods should support pod readiness gates [NodeFeature:PodReadinessGate]","total":-1,"completed":6,"skipped":38,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:39.172: INFO: Only supported for node OS distro [gci ubuntu custom] (not debian)
... skipping 46 lines ...
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [sig-storage] Downward API volume
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/downwardapi_volume.go:41
[It] should provide node allocatable (cpu) as default cpu limit if the limit is not set [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating a pod to test downward API volume plugin
Oct  1 08:49:36.658: INFO: Waiting up to 5m0s for pod "downwardapi-volume-f44eaf12-589d-451c-852a-fea3d21f70e4" in namespace "downward-api-2326" to be "Succeeded or Failed"
Oct  1 08:49:36.790: INFO: Pod "downwardapi-volume-f44eaf12-589d-451c-852a-fea3d21f70e4": Phase="Pending", Reason="", readiness=false. Elapsed: 132.032247ms
Oct  1 08:49:38.922: INFO: Pod "downwardapi-volume-f44eaf12-589d-451c-852a-fea3d21f70e4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.264286475s
STEP: Saw pod success
Oct  1 08:49:38.922: INFO: Pod "downwardapi-volume-f44eaf12-589d-451c-852a-fea3d21f70e4" satisfied condition "Succeeded or Failed"
Oct  1 08:49:39.054: INFO: Trying to get logs from node ip-172-20-41-255.ap-northeast-1.compute.internal pod downwardapi-volume-f44eaf12-589d-451c-852a-fea3d21f70e4 container client-container: <nil>
STEP: delete the pod
Oct  1 08:49:39.324: INFO: Waiting for pod downwardapi-volume-f44eaf12-589d-451c-852a-fea3d21f70e4 to disappear
Oct  1 08:49:39.456: INFO: Pod downwardapi-volume-f44eaf12-589d-451c-852a-fea3d21f70e4 no longer exists
[AfterEach] [sig-storage] Downward API volume
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:49:39.456: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "downward-api-2326" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] Downward API volume should provide node allocatable (cpu) as default cpu limit if the limit is not set [NodeConformance] [Conformance]","total":-1,"completed":11,"skipped":93,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:39.740: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 71 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:49:40.975: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "custom-resource-definition-8521" for this suite.

•
------------------------------
{"msg":"PASSED [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] Simple CustomResourceDefinition creating/deleting custom resource definition objects works  [Conformance]","total":-1,"completed":12,"skipped":103,"failed":0}
[BeforeEach] [Testpattern: Inline-volume (default fs)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:41.262: INFO: Driver local doesn't support InlineVolume -- skipping
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 37 lines ...
Oct  1 08:49:12.683: INFO: PersistentVolumeClaim pvc-x2ftq found but phase is Pending instead of Bound.
Oct  1 08:49:14.818: INFO: PersistentVolumeClaim pvc-x2ftq found and phase=Bound (10.813431689s)
Oct  1 08:49:14.818: INFO: Waiting up to 3m0s for PersistentVolume local-ssx54 to have phase Bound
Oct  1 08:49:14.952: INFO: PersistentVolume local-ssx54 found and phase=Bound (134.080936ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-s5s6
STEP: Creating a pod to test atomic-volume-subpath
Oct  1 08:49:15.357: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-s5s6" in namespace "provisioning-1749" to be "Succeeded or Failed"
Oct  1 08:49:15.506: INFO: Pod "pod-subpath-test-preprovisionedpv-s5s6": Phase="Pending", Reason="", readiness=false. Elapsed: 149.069098ms
Oct  1 08:49:17.641: INFO: Pod "pod-subpath-test-preprovisionedpv-s5s6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.283858177s
Oct  1 08:49:19.784: INFO: Pod "pod-subpath-test-preprovisionedpv-s5s6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.426903098s
Oct  1 08:49:21.923: INFO: Pod "pod-subpath-test-preprovisionedpv-s5s6": Phase="Running", Reason="", readiness=true. Elapsed: 6.566270048s
Oct  1 08:49:24.061: INFO: Pod "pod-subpath-test-preprovisionedpv-s5s6": Phase="Running", Reason="", readiness=true. Elapsed: 8.703804704s
Oct  1 08:49:26.209: INFO: Pod "pod-subpath-test-preprovisionedpv-s5s6": Phase="Running", Reason="", readiness=true. Elapsed: 10.852032542s
Oct  1 08:49:28.344: INFO: Pod "pod-subpath-test-preprovisionedpv-s5s6": Phase="Running", Reason="", readiness=true. Elapsed: 12.986713358s
Oct  1 08:49:30.478: INFO: Pod "pod-subpath-test-preprovisionedpv-s5s6": Phase="Running", Reason="", readiness=true. Elapsed: 15.121175432s
Oct  1 08:49:32.614: INFO: Pod "pod-subpath-test-preprovisionedpv-s5s6": Phase="Running", Reason="", readiness=true. Elapsed: 17.257251619s
Oct  1 08:49:34.749: INFO: Pod "pod-subpath-test-preprovisionedpv-s5s6": Phase="Running", Reason="", readiness=true. Elapsed: 19.392143946s
Oct  1 08:49:36.884: INFO: Pod "pod-subpath-test-preprovisionedpv-s5s6": Phase="Running", Reason="", readiness=true. Elapsed: 21.526916467s
Oct  1 08:49:39.019: INFO: Pod "pod-subpath-test-preprovisionedpv-s5s6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.661854843s
STEP: Saw pod success
Oct  1 08:49:39.019: INFO: Pod "pod-subpath-test-preprovisionedpv-s5s6" satisfied condition "Succeeded or Failed"
Oct  1 08:49:39.153: INFO: Trying to get logs from node ip-172-20-35-235.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-s5s6 container test-container-subpath-preprovisionedpv-s5s6: <nil>
STEP: delete the pod
Oct  1 08:49:39.439: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-s5s6 to disappear
Oct  1 08:49:39.573: INFO: Pod pod-subpath-test-preprovisionedpv-s5s6 no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-s5s6
Oct  1 08:49:39.573: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-s5s6" in namespace "provisioning-1749"
... skipping 19 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support file as subpath [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:227
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir-bindmounted] [Testpattern: Pre-provisioned PV (default fs)] subPath should support file as subpath [LinuxOnly]","total":-1,"completed":9,"skipped":90,"failed":0}

SSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:41.494: INFO: Driver local doesn't support ext4 -- skipping
... skipping 87 lines ...
Oct  1 08:49:23.555: INFO: Waiting for pod aws-client to disappear
Oct  1 08:49:23.687: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct  1 08:49:23.687: INFO: Deleting PersistentVolumeClaim "pvc-hxwpl"
Oct  1 08:49:23.819: INFO: Deleting PersistentVolume "aws-4r425"
Oct  1 08:49:24.369: INFO: Couldn't delete PD "aws://ap-northeast-1a/vol-08cc6c265f2cde698", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08cc6c265f2cde698 is currently attached to i-029bd822c8d7a82f8
	status code: 400, request id: 68508cc2-f8d0-4ffc-af4a-2214d7bdd3fe
Oct  1 08:49:30.089: INFO: Couldn't delete PD "aws://ap-northeast-1a/vol-08cc6c265f2cde698", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08cc6c265f2cde698 is currently attached to i-029bd822c8d7a82f8
	status code: 400, request id: bfb295ad-8c9d-4a82-9b5b-de928d827e0d
Oct  1 08:49:35.812: INFO: Couldn't delete PD "aws://ap-northeast-1a/vol-08cc6c265f2cde698", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08cc6c265f2cde698 is currently attached to i-029bd822c8d7a82f8
	status code: 400, request id: 614b1346-c3c5-431c-872f-8b3d3c32875b
Oct  1 08:49:41.565: INFO: Successfully deleted PD "aws://ap-northeast-1a/vol-08cc6c265f2cde698".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:49:41.565: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2316" for this suite.
... skipping 6 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] volumes
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should store data
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:151
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: aws] [Testpattern: Pre-provisioned PV (default fs)] volumes should store data","total":-1,"completed":3,"skipped":26,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][sig-windows] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:41.860: INFO: Driver emptydir doesn't support DynamicPV -- skipping
... skipping 51 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Inline-volume (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should be able to unmount after the subpath directory is deleted [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:441
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: hostPath] [Testpattern: Inline-volume (default fs)] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly]","total":-1,"completed":10,"skipped":64,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:42.497: INFO: Only supported for node OS distro [gci ubuntu custom] (not debian)
... skipping 217 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:49:45.223: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "pods-462" for this suite.

•
------------------------------
{"msg":"PASSED [k8s.io] Pods should get a host IP [NodeConformance] [Conformance]","total":-1,"completed":4,"skipped":29,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 2 lines ...
Oct  1 08:49:20.770: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
[It] should be able to unmount after the subpath directory is deleted [LinuxOnly]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:441
Oct  1 08:49:21.438: INFO: In-tree plugin kubernetes.io/host-path is not migrated, not validating any metrics
Oct  1 08:49:21.708: INFO: Waiting up to 5m0s for pod "hostpath-symlink-prep-provisioning-7774" in namespace "provisioning-7774" to be "Succeeded or Failed"
Oct  1 08:49:21.841: INFO: Pod "hostpath-symlink-prep-provisioning-7774": Phase="Pending", Reason="", readiness=false. Elapsed: 133.474844ms
Oct  1 08:49:23.976: INFO: Pod "hostpath-symlink-prep-provisioning-7774": Phase="Pending", Reason="", readiness=false. Elapsed: 2.268741788s
Oct  1 08:49:26.123: INFO: Pod "hostpath-symlink-prep-provisioning-7774": Phase="Pending", Reason="", readiness=false. Elapsed: 4.414997106s
Oct  1 08:49:28.265: INFO: Pod "hostpath-symlink-prep-provisioning-7774": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.55722047s
STEP: Saw pod success
Oct  1 08:49:28.265: INFO: Pod "hostpath-symlink-prep-provisioning-7774" satisfied condition "Succeeded or Failed"
Oct  1 08:49:28.265: INFO: Deleting pod "hostpath-symlink-prep-provisioning-7774" in namespace "provisioning-7774"
Oct  1 08:49:28.404: INFO: Wait up to 5m0s for pod "hostpath-symlink-prep-provisioning-7774" to be fully deleted
Oct  1 08:49:28.537: INFO: Creating resource for inline volume
STEP: Creating pod pod-subpath-test-inlinevolume-znzv
Oct  1 08:49:34.944: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=provisioning-7774 exec pod-subpath-test-inlinevolume-znzv --container test-container-volume-inlinevolume-znzv -- /bin/sh -c rm -r /test-volume/provisioning-7774'
Oct  1 08:49:36.308: INFO: stderr: ""
Oct  1 08:49:36.308: INFO: stdout: ""
STEP: Deleting pod pod-subpath-test-inlinevolume-znzv
Oct  1 08:49:36.308: INFO: Deleting pod "pod-subpath-test-inlinevolume-znzv" in namespace "provisioning-7774"
Oct  1 08:49:36.442: INFO: Wait up to 5m0s for pod "pod-subpath-test-inlinevolume-znzv" to be fully deleted
STEP: Deleting pod
Oct  1 08:49:48.709: INFO: Deleting pod "pod-subpath-test-inlinevolume-znzv" in namespace "provisioning-7774"
Oct  1 08:49:48.976: INFO: Waiting up to 5m0s for pod "hostpath-symlink-prep-provisioning-7774" in namespace "provisioning-7774" to be "Succeeded or Failed"
Oct  1 08:49:49.109: INFO: Pod "hostpath-symlink-prep-provisioning-7774": Phase="Pending", Reason="", readiness=false. Elapsed: 133.098297ms
Oct  1 08:49:51.243: INFO: Pod "hostpath-symlink-prep-provisioning-7774": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.266678637s
STEP: Saw pod success
Oct  1 08:49:51.243: INFO: Pod "hostpath-symlink-prep-provisioning-7774" satisfied condition "Succeeded or Failed"
Oct  1 08:49:51.243: INFO: Deleting pod "hostpath-symlink-prep-provisioning-7774" in namespace "provisioning-7774"
Oct  1 08:49:51.380: INFO: Wait up to 5m0s for pod "hostpath-symlink-prep-provisioning-7774" to be fully deleted
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:49:51.514: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "provisioning-7774" for this suite.
... skipping 6 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Inline-volume (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should be able to unmount after the subpath directory is deleted [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:441
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: hostPathSymlink] [Testpattern: Inline-volume (default fs)] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly]","total":-1,"completed":4,"skipped":51,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:51.798: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 104 lines ...
Oct  1 08:49:43.247: INFO: PersistentVolumeClaim pvc-jkk28 found but phase is Pending instead of Bound.
Oct  1 08:49:45.384: INFO: PersistentVolumeClaim pvc-jkk28 found and phase=Bound (8.664846339s)
Oct  1 08:49:45.384: INFO: Waiting up to 3m0s for PersistentVolume local-8clt2 to have phase Bound
Oct  1 08:49:45.516: INFO: PersistentVolume local-8clt2 found and phase=Bound (132.641835ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-k544
STEP: Creating a pod to test exec-volume-test
Oct  1 08:49:45.914: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-k544" in namespace "volume-2116" to be "Succeeded or Failed"
Oct  1 08:49:46.047: INFO: Pod "exec-volume-test-preprovisionedpv-k544": Phase="Pending", Reason="", readiness=false. Elapsed: 132.357613ms
Oct  1 08:49:48.179: INFO: Pod "exec-volume-test-preprovisionedpv-k544": Phase="Pending", Reason="", readiness=false. Elapsed: 2.264629972s
Oct  1 08:49:50.311: INFO: Pod "exec-volume-test-preprovisionedpv-k544": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.396727579s
STEP: Saw pod success
Oct  1 08:49:50.311: INFO: Pod "exec-volume-test-preprovisionedpv-k544" satisfied condition "Succeeded or Failed"
Oct  1 08:49:50.443: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod exec-volume-test-preprovisionedpv-k544 container exec-container-preprovisionedpv-k544: <nil>
STEP: delete the pod
Oct  1 08:49:50.714: INFO: Waiting for pod exec-volume-test-preprovisionedpv-k544 to disappear
Oct  1 08:49:50.846: INFO: Pod exec-volume-test-preprovisionedpv-k544 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-k544
Oct  1 08:49:50.846: INFO: Deleting pod "exec-volume-test-preprovisionedpv-k544" in namespace "volume-2116"
... skipping 17 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] volumes
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should allow exec of files on the volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:192
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir-link-bindmounted] [Testpattern: Pre-provisioned PV (default fs)] volumes should allow exec of files on the volume","total":-1,"completed":10,"skipped":62,"failed":0}

SSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 26 lines ...
Oct  1 08:49:42.638: INFO: PersistentVolumeClaim pvc-qsqlg found but phase is Pending instead of Bound.
Oct  1 08:49:44.771: INFO: PersistentVolumeClaim pvc-qsqlg found and phase=Bound (15.067842421s)
Oct  1 08:49:44.771: INFO: Waiting up to 3m0s for PersistentVolume local-k5mz4 to have phase Bound
Oct  1 08:49:44.908: INFO: PersistentVolume local-k5mz4 found and phase=Bound (136.780342ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-fp4k
STEP: Creating a pod to test subpath
Oct  1 08:49:45.309: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-fp4k" in namespace "provisioning-8601" to be "Succeeded or Failed"
Oct  1 08:49:45.442: INFO: Pod "pod-subpath-test-preprovisionedpv-fp4k": Phase="Pending", Reason="", readiness=false. Elapsed: 133.096888ms
Oct  1 08:49:47.610: INFO: Pod "pod-subpath-test-preprovisionedpv-fp4k": Phase="Pending", Reason="", readiness=false. Elapsed: 2.300536394s
Oct  1 08:49:49.743: INFO: Pod "pod-subpath-test-preprovisionedpv-fp4k": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.434111524s
STEP: Saw pod success
Oct  1 08:49:49.743: INFO: Pod "pod-subpath-test-preprovisionedpv-fp4k" satisfied condition "Succeeded or Failed"
Oct  1 08:49:49.880: INFO: Trying to get logs from node ip-172-20-41-255.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-fp4k container test-container-volume-preprovisionedpv-fp4k: <nil>
STEP: delete the pod
Oct  1 08:49:50.153: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-fp4k to disappear
Oct  1 08:49:50.287: INFO: Pod pod-subpath-test-preprovisionedpv-fp4k no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-fp4k
Oct  1 08:49:50.287: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-fp4k" in namespace "provisioning-8601"
... skipping 26 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support non-existent path
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:191
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: blockfs] [Testpattern: Pre-provisioned PV (default fs)] subPath should support non-existent path","total":-1,"completed":6,"skipped":15,"failed":0}

SSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 24 lines ...
Oct  1 08:49:44.212: INFO: PersistentVolumeClaim pvc-b4dhj found but phase is Pending instead of Bound.
Oct  1 08:49:46.343: INFO: PersistentVolumeClaim pvc-b4dhj found and phase=Bound (15.05078057s)
Oct  1 08:49:46.343: INFO: Waiting up to 3m0s for PersistentVolume local-p5qjr to have phase Bound
Oct  1 08:49:46.475: INFO: PersistentVolume local-p5qjr found and phase=Bound (131.960993ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-gxtl
STEP: Creating a pod to test subpath
Oct  1 08:49:46.874: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-gxtl" in namespace "provisioning-152" to be "Succeeded or Failed"
Oct  1 08:49:47.008: INFO: Pod "pod-subpath-test-preprovisionedpv-gxtl": Phase="Pending", Reason="", readiness=false. Elapsed: 133.41505ms
Oct  1 08:49:49.139: INFO: Pod "pod-subpath-test-preprovisionedpv-gxtl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.264517335s
Oct  1 08:49:51.270: INFO: Pod "pod-subpath-test-preprovisionedpv-gxtl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.39554845s
STEP: Saw pod success
Oct  1 08:49:51.270: INFO: Pod "pod-subpath-test-preprovisionedpv-gxtl" satisfied condition "Succeeded or Failed"
Oct  1 08:49:51.401: INFO: Trying to get logs from node ip-172-20-41-255.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-gxtl container test-container-subpath-preprovisionedpv-gxtl: <nil>
STEP: delete the pod
Oct  1 08:49:51.673: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-gxtl to disappear
Oct  1 08:49:51.803: INFO: Pod pod-subpath-test-preprovisionedpv-gxtl no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-gxtl
Oct  1 08:49:51.803: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-gxtl" in namespace "provisioning-152"
... skipping 24 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support existing single file [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:216
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: block] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing single file [LinuxOnly]","total":-1,"completed":9,"skipped":78,"failed":0}

SSS
------------------------------
[BeforeEach] [sig-storage] PersistentVolumes-local 
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 62 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:188
    One pod requesting one prebound PVC
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:205
      should be able to mount volume and read from pod1
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:228
------------------------------
{"msg":"PASSED [sig-storage] PersistentVolumes-local  [Volume type: blockfswithoutformat] One pod requesting one prebound PVC should be able to mount volume and read from pod1","total":-1,"completed":11,"skipped":75,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:56.415: INFO: Only supported for providers [azure] (not aws)
[AfterEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 149 lines ...
Oct  1 08:49:43.196: INFO: PersistentVolumeClaim pvc-jc9lm found but phase is Pending instead of Bound.
Oct  1 08:49:45.334: INFO: PersistentVolumeClaim pvc-jc9lm found and phase=Bound (12.956650463s)
Oct  1 08:49:45.334: INFO: Waiting up to 3m0s for PersistentVolume local-75wzl to have phase Bound
Oct  1 08:49:45.470: INFO: PersistentVolume local-75wzl found and phase=Bound (135.740248ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-4fp9
STEP: Creating a pod to test subpath
Oct  1 08:49:45.878: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-4fp9" in namespace "provisioning-1597" to be "Succeeded or Failed"
Oct  1 08:49:46.013: INFO: Pod "pod-subpath-test-preprovisionedpv-4fp9": Phase="Pending", Reason="", readiness=false. Elapsed: 135.470966ms
Oct  1 08:49:48.150: INFO: Pod "pod-subpath-test-preprovisionedpv-4fp9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.272341207s
Oct  1 08:49:50.286: INFO: Pod "pod-subpath-test-preprovisionedpv-4fp9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.408210288s
Oct  1 08:49:52.422: INFO: Pod "pod-subpath-test-preprovisionedpv-4fp9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.544064893s
Oct  1 08:49:54.557: INFO: Pod "pod-subpath-test-preprovisionedpv-4fp9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.679860457s
STEP: Saw pod success
Oct  1 08:49:54.558: INFO: Pod "pod-subpath-test-preprovisionedpv-4fp9" satisfied condition "Succeeded or Failed"
Oct  1 08:49:54.701: INFO: Trying to get logs from node ip-172-20-60-245.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-4fp9 container test-container-subpath-preprovisionedpv-4fp9: <nil>
STEP: delete the pod
Oct  1 08:49:54.984: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-4fp9 to disappear
Oct  1 08:49:55.120: INFO: Pod pod-subpath-test-preprovisionedpv-4fp9 no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-4fp9
Oct  1 08:49:55.120: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-4fp9" in namespace "provisioning-1597"
... skipping 19 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support readOnly file specified in the volumeMount [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:376
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir-link-bindmounted] [Testpattern: Pre-provisioned PV (default fs)] subPath should support readOnly file specified in the volumeMount [LinuxOnly]","total":-1,"completed":12,"skipped":119,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:57.051: INFO: Only supported for providers [openstack] (not aws)
[AfterEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 234 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_volumes.go:39
    [Testpattern: Dynamic PV (default fs)] volumes
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should store data
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:151
------------------------------
{"msg":"PASSED [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] volumes should store data","total":-1,"completed":8,"skipped":74,"failed":0}
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:49:58.053: INFO: Driver local doesn't support InlineVolume -- skipping
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 140 lines ...
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [sig-storage] Projected downwardAPI
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_downwardapi.go:41
[It] should provide container's memory request [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating a pod to test downward API volume plugin
Oct  1 08:49:57.948: INFO: Waiting up to 5m0s for pod "downwardapi-volume-3564050f-19b4-4e18-9551-e7e6f76c5676" in namespace "projected-9405" to be "Succeeded or Failed"
Oct  1 08:49:58.083: INFO: Pod "downwardapi-volume-3564050f-19b4-4e18-9551-e7e6f76c5676": Phase="Pending", Reason="", readiness=false. Elapsed: 135.338381ms
Oct  1 08:50:00.220: INFO: Pod "downwardapi-volume-3564050f-19b4-4e18-9551-e7e6f76c5676": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.27233091s
STEP: Saw pod success
Oct  1 08:50:00.220: INFO: Pod "downwardapi-volume-3564050f-19b4-4e18-9551-e7e6f76c5676" satisfied condition "Succeeded or Failed"
Oct  1 08:50:00.366: INFO: Trying to get logs from node ip-172-20-41-255.ap-northeast-1.compute.internal pod downwardapi-volume-3564050f-19b4-4e18-9551-e7e6f76c5676 container client-container: <nil>
STEP: delete the pod
Oct  1 08:50:00.696: INFO: Waiting for pod downwardapi-volume-3564050f-19b4-4e18-9551-e7e6f76c5676 to disappear
Oct  1 08:50:00.832: INFO: Pod downwardapi-volume-3564050f-19b4-4e18-9551-e7e6f76c5676 no longer exists
[AfterEach] [sig-storage] Projected downwardAPI
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:50:00.832: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "projected-9405" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] Projected downwardAPI should provide container's memory request [NodeConformance] [Conformance]","total":-1,"completed":13,"skipped":135,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:50:01.128: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 218 lines ...
• [SLOW TEST:13.601 seconds]
[sig-apps] CronJob
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23
  should be able to schedule after more than 100 missed schedule
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/cronjob.go:173
------------------------------
{"msg":"PASSED [sig-apps] CronJob should be able to schedule after more than 100 missed schedule","total":-1,"completed":11,"skipped":72,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][sig-windows] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:50:06.220: INFO: Driver hostPathSymlink doesn't support DynamicPV -- skipping
... skipping 14 lines ...
      Driver hostPathSymlink doesn't support DynamicPV -- skipping

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:173
------------------------------
SS
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: aws] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (Always)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents","total":-1,"completed":8,"skipped":36,"failed":0}
[BeforeEach] [sig-storage] EmptyDir volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:50:00.810: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename emptydir
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] when FSGroup is specified [LinuxOnly] [NodeFeature:FSGroup]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/empty_dir.go:50
[It] new files should be created with FSGroup ownership when container is non-root
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/empty_dir.go:59
STEP: Creating a pod to test emptydir 0644 on tmpfs
Oct  1 08:50:01.605: INFO: Waiting up to 5m0s for pod "pod-26282890-4b31-443c-b571-b09431c74c4d" in namespace "emptydir-9660" to be "Succeeded or Failed"
Oct  1 08:50:01.736: INFO: Pod "pod-26282890-4b31-443c-b571-b09431c74c4d": Phase="Pending", Reason="", readiness=false. Elapsed: 131.698051ms
Oct  1 08:50:03.868: INFO: Pod "pod-26282890-4b31-443c-b571-b09431c74c4d": Phase="Running", Reason="", readiness=true. Elapsed: 2.263692902s
Oct  1 08:50:06.004: INFO: Pod "pod-26282890-4b31-443c-b571-b09431c74c4d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.39900165s
STEP: Saw pod success
Oct  1 08:50:06.004: INFO: Pod "pod-26282890-4b31-443c-b571-b09431c74c4d" satisfied condition "Succeeded or Failed"
Oct  1 08:50:06.136: INFO: Trying to get logs from node ip-172-20-41-255.ap-northeast-1.compute.internal pod pod-26282890-4b31-443c-b571-b09431c74c4d container test-container: <nil>
STEP: delete the pod
Oct  1 08:50:06.407: INFO: Waiting for pod pod-26282890-4b31-443c-b571-b09431c74c4d to disappear
Oct  1 08:50:06.539: INFO: Pod pod-26282890-4b31-443c-b571-b09431c74c4d no longer exists
[AfterEach] [sig-storage] EmptyDir volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 6 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/empty_dir.go:45
  when FSGroup is specified [LinuxOnly] [NodeFeature:FSGroup]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/empty_dir.go:48
    new files should be created with FSGroup ownership when container is non-root
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/empty_dir.go:59
------------------------------
{"msg":"PASSED [sig-storage] EmptyDir volumes when FSGroup is specified [LinuxOnly] [NodeFeature:FSGroup] new files should be created with FSGroup ownership when container is non-root","total":-1,"completed":9,"skipped":36,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:50:06.813: INFO: Driver hostPath doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 34 lines ...
      Only supported for node OS distro [gci ubuntu custom] (not debian)

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/drivers/in_tree.go:265
------------------------------
S
------------------------------
{"msg":"PASSED [sig-instrumentation] MetricsGrabber should grab all metrics from a ControllerManager.","total":-1,"completed":7,"skipped":42,"failed":0}
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:49:40.414: INFO: >>> kubeConfig: /root/.kube/config
... skipping 18 lines ...
Oct  1 08:49:57.754: INFO: PersistentVolumeClaim pvc-7fpsm found but phase is Pending instead of Bound.
Oct  1 08:49:59.890: INFO: PersistentVolumeClaim pvc-7fpsm found and phase=Bound (15.080884533s)
Oct  1 08:49:59.890: INFO: Waiting up to 3m0s for PersistentVolume local-8pj6r to have phase Bound
Oct  1 08:50:00.024: INFO: PersistentVolume local-8pj6r found and phase=Bound (134.226719ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-thr6
STEP: Creating a pod to test subpath
Oct  1 08:50:00.460: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-thr6" in namespace "provisioning-8127" to be "Succeeded or Failed"
Oct  1 08:50:00.603: INFO: Pod "pod-subpath-test-preprovisionedpv-thr6": Phase="Pending", Reason="", readiness=false. Elapsed: 142.535099ms
Oct  1 08:50:02.738: INFO: Pod "pod-subpath-test-preprovisionedpv-thr6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.277564741s
Oct  1 08:50:04.873: INFO: Pod "pod-subpath-test-preprovisionedpv-thr6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.41288125s
STEP: Saw pod success
Oct  1 08:50:04.873: INFO: Pod "pod-subpath-test-preprovisionedpv-thr6" satisfied condition "Succeeded or Failed"
Oct  1 08:50:05.009: INFO: Trying to get logs from node ip-172-20-41-255.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-thr6 container test-container-subpath-preprovisionedpv-thr6: <nil>
STEP: delete the pod
Oct  1 08:50:05.318: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-thr6 to disappear
Oct  1 08:50:05.453: INFO: Pod pod-subpath-test-preprovisionedpv-thr6 no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-thr6
Oct  1 08:50:05.453: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-thr6" in namespace "provisioning-8127"
... skipping 19 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support readOnly directory specified in the volumeMount
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:361
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir-link] [Testpattern: Pre-provisioned PV (default fs)] subPath should support readOnly directory specified in the volumeMount","total":-1,"completed":8,"skipped":42,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ext3)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:50:07.292: INFO: Only supported for node OS distro [gci ubuntu custom] (not debian)
... skipping 87 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:50:09.746: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "resourcequota-8762" for this suite.

•
------------------------------
{"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","total":-1,"completed":9,"skipped":39,"failed":0}
[BeforeEach] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:49:05.667: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename crd-publish-openapi
STEP: Waiting for a default service account to be provisioned in namespace
... skipping 13 lines ...
• [SLOW TEST:65.431 seconds]
[sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin]
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
  works for multiple CRDs of same group but different versions [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for multiple CRDs of same group but different versions [Conformance]","total":-1,"completed":10,"skipped":39,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:50:11.114: INFO: Driver local doesn't support InlineVolume -- skipping
... skipping 12 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:376

      Driver local doesn't support InlineVolume -- skipping

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:173
------------------------------
{"msg":"PASSED [sig-api-machinery] ResourceQuota should be able to update and delete ResourceQuota. [Conformance]","total":-1,"completed":9,"skipped":46,"failed":0}
[BeforeEach] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:50:10.026: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename custom-resource-definition
STEP: Waiting for a default service account to be provisioned in namespace
... skipping 4 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:50:12.336: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "custom-resource-definition-2234" for this suite.

•
------------------------------
{"msg":"PASSED [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] custom resource defaulting for requests and from storage works  [Conformance]","total":-1,"completed":10,"skipped":46,"failed":0}

S
------------------------------
[BeforeEach] [sig-apps] StatefulSet
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 48 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23
  [k8s.io] Basic StatefulSet functionality [StatefulSetBasic]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
    should implement legacy replacement when the update strategy is OnDelete
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/statefulset.go:499
------------------------------
{"msg":"PASSED [sig-apps] StatefulSet [k8s.io] Basic StatefulSet functionality [StatefulSetBasic] should implement legacy replacement when the update strategy is OnDelete","total":-1,"completed":5,"skipped":35,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:50:12.922: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 96 lines ...
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [sig-storage] Downward API volume
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/downwardapi_volume.go:41
[It] should provide node allocatable (memory) as default memory limit if the limit is not set [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating a pod to test downward API volume plugin
Oct  1 08:50:11.976: INFO: Waiting up to 5m0s for pod "downwardapi-volume-d17d7e96-c8f5-4553-b76e-f6b415451682" in namespace "downward-api-7751" to be "Succeeded or Failed"
Oct  1 08:50:12.110: INFO: Pod "downwardapi-volume-d17d7e96-c8f5-4553-b76e-f6b415451682": Phase="Pending", Reason="", readiness=false. Elapsed: 134.261264ms
Oct  1 08:50:14.259: INFO: Pod "downwardapi-volume-d17d7e96-c8f5-4553-b76e-f6b415451682": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.28290556s
STEP: Saw pod success
Oct  1 08:50:14.259: INFO: Pod "downwardapi-volume-d17d7e96-c8f5-4553-b76e-f6b415451682" satisfied condition "Succeeded or Failed"
Oct  1 08:50:14.390: INFO: Trying to get logs from node ip-172-20-41-255.ap-northeast-1.compute.internal pod downwardapi-volume-d17d7e96-c8f5-4553-b76e-f6b415451682 container client-container: <nil>
STEP: delete the pod
Oct  1 08:50:14.661: INFO: Waiting for pod downwardapi-volume-d17d7e96-c8f5-4553-b76e-f6b415451682 to disappear
Oct  1 08:50:14.792: INFO: Pod downwardapi-volume-d17d7e96-c8f5-4553-b76e-f6b415451682 no longer exists
[AfterEach] [sig-storage] Downward API volume
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:50:14.792: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "downward-api-7751" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] Downward API volume should provide node allocatable (memory) as default memory limit if the limit is not set [NodeConformance] [Conformance]","total":-1,"completed":11,"skipped":42,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:50:15.070: INFO: Driver local doesn't support InlineVolume -- skipping
... skipping 48 lines ...
• [SLOW TEST:18.735 seconds]
[sig-api-machinery] ResourceQuota
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
  should verify ResourceQuota with terminating scopes. [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-api-machinery] ResourceQuota should verify ResourceQuota with terminating scopes. [Conformance]","total":-1,"completed":9,"skipped":79,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:50:16.832: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 44 lines ...
Oct  1 08:50:12.949: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename emptydir
STEP: Waiting for a default service account to be provisioned in namespace
[It] should support (non-root,0644,default) [LinuxOnly] [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating a pod to test emptydir 0644 on node default medium
Oct  1 08:50:13.754: INFO: Waiting up to 5m0s for pod "pod-0ea3c250-31bd-4af2-b919-35e3eb889248" in namespace "emptydir-4708" to be "Succeeded or Failed"
Oct  1 08:50:13.888: INFO: Pod "pod-0ea3c250-31bd-4af2-b919-35e3eb889248": Phase="Pending", Reason="", readiness=false. Elapsed: 133.674489ms
Oct  1 08:50:16.021: INFO: Pod "pod-0ea3c250-31bd-4af2-b919-35e3eb889248": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.266979761s
STEP: Saw pod success
Oct  1 08:50:16.022: INFO: Pod "pod-0ea3c250-31bd-4af2-b919-35e3eb889248" satisfied condition "Succeeded or Failed"
Oct  1 08:50:16.154: INFO: Trying to get logs from node ip-172-20-41-255.ap-northeast-1.compute.internal pod pod-0ea3c250-31bd-4af2-b919-35e3eb889248 container test-container: <nil>
STEP: delete the pod
Oct  1 08:50:16.445: INFO: Waiting for pod pod-0ea3c250-31bd-4af2-b919-35e3eb889248 to disappear
Oct  1 08:50:16.578: INFO: Pod pod-0ea3c250-31bd-4af2-b919-35e3eb889248 no longer exists
[AfterEach] [sig-storage] EmptyDir volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:50:16.578: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "emptydir-4708" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] EmptyDir volumes should support (non-root,0644,default) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":6,"skipped":41,"failed":0}

SSSSS
------------------------------
[BeforeEach] [k8s.io] [sig-node] NodeProblemDetector [DisabledForLargeClusters]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 9 lines ...
STEP: Destroying namespace "node-problem-detector-902" for this suite.


S [SKIPPING] in Spec Setup (BeforeEach) [0.935 seconds]
[k8s.io] [sig-node] NodeProblemDetector [DisabledForLargeClusters]
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  should run without error [BeforeEach]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/node/node_problem_detector.go:59

  Only supported for providers [gce gke] (not aws)

  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/node/node_problem_detector.go:54
------------------------------
... skipping 95 lines ...
Oct  1 08:49:51.827: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
[It] should support file as subpath [LinuxOnly]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:227
Oct  1 08:49:52.493: INFO: In-tree plugin kubernetes.io/host-path is not migrated, not validating any metrics
Oct  1 08:49:52.762: INFO: Waiting up to 5m0s for pod "hostpath-symlink-prep-provisioning-3663" in namespace "provisioning-3663" to be "Succeeded or Failed"
Oct  1 08:49:52.896: INFO: Pod "hostpath-symlink-prep-provisioning-3663": Phase="Pending", Reason="", readiness=false. Elapsed: 133.066933ms
Oct  1 08:49:55.029: INFO: Pod "hostpath-symlink-prep-provisioning-3663": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.266727053s
STEP: Saw pod success
Oct  1 08:49:55.029: INFO: Pod "hostpath-symlink-prep-provisioning-3663" satisfied condition "Succeeded or Failed"
Oct  1 08:49:55.029: INFO: Deleting pod "hostpath-symlink-prep-provisioning-3663" in namespace "provisioning-3663"
Oct  1 08:49:55.167: INFO: Wait up to 5m0s for pod "hostpath-symlink-prep-provisioning-3663" to be fully deleted
Oct  1 08:49:55.300: INFO: Creating resource for inline volume
STEP: Creating pod pod-subpath-test-inlinevolume-b84m
STEP: Creating a pod to test atomic-volume-subpath
Oct  1 08:49:55.435: INFO: Waiting up to 5m0s for pod "pod-subpath-test-inlinevolume-b84m" in namespace "provisioning-3663" to be "Succeeded or Failed"
Oct  1 08:49:55.568: INFO: Pod "pod-subpath-test-inlinevolume-b84m": Phase="Pending", Reason="", readiness=false. Elapsed: 133.461061ms
Oct  1 08:49:57.704: INFO: Pod "pod-subpath-test-inlinevolume-b84m": Phase="Running", Reason="", readiness=true. Elapsed: 2.269266744s
Oct  1 08:49:59.838: INFO: Pod "pod-subpath-test-inlinevolume-b84m": Phase="Running", Reason="", readiness=true. Elapsed: 4.402775882s
Oct  1 08:50:01.973: INFO: Pod "pod-subpath-test-inlinevolume-b84m": Phase="Running", Reason="", readiness=true. Elapsed: 6.538114731s
Oct  1 08:50:04.107: INFO: Pod "pod-subpath-test-inlinevolume-b84m": Phase="Running", Reason="", readiness=true. Elapsed: 8.671822031s
Oct  1 08:50:06.241: INFO: Pod "pod-subpath-test-inlinevolume-b84m": Phase="Running", Reason="", readiness=true. Elapsed: 10.805818107s
Oct  1 08:50:08.374: INFO: Pod "pod-subpath-test-inlinevolume-b84m": Phase="Running", Reason="", readiness=true. Elapsed: 12.939443516s
Oct  1 08:50:10.508: INFO: Pod "pod-subpath-test-inlinevolume-b84m": Phase="Running", Reason="", readiness=true. Elapsed: 15.072960157s
Oct  1 08:50:12.642: INFO: Pod "pod-subpath-test-inlinevolume-b84m": Phase="Running", Reason="", readiness=true. Elapsed: 17.207420965s
Oct  1 08:50:14.776: INFO: Pod "pod-subpath-test-inlinevolume-b84m": Phase="Running", Reason="", readiness=true. Elapsed: 19.341173057s
Oct  1 08:50:16.910: INFO: Pod "pod-subpath-test-inlinevolume-b84m": Phase="Running", Reason="", readiness=true. Elapsed: 21.47496749s
Oct  1 08:50:19.043: INFO: Pod "pod-subpath-test-inlinevolume-b84m": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.60859895s
STEP: Saw pod success
Oct  1 08:50:19.044: INFO: Pod "pod-subpath-test-inlinevolume-b84m" satisfied condition "Succeeded or Failed"
Oct  1 08:50:19.177: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod pod-subpath-test-inlinevolume-b84m container test-container-subpath-inlinevolume-b84m: <nil>
STEP: delete the pod
Oct  1 08:50:19.458: INFO: Waiting for pod pod-subpath-test-inlinevolume-b84m to disappear
Oct  1 08:50:19.591: INFO: Pod pod-subpath-test-inlinevolume-b84m no longer exists
STEP: Deleting pod pod-subpath-test-inlinevolume-b84m
Oct  1 08:50:19.591: INFO: Deleting pod "pod-subpath-test-inlinevolume-b84m" in namespace "provisioning-3663"
STEP: Deleting pod
Oct  1 08:50:19.725: INFO: Deleting pod "pod-subpath-test-inlinevolume-b84m" in namespace "provisioning-3663"
Oct  1 08:50:19.993: INFO: Waiting up to 5m0s for pod "hostpath-symlink-prep-provisioning-3663" in namespace "provisioning-3663" to be "Succeeded or Failed"
Oct  1 08:50:20.126: INFO: Pod "hostpath-symlink-prep-provisioning-3663": Phase="Pending", Reason="", readiness=false. Elapsed: 133.212914ms
Oct  1 08:50:22.259: INFO: Pod "hostpath-symlink-prep-provisioning-3663": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.266489997s
STEP: Saw pod success
Oct  1 08:50:22.259: INFO: Pod "hostpath-symlink-prep-provisioning-3663" satisfied condition "Succeeded or Failed"
Oct  1 08:50:22.259: INFO: Deleting pod "hostpath-symlink-prep-provisioning-3663" in namespace "provisioning-3663"
Oct  1 08:50:22.402: INFO: Wait up to 5m0s for pod "hostpath-symlink-prep-provisioning-3663" to be fully deleted
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 08:50:22.536: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "provisioning-3663" for this suite.
... skipping 6 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Inline-volume (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support file as subpath [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:227
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: hostPathSymlink] [Testpattern: Inline-volume (default fs)] subPath should support file as subpath [LinuxOnly]","total":-1,"completed":5,"skipped":58,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ntfs)][sig-windows] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:50:22.821: INFO: Driver hostPath doesn't support PreprovisionedPV -- skipping
... skipping 152 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:188
    One pod requesting one prebound PVC
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:205
      should be able to mount volume and read from pod1
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:228
------------------------------
{"msg":"PASSED [sig-storage] PersistentVolumes-local  [Volume type: blockfswithformat] One pod requesting one prebound PVC should be able to mount volume and read from pod1","total":-1,"completed":12,"skipped":78,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 08:50:26.198: INFO: Only supported for providers [openstack] (not aws)
... skipping 47783 lines ...
ct  1 08:59:26.683: INFO: Unable to read jessie_tcp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:26.818: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:26.953: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:27.088: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:27.358: INFO: Unable to read jessie_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:27.493: INFO: Unable to read jessie_tcp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:27.764: INFO: Lookups using dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c failed for: [wheezy_udp@dns-test-service.dns-2383.svc wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc wheezy_udp@PodARecord jessie_udp@dns-test-service jessie_udp@dns-test-service.dns-2383 jessie_tcp@dns-test-service.dns-2383 jessie_udp@dns-test-service.dns-2383.svc jessie_tcp@dns-test-service.dns-2383.svc jessie_udp@_http._tcp.dns-test-service.dns-2383.svc jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc jessie_udp@_http._tcp.test-service-2.dns-2383.svc jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:59:29.644: INFO: Unable to read wheezy_udp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:29.914: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:30.456: INFO: Unable to read wheezy_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:30.999: INFO: Unable to read jessie_udp@dns-test-service from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:31.273: INFO: Unable to read jessie_udp@dns-test-service.dns-2383 from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
... skipping 2 lines ...
Oct  1 08:59:31.678: INFO: Unable to read jessie_tcp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:31.814: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:31.949: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:32.084: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:32.356: INFO: Unable to read jessie_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:32.492: INFO: Unable to read jessie_tcp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:32.765: INFO: Lookups using dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c failed for: [wheezy_udp@dns-test-service.dns-2383.svc wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc wheezy_udp@PodARecord jessie_udp@dns-test-service jessie_udp@dns-test-service.dns-2383 jessie_tcp@dns-test-service.dns-2383 jessie_udp@dns-test-service.dns-2383.svc jessie_tcp@dns-test-service.dns-2383.svc jessie_udp@_http._tcp.dns-test-service.dns-2383.svc jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc jessie_udp@_http._tcp.test-service-2.dns-2383.svc jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:59:34.642: INFO: Unable to read wheezy_udp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:34.912: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:35.452: INFO: Unable to read wheezy_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:35.995: INFO: Unable to read jessie_udp@dns-test-service from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:36.266: INFO: Unable to read jessie_udp@dns-test-service.dns-2383 from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
... skipping 2 lines ...
Oct  1 08:59:36.674: INFO: Unable to read jessie_tcp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:36.809: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:36.944: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:37.080: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:37.352: INFO: Unable to read jessie_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:37.492: INFO: Unable to read jessie_tcp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:37.762: INFO: Lookups using dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c failed for: [wheezy_udp@dns-test-service.dns-2383.svc wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc wheezy_udp@PodARecord jessie_udp@dns-test-service jessie_udp@dns-test-service.dns-2383 jessie_tcp@dns-test-service.dns-2383 jessie_udp@dns-test-service.dns-2383.svc jessie_tcp@dns-test-service.dns-2383.svc jessie_udp@_http._tcp.dns-test-service.dns-2383.svc jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc jessie_udp@_http._tcp.test-service-2.dns-2383.svc jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:59:39.642: INFO: Unable to read wheezy_udp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:39.913: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:40.456: INFO: Unable to read wheezy_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:40.998: INFO: Unable to read jessie_udp@dns-test-service from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:41.269: INFO: Unable to read jessie_udp@dns-test-service.dns-2383 from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
... skipping 2 lines ...
Oct  1 08:59:41.675: INFO: Unable to read jessie_tcp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:41.813: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:41.948: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:42.083: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:42.365: INFO: Unable to read jessie_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:42.500: INFO: Unable to read jessie_tcp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:42.770: INFO: Lookups using dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c failed for: [wheezy_udp@dns-test-service.dns-2383.svc wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc wheezy_udp@PodARecord jessie_udp@dns-test-service jessie_udp@dns-test-service.dns-2383 jessie_tcp@dns-test-service.dns-2383 jessie_udp@dns-test-service.dns-2383.svc jessie_tcp@dns-test-service.dns-2383.svc jessie_udp@_http._tcp.dns-test-service.dns-2383.svc jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc jessie_udp@_http._tcp.test-service-2.dns-2383.svc jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:59:44.658: INFO: Unable to read wheezy_udp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:44.936: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:45.480: INFO: Unable to read wheezy_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:46.021: INFO: Unable to read jessie_udp@dns-test-service from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:46.292: INFO: Unable to read jessie_udp@dns-test-service.dns-2383 from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
... skipping 2 lines ...
Oct  1 08:59:46.740: INFO: Unable to read jessie_tcp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:46.888: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:47.027: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:47.164: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:47.435: INFO: Unable to read jessie_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:47.570: INFO: Unable to read jessie_tcp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:47.843: INFO: Lookups using dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c failed for: [wheezy_udp@dns-test-service.dns-2383.svc wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc wheezy_udp@PodARecord jessie_udp@dns-test-service jessie_udp@dns-test-service.dns-2383 jessie_tcp@dns-test-service.dns-2383 jessie_udp@dns-test-service.dns-2383.svc jessie_tcp@dns-test-service.dns-2383.svc jessie_udp@_http._tcp.dns-test-service.dns-2383.svc jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc jessie_udp@_http._tcp.test-service-2.dns-2383.svc jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:59:49.642: INFO: Unable to read wheezy_udp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:49.913: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:50.453: INFO: Unable to read wheezy_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:50.995: INFO: Unable to read jessie_udp@dns-test-service from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:51.271: INFO: Unable to read jessie_udp@dns-test-service.dns-2383 from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
... skipping 2 lines ...
Oct  1 08:59:51.678: INFO: Unable to read jessie_tcp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:51.813: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:51.948: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:52.083: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:52.354: INFO: Unable to read jessie_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:52.490: INFO: Unable to read jessie_tcp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:52.760: INFO: Lookups using dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c failed for: [wheezy_udp@dns-test-service.dns-2383.svc wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc wheezy_udp@PodARecord jessie_udp@dns-test-service jessie_udp@dns-test-service.dns-2383 jessie_tcp@dns-test-service.dns-2383 jessie_udp@dns-test-service.dns-2383.svc jessie_tcp@dns-test-service.dns-2383.svc jessie_udp@_http._tcp.dns-test-service.dns-2383.svc jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc jessie_udp@_http._tcp.test-service-2.dns-2383.svc jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:59:54.642: INFO: Unable to read wheezy_udp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:54.913: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:55.455: INFO: Unable to read wheezy_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:55.996: INFO: Unable to read jessie_udp@dns-test-service from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:56.266: INFO: Unable to read jessie_udp@dns-test-service.dns-2383 from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
... skipping 2 lines ...
Oct  1 08:59:56.672: INFO: Unable to read jessie_tcp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:56.809: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:56.945: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:57.080: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:57.350: INFO: Unable to read jessie_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:57.487: INFO: Unable to read jessie_tcp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:57.758: INFO: Lookups using dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c failed for: [wheezy_udp@dns-test-service.dns-2383.svc wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc wheezy_udp@PodARecord jessie_udp@dns-test-service jessie_udp@dns-test-service.dns-2383 jessie_tcp@dns-test-service.dns-2383 jessie_udp@dns-test-service.dns-2383.svc jessie_tcp@dns-test-service.dns-2383.svc jessie_udp@_http._tcp.dns-test-service.dns-2383.svc jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc jessie_udp@_http._tcp.test-service-2.dns-2383.svc jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:59:59.648: INFO: Unable to read wheezy_udp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 08:59:59.918: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:00.463: INFO: Unable to read wheezy_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:01.006: INFO: Unable to read jessie_udp@dns-test-service from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:01.276: INFO: Unable to read jessie_udp@dns-test-service.dns-2383 from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
... skipping 2 lines ...
Oct  1 09:00:01.681: INFO: Unable to read jessie_tcp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:01.817: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:01.952: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:02.090: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:02.363: INFO: Unable to read jessie_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:02.498: INFO: Unable to read jessie_tcp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:02.768: INFO: Lookups using dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c failed for: [wheezy_udp@dns-test-service.dns-2383.svc wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc wheezy_udp@PodARecord jessie_udp@dns-test-service jessie_udp@dns-test-service.dns-2383 jessie_tcp@dns-test-service.dns-2383 jessie_udp@dns-test-service.dns-2383.svc jessie_tcp@dns-test-service.dns-2383.svc jessie_udp@_http._tcp.dns-test-service.dns-2383.svc jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc jessie_udp@_http._tcp.test-service-2.dns-2383.svc jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 09:00:04.644: INFO: Unable to read wheezy_udp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:04.914: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:05.457: INFO: Unable to read wheezy_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:05.997: INFO: Unable to read jessie_udp@dns-test-service from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:06.268: INFO: Unable to read jessie_udp@dns-test-service.dns-2383 from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
... skipping 2 lines ...
Oct  1 09:00:06.675: INFO: Unable to read jessie_tcp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:06.810: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:06.946: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:07.081: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:07.361: INFO: Unable to read jessie_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:07.496: INFO: Unable to read jessie_tcp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:07.767: INFO: Lookups using dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c failed for: [wheezy_udp@dns-test-service.dns-2383.svc wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc wheezy_udp@PodARecord jessie_udp@dns-test-service jessie_udp@dns-test-service.dns-2383 jessie_tcp@dns-test-service.dns-2383 jessie_udp@dns-test-service.dns-2383.svc jessie_tcp@dns-test-service.dns-2383.svc jessie_udp@_http._tcp.dns-test-service.dns-2383.svc jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc jessie_udp@_http._tcp.test-service-2.dns-2383.svc jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 09:00:09.646: INFO: Unable to read wheezy_udp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:09.917: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:10.457: INFO: Unable to read wheezy_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:10.998: INFO: Unable to read jessie_udp@dns-test-service from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:11.270: INFO: Unable to read jessie_udp@dns-test-service.dns-2383 from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
... skipping 2 lines ...
Oct  1 09:00:11.675: INFO: Unable to read jessie_tcp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:11.810: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:11.945: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:12.080: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:12.353: INFO: Unable to read jessie_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:12.488: INFO: Unable to read jessie_tcp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:12.760: INFO: Lookups using dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c failed for: [wheezy_udp@dns-test-service.dns-2383.svc wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc wheezy_udp@PodARecord jessie_udp@dns-test-service jessie_udp@dns-test-service.dns-2383 jessie_tcp@dns-test-service.dns-2383 jessie_udp@dns-test-service.dns-2383.svc jessie_tcp@dns-test-service.dns-2383.svc jessie_udp@_http._tcp.dns-test-service.dns-2383.svc jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc jessie_udp@_http._tcp.test-service-2.dns-2383.svc jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 09:00:14.641: INFO: Unable to read wheezy_udp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:14.911: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:15.454: INFO: Unable to read wheezy_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:15.996: INFO: Unable to read jessie_udp@dns-test-service from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:16.269: INFO: Unable to read jessie_udp@dns-test-service.dns-2383 from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
... skipping 2 lines ...
Oct  1 09:00:16.732: INFO: Unable to read jessie_tcp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:16.869: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:17.004: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:17.141: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:17.412: INFO: Unable to read jessie_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:17.548: INFO: Unable to read jessie_tcp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:17.818: INFO: Lookups using dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c failed for: [wheezy_udp@dns-test-service.dns-2383.svc wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc wheezy_udp@PodARecord jessie_udp@dns-test-service jessie_udp@dns-test-service.dns-2383 jessie_tcp@dns-test-service.dns-2383 jessie_udp@dns-test-service.dns-2383.svc jessie_tcp@dns-test-service.dns-2383.svc jessie_udp@_http._tcp.dns-test-service.dns-2383.svc jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc jessie_udp@_http._tcp.test-service-2.dns-2383.svc jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 09:00:19.644: INFO: Unable to read wheezy_udp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:19.917: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:20.466: INFO: Unable to read wheezy_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:21.008: INFO: Unable to read jessie_udp@dns-test-service from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:21.279: INFO: Unable to read jessie_udp@dns-test-service.dns-2383 from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
... skipping 2 lines ...
Oct  1 09:00:21.686: INFO: Unable to read jessie_tcp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:21.823: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:21.958: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:22.095: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:22.365: INFO: Unable to read jessie_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:22.500: INFO: Unable to read jessie_tcp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:22.793: INFO: Lookups using dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c failed for: [wheezy_udp@dns-test-service.dns-2383.svc wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc wheezy_udp@PodARecord jessie_udp@dns-test-service jessie_udp@dns-test-service.dns-2383 jessie_tcp@dns-test-service.dns-2383 jessie_udp@dns-test-service.dns-2383.svc jessie_tcp@dns-test-service.dns-2383.svc jessie_udp@_http._tcp.dns-test-service.dns-2383.svc jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc jessie_udp@_http._tcp.test-service-2.dns-2383.svc jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 09:00:24.645: INFO: Unable to read wheezy_udp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:24.915: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:25.462: INFO: Unable to read wheezy_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:26.007: INFO: Unable to read jessie_udp@dns-test-service from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:26.278: INFO: Unable to read jessie_udp@dns-test-service.dns-2383 from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
... skipping 2 lines ...
Oct  1 09:00:26.685: INFO: Unable to read jessie_tcp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:26.821: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:26.956: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:27.091: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:27.361: INFO: Unable to read jessie_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:27.497: INFO: Unable to read jessie_tcp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:27.768: INFO: Lookups using dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c failed for: [wheezy_udp@dns-test-service.dns-2383.svc wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc wheezy_udp@PodARecord jessie_udp@dns-test-service jessie_udp@dns-test-service.dns-2383 jessie_tcp@dns-test-service.dns-2383 jessie_udp@dns-test-service.dns-2383.svc jessie_tcp@dns-test-service.dns-2383.svc jessie_udp@_http._tcp.dns-test-service.dns-2383.svc jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc jessie_udp@_http._tcp.test-service-2.dns-2383.svc jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 09:00:29.645: INFO: Unable to read wheezy_udp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:29.915: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:30.475: INFO: Unable to read wheezy_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:31.046: INFO: Unable to read jessie_udp@dns-test-service from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:31.318: INFO: Unable to read jessie_udp@dns-test-service.dns-2383 from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
... skipping 2 lines ...
Oct  1 09:00:31.727: INFO: Unable to read jessie_tcp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:31.862: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:31.998: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:32.134: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:32.406: INFO: Unable to read jessie_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:32.541: INFO: Unable to read jessie_tcp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:32.812: INFO: Lookups using dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c failed for: [wheezy_udp@dns-test-service.dns-2383.svc wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc wheezy_udp@PodARecord jessie_udp@dns-test-service jessie_udp@dns-test-service.dns-2383 jessie_tcp@dns-test-service.dns-2383 jessie_udp@dns-test-service.dns-2383.svc jessie_tcp@dns-test-service.dns-2383.svc jessie_udp@_http._tcp.dns-test-service.dns-2383.svc jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc jessie_udp@_http._tcp.test-service-2.dns-2383.svc jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 09:00:33.512: INFO: Unable to read wheezy_udp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:33.782: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:34.324: INFO: Unable to read wheezy_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:34.865: INFO: Unable to read jessie_udp@dns-test-service from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:35.136: INFO: Unable to read jessie_udp@dns-test-service.dns-2383 from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
... skipping 2 lines ...
Oct  1 09:00:35.548: INFO: Unable to read jessie_tcp@dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:35.683: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:35.820: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:35.955: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-2383.svc from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:36.225: INFO: Unable to read jessie_udp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:36.365: INFO: Unable to read jessie_tcp@PodARecord from pod dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c: the server could not find the requested resource (get pods dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c)
Oct  1 09:00:36.640: INFO: Lookups using dns-2383/dns-test-e5d39048-8e21-43c4-8622-72a8b54e3f2c failed for: [wheezy_udp@dns-test-service.dns-2383.svc wheezy_udp@_http._tcp.dns-test-service.dns-2383.svc wheezy_udp@PodARecord jessie_udp@dns-test-service jessie_udp@dns-test-service.dns-2383 jessie_tcp@dns-test-service.dns-2383 jessie_udp@dns-test-service.dns-2383.svc jessie_tcp@dns-test-service.dns-2383.svc jessie_udp@_http._tcp.dns-test-service.dns-2383.svc jessie_tcp@_http._tcp.dns-test-service.dns-2383.svc jessie_udp@_http._tcp.test-service-2.dns-2383.svc jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 09:00:36.641: FAIL: Unexpected error:
    <*errors.errorString | 0xc000202200>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred

... skipping 309 lines ...
• Failure [629.433 seconds]
[sig-network] DNS
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
  should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance] [It]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629

  Oct  1 09:00:36.641: Unexpected error:
      <*errors.errorString | 0xc000202200>: {
          s: "timed out waiting for the condition",
      }
      timed out waiting for the condition
  occurred

  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:464
------------------------------
{"msg":"FAILED [sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]","total":-1,"completed":10,"skipped":49,"failed":1,"failures":["[sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]"]}

SSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
... skipping 42 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 09:00:45.655: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "custom-resource-definition-5477" for this suite.

•
------------------------------
{"msg":"PASSED [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] Simple CustomResourceDefinition getting/updating/patching custom resource definition status sub-resource works  [Conformance]","total":-1,"completed":11,"skipped":54,"failed":1,"failures":["[sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]"]}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:00:45.940: INFO: Driver hostPath doesn't support DynamicPV -- skipping
... skipping 5 lines ...
[sig-storage] In-tree Volumes
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  [Driver: hostPath]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Dynamic PV (immediate binding)] topology
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should fail to schedule a pod which has topologies that conflict with AllowedTopologies [BeforeEach]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Driver hostPath doesn't support DynamicPV -- skipping

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:173
------------------------------
... skipping 75 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should be able to unmount after the subpath directory is deleted [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:441
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir] [Testpattern: Pre-provisioned PV (default fs)] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly]","total":-1,"completed":23,"skipped":125,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ext4)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:00:46.240: INFO: Only supported for providers [vsphere] (not aws)
... skipping 79 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:188
    Two pods mounting a local volume one after the other
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:250
      should be able to write from pod1 and read from pod2
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:251
------------------------------
{"msg":"PASSED [sig-storage] PersistentVolumes-local  [Volume type: dir-link-bindmounted] Two pods mounting a local volume one after the other should be able to write from pod1 and read from pod2","total":-1,"completed":21,"skipped":138,"failed":0}

SSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:00:47.074: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 121 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (ext4)] volumes
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should store data
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:151
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: block] [Testpattern: Pre-provisioned PV (ext4)] volumes should store data","total":-1,"completed":25,"skipped":152,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:00:48.270: INFO: Driver local doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (default fs)] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 112 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:188
    Two pods mounting a local volume at the same time
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:244
      should be able to write from pod1 and read from pod2
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:245
------------------------------
{"msg":"PASSED [sig-storage] PersistentVolumes-local  [Volume type: tmpfs] Two pods mounting a local volume at the same time should be able to write from pod1 and read from pod2","total":-1,"completed":33,"skipped":214,"failed":0}

SS
------------------------------
[BeforeEach] [k8s.io] [sig-node] Mount propagation
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 63 lines ...
Oct  1 09:00:20.006: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:20.884: INFO: Exec stderr: ""
Oct  1 09:00:23.291: INFO: ExecWithOptions {Command:[nsenter --mount=/rootfs/proc/1/ns/mnt -- sh -c mkdir "/var/lib/kubelet/mount-propagation-1576"/host; mount -t tmpfs e2e-mount-propagation-host "/var/lib/kubelet/mount-propagation-1576"/host; echo host > "/var/lib/kubelet/mount-propagation-1576"/host/file] Namespace:mount-propagation-1576 PodName:hostexec-ip-172-20-35-235.ap-northeast-1.compute.internal-shzgt ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:true Quiet:false}
Oct  1 09:00:23.291: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:24.299: INFO: ExecWithOptions {Command:[/bin/sh -c cat /mnt/test/master/file] Namespace:mount-propagation-1576 PodName:master ContainerName:cntr Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Oct  1 09:00:24.299: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:25.184: INFO: pod master mount master: stdout: "master", stderr: "" error: <nil>
Oct  1 09:00:25.321: INFO: ExecWithOptions {Command:[/bin/sh -c cat /mnt/test/slave/file] Namespace:mount-propagation-1576 PodName:master ContainerName:cntr Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Oct  1 09:00:25.321: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:26.204: INFO: pod master mount slave: stdout: "", stderr: "cat: can't open '/mnt/test/slave/file': No such file or directory" error: command terminated with exit code 1
Oct  1 09:00:26.338: INFO: ExecWithOptions {Command:[/bin/sh -c cat /mnt/test/private/file] Namespace:mount-propagation-1576 PodName:master ContainerName:cntr Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Oct  1 09:00:26.338: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:27.212: INFO: pod master mount private: stdout: "", stderr: "cat: can't open '/mnt/test/private/file': No such file or directory" error: command terminated with exit code 1
Oct  1 09:00:27.346: INFO: ExecWithOptions {Command:[/bin/sh -c cat /mnt/test/default/file] Namespace:mount-propagation-1576 PodName:master ContainerName:cntr Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Oct  1 09:00:27.346: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:28.204: INFO: pod master mount default: stdout: "", stderr: "cat: can't open '/mnt/test/default/file': No such file or directory" error: command terminated with exit code 1
Oct  1 09:00:28.338: INFO: ExecWithOptions {Command:[/bin/sh -c cat /mnt/test/host/file] Namespace:mount-propagation-1576 PodName:master ContainerName:cntr Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Oct  1 09:00:28.338: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:29.232: INFO: pod master mount host: stdout: "host", stderr: "" error: <nil>
Oct  1 09:00:29.366: INFO: ExecWithOptions {Command:[/bin/sh -c cat /mnt/test/master/file] Namespace:mount-propagation-1576 PodName:slave ContainerName:cntr Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Oct  1 09:00:29.366: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:30.238: INFO: pod slave mount master: stdout: "master", stderr: "" error: <nil>
Oct  1 09:00:30.372: INFO: ExecWithOptions {Command:[/bin/sh -c cat /mnt/test/slave/file] Namespace:mount-propagation-1576 PodName:slave ContainerName:cntr Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Oct  1 09:00:30.372: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:31.216: INFO: pod slave mount slave: stdout: "slave", stderr: "" error: <nil>
Oct  1 09:00:31.349: INFO: ExecWithOptions {Command:[/bin/sh -c cat /mnt/test/private/file] Namespace:mount-propagation-1576 PodName:slave ContainerName:cntr Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Oct  1 09:00:31.349: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:32.226: INFO: pod slave mount private: stdout: "", stderr: "cat: can't open '/mnt/test/private/file': No such file or directory" error: command terminated with exit code 1
Oct  1 09:00:32.360: INFO: ExecWithOptions {Command:[/bin/sh -c cat /mnt/test/default/file] Namespace:mount-propagation-1576 PodName:slave ContainerName:cntr Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Oct  1 09:00:32.360: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:33.244: INFO: pod slave mount default: stdout: "", stderr: "cat: can't open '/mnt/test/default/file': No such file or directory" error: command terminated with exit code 1
Oct  1 09:00:33.377: INFO: ExecWithOptions {Command:[/bin/sh -c cat /mnt/test/host/file] Namespace:mount-propagation-1576 PodName:slave ContainerName:cntr Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Oct  1 09:00:33.377: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:34.266: INFO: pod slave mount host: stdout: "host", stderr: "" error: <nil>
Oct  1 09:00:34.400: INFO: ExecWithOptions {Command:[/bin/sh -c cat /mnt/test/master/file] Namespace:mount-propagation-1576 PodName:private ContainerName:cntr Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Oct  1 09:00:34.400: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:35.284: INFO: pod private mount master: stdout: "", stderr: "cat: can't open '/mnt/test/master/file': No such file or directory" error: command terminated with exit code 1
Oct  1 09:00:35.418: INFO: ExecWithOptions {Command:[/bin/sh -c cat /mnt/test/slave/file] Namespace:mount-propagation-1576 PodName:private ContainerName:cntr Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Oct  1 09:00:35.418: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:36.292: INFO: pod private mount slave: stdout: "", stderr: "cat: can't open '/mnt/test/slave/file': No such file or directory" error: command terminated with exit code 1
Oct  1 09:00:36.427: INFO: ExecWithOptions {Command:[/bin/sh -c cat /mnt/test/private/file] Namespace:mount-propagation-1576 PodName:private ContainerName:cntr Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Oct  1 09:00:36.427: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:37.516: INFO: pod private mount private: stdout: "private", stderr: "" error: <nil>
Oct  1 09:00:37.649: INFO: ExecWithOptions {Command:[/bin/sh -c cat /mnt/test/default/file] Namespace:mount-propagation-1576 PodName:private ContainerName:cntr Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Oct  1 09:00:37.649: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:38.524: INFO: pod private mount default: stdout: "", stderr: "cat: can't open '/mnt/test/default/file': No such file or directory" error: command terminated with exit code 1
Oct  1 09:00:38.658: INFO: ExecWithOptions {Command:[/bin/sh -c cat /mnt/test/host/file] Namespace:mount-propagation-1576 PodName:private ContainerName:cntr Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Oct  1 09:00:38.658: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:39.533: INFO: pod private mount host: stdout: "", stderr: "cat: can't open '/mnt/test/host/file': No such file or directory" error: command terminated with exit code 1
Oct  1 09:00:39.667: INFO: ExecWithOptions {Command:[/bin/sh -c cat /mnt/test/master/file] Namespace:mount-propagation-1576 PodName:default ContainerName:cntr Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Oct  1 09:00:39.667: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:40.638: INFO: pod default mount master: stdout: "", stderr: "cat: can't open '/mnt/test/master/file': No such file or directory" error: command terminated with exit code 1
Oct  1 09:00:40.772: INFO: ExecWithOptions {Command:[/bin/sh -c cat /mnt/test/slave/file] Namespace:mount-propagation-1576 PodName:default ContainerName:cntr Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Oct  1 09:00:40.772: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:41.661: INFO: pod default mount slave: stdout: "", stderr: "cat: can't open '/mnt/test/slave/file': No such file or directory" error: command terminated with exit code 1
Oct  1 09:00:41.795: INFO: ExecWithOptions {Command:[/bin/sh -c cat /mnt/test/private/file] Namespace:mount-propagation-1576 PodName:default ContainerName:cntr Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Oct  1 09:00:41.795: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:42.666: INFO: pod default mount private: stdout: "", stderr: "cat: can't open '/mnt/test/private/file': No such file or directory" error: command terminated with exit code 1
Oct  1 09:00:42.800: INFO: ExecWithOptions {Command:[/bin/sh -c cat /mnt/test/default/file] Namespace:mount-propagation-1576 PodName:default ContainerName:cntr Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Oct  1 09:00:42.800: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:43.721: INFO: pod default mount default: stdout: "default", stderr: "" error: <nil>
Oct  1 09:00:43.855: INFO: ExecWithOptions {Command:[/bin/sh -c cat /mnt/test/host/file] Namespace:mount-propagation-1576 PodName:default ContainerName:cntr Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Oct  1 09:00:43.855: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:44.720: INFO: pod default mount host: stdout: "", stderr: "cat: can't open '/mnt/test/host/file': No such file or directory" error: command terminated with exit code 1
Oct  1 09:00:44.720: INFO: ExecWithOptions {Command:[nsenter --mount=/rootfs/proc/1/ns/mnt -- sh -c test `cat "/var/lib/kubelet/mount-propagation-1576"/master/file` = master] Namespace:mount-propagation-1576 PodName:hostexec-ip-172-20-35-235.ap-northeast-1.compute.internal-shzgt ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:true Quiet:false}
Oct  1 09:00:44.720: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:45.575: INFO: ExecWithOptions {Command:[nsenter --mount=/rootfs/proc/1/ns/mnt -- sh -c test ! -e "/var/lib/kubelet/mount-propagation-1576"/slave/file] Namespace:mount-propagation-1576 PodName:hostexec-ip-172-20-35-235.ap-northeast-1.compute.internal-shzgt ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:true Quiet:false}
Oct  1 09:00:45.575: INFO: >>> kubeConfig: /root/.kube/config
Oct  1 09:00:46.451: INFO: ExecWithOptions {Command:[nsenter --mount=/rootfs/proc/1/ns/mnt -- sh -c umount "/var/lib/kubelet/mount-propagation-1576"/host] Namespace:mount-propagation-1576 PodName:hostexec-ip-172-20-35-235.ap-northeast-1.compute.internal-shzgt ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:true Quiet:false}
Oct  1 09:00:46.451: INFO: >>> kubeConfig: /root/.kube/config
... skipping 21 lines ...
• [SLOW TEST:65.193 seconds]
[k8s.io] [sig-node] Mount propagation
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  should propagate mounts to the host
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/node/mount_propagation.go:82
------------------------------
{"msg":"PASSED [k8s.io] [sig-node] Mount propagation should propagate mounts to the host","total":-1,"completed":29,"skipped":223,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:00:52.736: INFO: Only supported for providers [gce gke] (not aws)
[AfterEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 85 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23
  [k8s.io] Basic StatefulSet functionality [StatefulSetBasic]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
    should perform rolling updates and roll backs of template modifications [Conformance]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-apps] StatefulSet [k8s.io] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications [Conformance]","total":-1,"completed":29,"skipped":276,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:00:54.506: INFO: Driver local doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 187 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] volumes
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should store data
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:151
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir-bindmounted] [Testpattern: Pre-provisioned PV (default fs)] volumes should store data","total":-1,"completed":31,"skipped":273,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:00.097: INFO: Driver hostPathSymlink doesn't support DynamicPV -- skipping
... skipping 104 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:151

      Driver local doesn't support InlineVolume -- skipping

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:173
------------------------------
{"msg":"PASSED [sig-storage] Downward API volume should provide podname as non-root with fsgroup and defaultMode [LinuxOnly] [NodeFeature:FSGroup]","total":-1,"completed":32,"skipped":198,"failed":0}
[BeforeEach] [Testpattern: Inline-volume (default fs)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
[BeforeEach] [Testpattern: Inline-volume (default fs)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 09:00:19.254: INFO: >>> kubeConfig: /root/.kube/config
... skipping 73 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Inline-volume (default fs)] volumes
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should store data
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:151
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: hostPath] [Testpattern: Inline-volume (default fs)] volumes should store data","total":-1,"completed":33,"skipped":198,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ext3)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:01.680: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 32 lines ...
Oct  1 09:00:03.424: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1866-aws-sc2b2qq
STEP: creating a claim
Oct  1 09:00:03.557: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-tnnt
STEP: Creating a pod to test subpath
Oct  1 09:00:03.959: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-tnnt" in namespace "provisioning-1866" to be "Succeeded or Failed"
Oct  1 09:00:04.092: INFO: Pod "pod-subpath-test-dynamicpv-tnnt": Phase="Pending", Reason="", readiness=false. Elapsed: 132.899562ms
Oct  1 09:00:06.225: INFO: Pod "pod-subpath-test-dynamicpv-tnnt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.265971296s
Oct  1 09:00:08.360: INFO: Pod "pod-subpath-test-dynamicpv-tnnt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.400529997s
Oct  1 09:00:10.493: INFO: Pod "pod-subpath-test-dynamicpv-tnnt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.533339072s
Oct  1 09:00:12.628: INFO: Pod "pod-subpath-test-dynamicpv-tnnt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.669033614s
Oct  1 09:00:14.761: INFO: Pod "pod-subpath-test-dynamicpv-tnnt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.802094505s
... skipping 2 lines ...
Oct  1 09:00:21.161: INFO: Pod "pod-subpath-test-dynamicpv-tnnt": Phase="Pending", Reason="", readiness=false. Elapsed: 17.201272252s
Oct  1 09:00:23.296: INFO: Pod "pod-subpath-test-dynamicpv-tnnt": Phase="Pending", Reason="", readiness=false. Elapsed: 19.336232096s
Oct  1 09:00:25.429: INFO: Pod "pod-subpath-test-dynamicpv-tnnt": Phase="Pending", Reason="", readiness=false. Elapsed: 21.469242724s
Oct  1 09:00:27.562: INFO: Pod "pod-subpath-test-dynamicpv-tnnt": Phase="Pending", Reason="", readiness=false. Elapsed: 23.602625265s
Oct  1 09:00:29.695: INFO: Pod "pod-subpath-test-dynamicpv-tnnt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.735753792s
STEP: Saw pod success
Oct  1 09:00:29.695: INFO: Pod "pod-subpath-test-dynamicpv-tnnt" satisfied condition "Succeeded or Failed"
Oct  1 09:00:29.828: INFO: Trying to get logs from node ip-172-20-35-235.ap-northeast-1.compute.internal pod pod-subpath-test-dynamicpv-tnnt container test-container-volume-dynamicpv-tnnt: <nil>
STEP: delete the pod
Oct  1 09:00:30.103: INFO: Waiting for pod pod-subpath-test-dynamicpv-tnnt to disappear
Oct  1 09:00:30.235: INFO: Pod pod-subpath-test-dynamicpv-tnnt no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-tnnt
Oct  1 09:00:30.236: INFO: Deleting pod "pod-subpath-test-dynamicpv-tnnt" in namespace "provisioning-1866"
... skipping 23 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Dynamic PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support non-existent path
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:191
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: aws] [Testpattern: Dynamic PV (default fs)] subPath should support non-existent path","total":-1,"completed":32,"skipped":264,"failed":0}
[BeforeEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:02.245: INFO: Driver local doesn't support ext4 -- skipping
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 48 lines ...
Oct  1 09:00:54.560: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
[It] should support readOnly file specified in the volumeMount [LinuxOnly]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:376
Oct  1 09:00:55.237: INFO: In-tree plugin kubernetes.io/host-path is not migrated, not validating any metrics
Oct  1 09:00:55.512: INFO: Waiting up to 5m0s for pod "hostpath-symlink-prep-provisioning-5545" in namespace "provisioning-5545" to be "Succeeded or Failed"
Oct  1 09:00:55.647: INFO: Pod "hostpath-symlink-prep-provisioning-5545": Phase="Pending", Reason="", readiness=false. Elapsed: 135.229347ms
Oct  1 09:00:57.782: INFO: Pod "hostpath-symlink-prep-provisioning-5545": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.270645475s
STEP: Saw pod success
Oct  1 09:00:57.782: INFO: Pod "hostpath-symlink-prep-provisioning-5545" satisfied condition "Succeeded or Failed"
Oct  1 09:00:57.782: INFO: Deleting pod "hostpath-symlink-prep-provisioning-5545" in namespace "provisioning-5545"
Oct  1 09:00:57.924: INFO: Wait up to 5m0s for pod "hostpath-symlink-prep-provisioning-5545" to be fully deleted
Oct  1 09:00:58.060: INFO: Creating resource for inline volume
STEP: Creating pod pod-subpath-test-inlinevolume-w528
STEP: Creating a pod to test subpath
Oct  1 09:00:58.197: INFO: Waiting up to 5m0s for pod "pod-subpath-test-inlinevolume-w528" in namespace "provisioning-5545" to be "Succeeded or Failed"
Oct  1 09:00:58.333: INFO: Pod "pod-subpath-test-inlinevolume-w528": Phase="Pending", Reason="", readiness=false. Elapsed: 135.399315ms
Oct  1 09:01:00.468: INFO: Pod "pod-subpath-test-inlinevolume-w528": Phase="Pending", Reason="", readiness=false. Elapsed: 2.271037406s
Oct  1 09:01:02.604: INFO: Pod "pod-subpath-test-inlinevolume-w528": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.406954457s
STEP: Saw pod success
Oct  1 09:01:02.604: INFO: Pod "pod-subpath-test-inlinevolume-w528" satisfied condition "Succeeded or Failed"
Oct  1 09:01:02.740: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod pod-subpath-test-inlinevolume-w528 container test-container-subpath-inlinevolume-w528: <nil>
STEP: delete the pod
Oct  1 09:01:03.018: INFO: Waiting for pod pod-subpath-test-inlinevolume-w528 to disappear
Oct  1 09:01:03.153: INFO: Pod pod-subpath-test-inlinevolume-w528 no longer exists
STEP: Deleting pod pod-subpath-test-inlinevolume-w528
Oct  1 09:01:03.153: INFO: Deleting pod "pod-subpath-test-inlinevolume-w528" in namespace "provisioning-5545"
STEP: Deleting pod
Oct  1 09:01:03.288: INFO: Deleting pod "pod-subpath-test-inlinevolume-w528" in namespace "provisioning-5545"
Oct  1 09:01:03.560: INFO: Waiting up to 5m0s for pod "hostpath-symlink-prep-provisioning-5545" in namespace "provisioning-5545" to be "Succeeded or Failed"
Oct  1 09:01:03.696: INFO: Pod "hostpath-symlink-prep-provisioning-5545": Phase="Pending", Reason="", readiness=false. Elapsed: 135.50042ms
Oct  1 09:01:05.832: INFO: Pod "hostpath-symlink-prep-provisioning-5545": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.27149888s
STEP: Saw pod success
Oct  1 09:01:05.832: INFO: Pod "hostpath-symlink-prep-provisioning-5545" satisfied condition "Succeeded or Failed"
Oct  1 09:01:05.832: INFO: Deleting pod "hostpath-symlink-prep-provisioning-5545" in namespace "provisioning-5545"
Oct  1 09:01:05.972: INFO: Wait up to 5m0s for pod "hostpath-symlink-prep-provisioning-5545" to be fully deleted
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 09:01:06.107: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "provisioning-5545" for this suite.
... skipping 6 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Inline-volume (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support readOnly file specified in the volumeMount [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:376
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: hostPathSymlink] [Testpattern: Inline-volume (default fs)] subPath should support readOnly file specified in the volumeMount [LinuxOnly]","total":-1,"completed":30,"skipped":284,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext3)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:06.406: INFO: Only supported for node OS distro [gci ubuntu custom] (not debian)
... skipping 37 lines ...
• [SLOW TEST:8.349 seconds]
[sig-api-machinery] ResourceQuota
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
  should create a ResourceQuota and ensure its status is promptly calculated. [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-api-machinery] ResourceQuota should create a ResourceQuota and ensure its status is promptly calculated. [Conformance]","total":-1,"completed":34,"skipped":203,"failed":0}
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:10.061: INFO: Driver supports dynamic provisioning, skipping InlineVolume pattern
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 11 lines ...
      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:833
------------------------------
SSSS
------------------------------
{"msg":"PASSED [sig-auth] Certificates API [Privileged:ClusterAdmin] should support CSR API operations [Conformance]","total":-1,"completed":16,"skipped":139,"failed":0}
[BeforeEach] [sig-network] DNS
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 08:50:52.584: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename dns
STEP: Waiting for a default service account to be provisioned in namespace
... skipping 17 lines ...
Oct  1 08:51:00.909: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:01.048: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:01.183: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:01.319: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:01.455: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:01.591: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:01.591: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:51:06.728: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:06.867: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:07.004: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:07.147: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:07.282: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:07.419: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:07.556: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:07.692: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:07.828: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:07.964: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:08.100: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:08.236: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:08.236: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:51:11.727: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:11.863: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:12.000: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:12.136: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:12.273: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:12.409: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:12.549: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:12.686: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:12.822: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:12.958: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:13.094: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:13.230: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:13.230: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:51:16.727: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:16.863: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:16.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:17.135: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:17.271: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:17.407: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:17.549: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:17.688: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:17.824: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:17.960: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:18.095: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:18.237: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:18.237: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:51:21.727: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:22.004: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:22.141: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:22.276: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:22.412: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:22.553: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:22.689: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:22.825: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:22.961: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:23.097: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:23.233: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:23.233: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:51:26.728: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:26.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:27.137: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:27.281: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:27.419: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:27.555: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:27.691: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:27.829: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:27.965: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:28.100: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:28.236: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:28.236: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:51:31.727: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:32.001: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:32.137: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:32.273: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:32.411: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:32.551: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:32.688: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:32.824: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:32.960: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:33.096: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:33.232: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:33.232: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:51:36.731: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:37.002: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:37.138: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:37.275: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:37.412: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:37.548: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:37.684: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:37.819: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:37.955: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:38.092: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:38.228: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:38.228: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:51:41.727: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:41.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:42.135: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:42.271: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:42.407: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:42.543: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:42.679: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:42.814: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:43.086: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:43.223: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:43.223: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:51:46.733: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:47.005: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:47.279: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:47.414: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:47.554: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:47.690: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:47.826: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:48.098: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:48.234: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:48.234: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:51:51.728: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:51.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:52.271: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:52.408: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:52.544: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:52.681: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:52.817: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:53.089: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:53.225: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:53.226: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:51:56.727: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:56.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:57.275: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:57.420: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:57.557: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:57.693: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:57.830: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:58.102: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:58.238: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:51:58.238: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:52:01.727: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:01.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:02.283: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:02.419: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:02.555: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:02.691: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:02.827: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:03.100: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:03.236: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:03.236: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:52:06.730: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:07.002: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:07.275: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:07.411: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:07.547: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:07.683: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:07.820: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:08.092: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:08.228: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:52:11.727: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:11.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:12.270: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:12.406: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:12.542: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:12.678: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:12.813: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:13.086: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:13.222: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:52:16.727: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:16.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:17.271: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:17.407: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:17.545: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:17.682: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:17.818: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:18.089: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:18.225: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:52:22.000: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:22.272: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:22.543: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:22.826: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:23.099: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:23.236: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:52:27.000: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:27.271: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:27.543: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:27.816: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:28.088: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:28.224: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:52:32.001: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:32.274: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:32.546: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:32.818: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:33.108: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:33.245: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:52:37.000: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:37.272: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:37.546: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:37.818: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:38.089: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:38.225: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:52:41.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:42.273: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:42.544: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:42.816: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:43.087: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:43.227: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:52:46.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:47.273: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:47.552: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:47.824: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:48.096: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:48.232: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:52:51.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:52.272: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:52.544: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:52.831: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:53.129: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:53.265: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:52:57.008: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:57.287: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:57.559: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:57.832: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:58.105: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:52:58.241: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:53:02.018: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:02.290: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:02.576: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:02.857: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:03.145: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:03.288: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:53:06.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:07.271: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:07.543: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:07.818: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:08.090: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:08.230: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:53:12.007: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:12.279: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:12.550: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:12.823: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:13.095: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:13.231: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:53:17.002: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:17.274: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:17.545: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:17.822: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:18.093: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:18.229: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:53:21.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:22.271: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:22.543: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:22.814: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:23.087: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:23.223: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:53:26.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:27.277: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:27.549: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:27.821: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:28.093: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:28.247: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:53:32.000: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:32.271: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:32.543: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:32.814: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:33.086: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:33.222: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:53:37.005: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:37.277: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:37.552: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:37.827: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:38.100: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:38.236: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:53:41.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:42.271: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:42.543: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:42.816: INFO: Unable to read jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:43.089: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:43.225: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:53:47.000: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:47.272: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:47.543: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:48.093: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:48.229: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:53:52.000: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:52.273: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:52.545: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:53.091: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:53.227: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:53:57.002: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:57.273: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:57.552: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:58.103: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:53:58.244: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:54:02.000: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:02.278: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:02.550: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:03.116: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:03.257: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:54:07.004: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:07.295: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:07.567: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:08.113: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:08.249: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:54:12.002: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:12.273: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:12.546: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:13.090: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:13.226: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:54:16.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:17.281: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:17.558: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:18.103: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:18.239: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:54:22.003: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:22.275: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:22.547: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:23.093: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:23.230: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:54:27.001: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:27.273: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:27.545: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:28.089: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:28.225: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:54:31.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:32.272: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:32.546: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:33.090: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:33.226: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-5567.svc.cluster.local jessie_udp@PodARecord]

Oct  1 08:54:37.000: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:37.272: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:38.101: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:38.237: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:54:41.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:42.271: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:43.118: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:43.254: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:54:47.000: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:47.272: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:48.090: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:48.226: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:54:52.000: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:52.273: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:53.088: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:53.224: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:54:57.013: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:57.286: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:58.109: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:54:58.247: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:55:02.006: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:02.279: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:03.116: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:03.253: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:55:07.002: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:07.273: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:08.093: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:08.229: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:55:12.005: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:12.277: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:13.102: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:13.238: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:55:17.005: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:17.277: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:18.094: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:18.230: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:55:21.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:22.271: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:23.086: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:23.221: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:55:27.002: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:27.276: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:28.125: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:28.263: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:55:32.001: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:32.272: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:33.089: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:33.225: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:55:37.006: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:37.278: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:38.105: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:38.240: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:55:41.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:42.270: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:43.095: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:43.231: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:55:46.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:47.272: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:48.098: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:48.234: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:55:51.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:52.271: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:53.087: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:53.223: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:55:57.000: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:57.278: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:58.095: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:55:58.231: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:56:02.000: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:02.272: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:03.088: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:03.223: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:56:07.004: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:07.275: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:08.091: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:08.227: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:56:11.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:12.271: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:13.087: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:13.225: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:56:17.000: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:17.273: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:18.089: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:18.225: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:56:21.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:22.270: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:23.087: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:23.223: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:56:27.009: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:27.283: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:28.110: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:28.246: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:56:31.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:32.273: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:33.096: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:33.233: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:56:37.002: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:37.275: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:38.170: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:38.306: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:56:41.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:42.272: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:43.086: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:43.222: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:56:47.012: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:47.283: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:48.100: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:48.236: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:56:52.049: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:52.321: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:53.143: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:53.285: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:56:57.001: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:57.272: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:58.091: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:56:58.227: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:57:02.111: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:02.391: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:03.223: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:03.365: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:57:06.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:07.271: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:08.087: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:08.223: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:57:11.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:12.271: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:13.093: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:13.243: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:57:16.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:17.271: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:18.094: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:18.230: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:57:21.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:22.271: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:23.130: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:23.267: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:57:27.009: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:27.280: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:28.113: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:28.249: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:57:32.000: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:32.272: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:33.088: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:33.225: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:57:36.999: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:37.271: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:38.099: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:38.250: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@dns-test-service-2.dns-5567.svc.cluster.local wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:57:42.275: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:43.092: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:43.228: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:57:47.272: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:48.089: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:48.226: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:57:52.271: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:53.087: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:53.223: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:57:57.271: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:58.088: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:57:58.224: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:58:02.277: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:03.093: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:03.229: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:58:07.273: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:08.093: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:08.229: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:58:12.289: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:13.110: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:13.246: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:58:17.310: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:18.247: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:18.384: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:58:22.283: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:23.108: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:23.244: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:58:27.287: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:28.116: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:28.254: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:58:32.275: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:33.091: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:33.227: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:58:37.273: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:38.093: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:38.230: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:58:42.278: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:43.105: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:43.253: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:58:47.284: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:48.109: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:48.245: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:58:52.277: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:53.193: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:53.330: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:58:57.274: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:58.097: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:58:58.233: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:59:02.284: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:03.109: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:03.245: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:59:07.280: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:08.106: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:08.241: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:59:12.279: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:13.100: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:13.235: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:59:17.294: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:18.287: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:18.433: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:59:22.282: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:23.099: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:23.235: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:59:27.274: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:28.096: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:28.232: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:59:32.271: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:33.093: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:33.233: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:59:37.273: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:38.093: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:38.229: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:59:42.272: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:43.088: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:43.224: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:59:47.301: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:48.119: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:48.254: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:59:52.274: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:53.091: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:53.227: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 08:59:57.271: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:58.101: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 08:59:58.238: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 09:00:02.275: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:03.093: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:03.229: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 09:00:07.279: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:08.099: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:08.235: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 09:00:12.272: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:13.088: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:13.224: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 09:00:17.278: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:18.094: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:18.230: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 09:00:22.274: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:23.090: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:23.227: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 09:00:27.272: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:28.089: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:28.225: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 09:00:32.286: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:33.116: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:33.252: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 09:00:37.272: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:38.090: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:38.226: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 09:00:42.272: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:43.089: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:43.233: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 09:00:47.273: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:48.098: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:48.234: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 09:00:52.295: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:53.112: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:53.248: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 09:00:57.272: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:58.095: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:00:58.235: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 09:01:02.274: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:01:03.116: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:01:03.252: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 09:01:03.936: INFO: Unable to read wheezy_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:01:04.753: INFO: Unable to read jessie_udp@PodARecord from pod dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6: the server could not find the requested resource (get pods dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6)
Oct  1 09:01:04.889: INFO: Lookups using dns-5567/dns-test-6fe3e07e-ea75-4093-9743-803f381e4af6 failed for: [wheezy_udp@PodARecord jessie_udp@PodARecord]

Oct  1 09:01:04.890: FAIL: Unexpected error:
    <*errors.errorString | 0xc000202200>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred

... skipping 298 lines ...
• Failure [618.736 seconds]
[sig-network] DNS
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
  should provide DNS for pods for Subdomain [Conformance] [It]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629

  Oct  1 09:01:04.890: Unexpected error:
      <*errors.errorString | 0xc000202200>: {
          s: "timed out waiting for the condition",
      }
      timed out waiting for the condition
  occurred

  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:464
------------------------------
{"msg":"FAILED [sig-network] DNS should provide DNS for pods for Subdomain [Conformance]","total":-1,"completed":16,"skipped":139,"failed":1,"failures":["[sig-network] DNS should provide DNS for pods for Subdomain [Conformance]"]}

S
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:11.346: INFO: Only supported for node OS distro [gci ubuntu custom] (not debian)
... skipping 65 lines ...
Oct  1 09:00:59.271: INFO: PersistentVolumeClaim pvc-4j895 found but phase is Pending instead of Bound.
Oct  1 09:01:01.404: INFO: PersistentVolumeClaim pvc-4j895 found and phase=Bound (10.802501817s)
Oct  1 09:01:01.404: INFO: Waiting up to 3m0s for PersistentVolume local-l2p96 to have phase Bound
Oct  1 09:01:01.538: INFO: PersistentVolume local-l2p96 found and phase=Bound (133.430351ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-br2c
STEP: Creating a pod to test subpath
Oct  1 09:01:01.942: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-br2c" in namespace "provisioning-7190" to be "Succeeded or Failed"
Oct  1 09:01:02.077: INFO: Pod "pod-subpath-test-preprovisionedpv-br2c": Phase="Pending", Reason="", readiness=false. Elapsed: 135.579546ms
Oct  1 09:01:04.211: INFO: Pod "pod-subpath-test-preprovisionedpv-br2c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.269355949s
Oct  1 09:01:06.345: INFO: Pod "pod-subpath-test-preprovisionedpv-br2c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.40350324s
STEP: Saw pod success
Oct  1 09:01:06.345: INFO: Pod "pod-subpath-test-preprovisionedpv-br2c" satisfied condition "Succeeded or Failed"
Oct  1 09:01:06.479: INFO: Trying to get logs from node ip-172-20-60-245.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-br2c container test-container-subpath-preprovisionedpv-br2c: <nil>
STEP: delete the pod
Oct  1 09:01:06.762: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-br2c to disappear
Oct  1 09:01:06.896: INFO: Pod pod-subpath-test-preprovisionedpv-br2c no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-br2c
Oct  1 09:01:06.896: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-br2c" in namespace "provisioning-7190"
STEP: Creating pod pod-subpath-test-preprovisionedpv-br2c
STEP: Creating a pod to test subpath
Oct  1 09:01:07.164: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-br2c" in namespace "provisioning-7190" to be "Succeeded or Failed"
Oct  1 09:01:07.298: INFO: Pod "pod-subpath-test-preprovisionedpv-br2c": Phase="Pending", Reason="", readiness=false. Elapsed: 134.223164ms
Oct  1 09:01:09.432: INFO: Pod "pod-subpath-test-preprovisionedpv-br2c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.268448332s
STEP: Saw pod success
Oct  1 09:01:09.433: INFO: Pod "pod-subpath-test-preprovisionedpv-br2c" satisfied condition "Succeeded or Failed"
Oct  1 09:01:09.566: INFO: Trying to get logs from node ip-172-20-60-245.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-br2c container test-container-subpath-preprovisionedpv-br2c: <nil>
STEP: delete the pod
Oct  1 09:01:09.841: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-br2c to disappear
Oct  1 09:01:09.974: INFO: Pod pod-subpath-test-preprovisionedpv-br2c no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-br2c
Oct  1 09:01:09.974: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-br2c" in namespace "provisioning-7190"
... skipping 19 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support existing directories when readOnly specified in the volumeSource
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:391
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir-link-bindmounted] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing directories when readOnly specified in the volumeSource","total":-1,"completed":24,"skipped":128,"failed":0}

SSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:11.941: INFO: Only supported for providers [azure] (not aws)
... skipping 168 lines ...
• [SLOW TEST:6.702 seconds]
[sig-storage] Projected downwardAPI
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_downwardapi.go:35
  should update labels on modification [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-storage] Projected downwardAPI should update labels on modification [NodeConformance] [Conformance]","total":-1,"completed":31,"skipped":291,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:13.137: INFO: Driver local doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 114 lines ...
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [sig-storage] Downward API volume
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/downwardapi_volume.go:41
[It] should provide container's cpu request [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating a pod to test downward API volume plugin
Oct  1 09:01:10.896: INFO: Waiting up to 5m0s for pod "downwardapi-volume-501c9e0e-c8a6-4009-ad78-b84622788a61" in namespace "downward-api-4884" to be "Succeeded or Failed"
Oct  1 09:01:11.031: INFO: Pod "downwardapi-volume-501c9e0e-c8a6-4009-ad78-b84622788a61": Phase="Pending", Reason="", readiness=false. Elapsed: 134.859477ms
Oct  1 09:01:13.166: INFO: Pod "downwardapi-volume-501c9e0e-c8a6-4009-ad78-b84622788a61": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.269494574s
STEP: Saw pod success
Oct  1 09:01:13.166: INFO: Pod "downwardapi-volume-501c9e0e-c8a6-4009-ad78-b84622788a61" satisfied condition "Succeeded or Failed"
Oct  1 09:01:13.300: INFO: Trying to get logs from node ip-172-20-35-235.ap-northeast-1.compute.internal pod downwardapi-volume-501c9e0e-c8a6-4009-ad78-b84622788a61 container client-container: <nil>
STEP: delete the pod
Oct  1 09:01:13.577: INFO: Waiting for pod downwardapi-volume-501c9e0e-c8a6-4009-ad78-b84622788a61 to disappear
Oct  1 09:01:13.712: INFO: Pod downwardapi-volume-501c9e0e-c8a6-4009-ad78-b84622788a61 no longer exists
[AfterEach] [sig-storage] Downward API volume
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 09:01:13.712: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "downward-api-4884" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] Downward API volume should provide container's cpu request [NodeConformance] [Conformance]","total":-1,"completed":35,"skipped":208,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:13.991: INFO: Driver emptydir doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 83 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should resize volume when PVC is edited while pod is using it
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:241
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: aws] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand should resize volume when PVC is edited while pod is using it","total":-1,"completed":20,"skipped":149,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][sig-windows] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:16.529: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 21 lines ...
Oct  1 09:01:14.037: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename emptydir
STEP: Waiting for a default service account to be provisioned in namespace
[It] should support (non-root,0666,default) [LinuxOnly] [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating a pod to test emptydir 0666 on node default medium
Oct  1 09:01:14.846: INFO: Waiting up to 5m0s for pod "pod-898a0114-bc7c-4de6-a005-0bce0e351a1d" in namespace "emptydir-9748" to be "Succeeded or Failed"
Oct  1 09:01:14.980: INFO: Pod "pod-898a0114-bc7c-4de6-a005-0bce0e351a1d": Phase="Pending", Reason="", readiness=false. Elapsed: 134.45095ms
Oct  1 09:01:17.115: INFO: Pod "pod-898a0114-bc7c-4de6-a005-0bce0e351a1d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.268852224s
STEP: Saw pod success
Oct  1 09:01:17.115: INFO: Pod "pod-898a0114-bc7c-4de6-a005-0bce0e351a1d" satisfied condition "Succeeded or Failed"
Oct  1 09:01:17.249: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod pod-898a0114-bc7c-4de6-a005-0bce0e351a1d container test-container: <nil>
STEP: delete the pod
Oct  1 09:01:17.524: INFO: Waiting for pod pod-898a0114-bc7c-4de6-a005-0bce0e351a1d to disappear
Oct  1 09:01:17.658: INFO: Pod pod-898a0114-bc7c-4de6-a005-0bce0e351a1d no longer exists
[AfterEach] [sig-storage] EmptyDir volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 09:01:17.658: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "emptydir-9748" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] EmptyDir volumes should support (non-root,0666,default) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":36,"skipped":217,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ext3)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:17.949: INFO: Only supported for providers [gce gke] (not aws)
... skipping 41 lines ...
Oct  1 09:01:15.379: INFO: ForEach: Found 1 pods from the filter.  Now looping through them.
Oct  1 09:01:15.379: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-9725 describe pod agnhost-primary-5w77b'
Oct  1 09:01:16.134: INFO: stderr: ""
Oct  1 09:01:16.134: INFO: stdout: "Name:         agnhost-primary-5w77b\nNamespace:    kubectl-9725\nPriority:     0\nNode:         ip-172-20-37-175.ap-northeast-1.compute.internal/172.20.37.175\nStart Time:   Fri, 01 Oct 2021 09:01:13 +0000\nLabels:       app=agnhost\n              role=primary\nAnnotations:  <none>\nStatus:       Running\nIP:           100.96.1.17\nIPs:\n  IP:           100.96.1.17\nControlled By:  ReplicationController/agnhost-primary\nContainers:\n  agnhost-primary:\n    Container ID:   containerd://098a274c07fea6e569f5592466a4a06b14f3aff34917bb718913a83c2a2cc565\n    Image:          k8s.gcr.io/e2e-test-images/agnhost:2.21\n    Image ID:       k8s.gcr.io/e2e-test-images/agnhost@sha256:ab055cd3d45f50b90732c14593a5bf50f210871bb4f91994c756fc22db6d922a\n    Port:           6379/TCP\n    Host Port:      0/TCP\n    State:          Running\n      Started:      Fri, 01 Oct 2021 09:01:14 +0000\n    Ready:          True\n    Restart Count:  0\n    Environment:    <none>\n    Mounts:\n      /var/run/secrets/kubernetes.io/serviceaccount from default-token-d795k (ro)\nConditions:\n  Type              Status\n  Initialized       True \n  Ready             True \n  ContainersReady   True \n  PodScheduled      True \nVolumes:\n  default-token-d795k:\n    Type:        Secret (a volume populated by a Secret)\n    SecretName:  default-token-d795k\n    Optional:    false\nQoS Class:       BestEffort\nNode-Selectors:  <none>\nTolerations:     node.kubernetes.io/not-ready:NoExecute op=Exists for 300s\n                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s\nEvents:\n  Type    Reason     Age   From               Message\n  ----    ------     ----  ----               -------\n  Normal  Scheduled  3s    default-scheduler  Successfully assigned kubectl-9725/agnhost-primary-5w77b to ip-172-20-37-175.ap-northeast-1.compute.internal\n  Normal  Pulled     2s    kubelet            Container image \"k8s.gcr.io/e2e-test-images/agnhost:2.21\" already present on machine\n  Normal  Created    2s    kubelet            Created container agnhost-primary\n  Normal  Started    2s    kubelet            Started container agnhost-primary\n"
Oct  1 09:01:16.134: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-9725 describe rc agnhost-primary'
Oct  1 09:01:17.025: INFO: stderr: ""
Oct  1 09:01:17.025: INFO: stdout: "Name:         agnhost-primary\nNamespace:    kubectl-9725\nSelector:     app=agnhost,role=primary\nLabels:       app=agnhost\n              role=primary\nAnnotations:  <none>\nReplicas:     1 current / 1 desired\nPods Status:  1 Running / 0 Waiting / 0 Succeeded / 0 Failed\nPod Template:\n  Labels:  app=agnhost\n           role=primary\n  Containers:\n   agnhost-primary:\n    Image:        k8s.gcr.io/e2e-test-images/agnhost:2.21\n    Port:         6379/TCP\n    Host Port:    0/TCP\n    Environment:  <none>\n    Mounts:       <none>\n  Volumes:        <none>\nEvents:\n  Type    Reason            Age   From                    Message\n  ----    ------            ----  ----                    -------\n  Normal  SuccessfulCreate  4s    replication-controller  Created pod: agnhost-primary-5w77b\n"
Oct  1 09:01:17.025: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-9725 describe service agnhost-primary'
Oct  1 09:01:17.923: INFO: stderr: ""
Oct  1 09:01:17.923: INFO: stdout: "Name:              agnhost-primary\nNamespace:         kubectl-9725\nLabels:            app=agnhost\n                   role=primary\nAnnotations:       <none>\nSelector:          app=agnhost,role=primary\nType:              ClusterIP\nIP Families:       <none>\nIP:                100.68.250.29\nIPs:               100.68.250.29\nPort:              <unset>  6379/TCP\nTargetPort:        agnhost-server/TCP\nEndpoints:         100.96.1.17:6379\nSession Affinity:  None\nEvents:            <none>\n"
Oct  1 09:01:18.059: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-9725 describe node ip-172-20-33-232.ap-northeast-1.compute.internal'
Oct  1 09:01:19.523: INFO: stderr: ""
Oct  1 09:01:19.523: INFO: stdout: "Name:               ip-172-20-33-232.ap-northeast-1.compute.internal\nRoles:              control-plane,master\nLabels:             beta.kubernetes.io/arch=amd64\n                    beta.kubernetes.io/instance-type=c5.large\n                    beta.kubernetes.io/os=linux\n                    failure-domain.beta.kubernetes.io/region=ap-northeast-1\n                    failure-domain.beta.kubernetes.io/zone=ap-northeast-1a\n                    kops.k8s.io/instancegroup=master-ap-northeast-1a\n                    kops.k8s.io/kops-controller-pki=\n                    kubernetes.io/arch=amd64\n                    kubernetes.io/hostname=ip-172-20-33-232.ap-northeast-1.compute.internal\n                    kubernetes.io/os=linux\n                    kubernetes.io/role=master\n                    node-role.kubernetes.io/control-plane=\n                    node-role.kubernetes.io/master=\n                    node.kubernetes.io/exclude-from-external-load-balancers=\n                    node.kubernetes.io/instance-type=c5.large\n                    topology.kubernetes.io/region=ap-northeast-1\n                    topology.kubernetes.io/zone=ap-northeast-1a\nAnnotations:        flannel.alpha.coreos.com/backend-data: {\"VtepMAC\":\"1a:ae:fe:57:c9:c7\"}\n                    flannel.alpha.coreos.com/backend-type: vxlan\n                    flannel.alpha.coreos.com/kube-subnet-manager: true\n                    flannel.alpha.coreos.com/public-ip: 172.20.33.232\n                    node.alpha.kubernetes.io/ttl: 0\n                    volumes.kubernetes.io/controller-managed-attach-detach: true\nCreationTimestamp:  Fri, 01 Oct 2021 08:41:20 +0000\nTaints:             node-role.kubernetes.io/master:NoSchedule\nUnschedulable:      false\nLease:\n  HolderIdentity:  ip-172-20-33-232.ap-northeast-1.compute.internal\n  AcquireTime:     <unset>\n  RenewTime:       Fri, 01 Oct 2021 09:01:15 +0000\nConditions:\n  Type                 Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message\n  ----                 ------  -----------------                 ------------------                ------                       -------\n  NetworkUnavailable   False   Fri, 01 Oct 2021 08:42:07 +0000   Fri, 01 Oct 2021 08:42:07 +0000   FlannelIsUp                  Flannel is running on this node\n  MemoryPressure       False   Fri, 01 Oct 2021 08:57:21 +0000   Fri, 01 Oct 2021 08:41:20 +0000   KubeletHasSufficientMemory   kubelet has sufficient memory available\n  DiskPressure         False   Fri, 01 Oct 2021 08:57:21 +0000   Fri, 01 Oct 2021 08:41:20 +0000   KubeletHasNoDiskPressure     kubelet has no disk pressure\n  PIDPressure          False   Fri, 01 Oct 2021 08:57:21 +0000   Fri, 01 Oct 2021 08:41:20 +0000   KubeletHasSufficientPID      kubelet has sufficient PID available\n  Ready                True    Fri, 01 Oct 2021 08:57:21 +0000   Fri, 01 Oct 2021 08:42:10 +0000   KubeletReady                 kubelet is posting ready status\nAddresses:\n  InternalIP:   172.20.33.232\n  ExternalIP:   54.249.188.168\n  Hostname:     ip-172-20-33-232.ap-northeast-1.compute.internal\n  InternalDNS:  ip-172-20-33-232.ap-northeast-1.compute.internal\n  ExternalDNS:  ec2-54-249-188-168.ap-northeast-1.compute.amazonaws.com\nCapacity:\n  attachable-volumes-aws-ebs:  25\n  cpu:                         2\n  ephemeral-storage:           50319340Ki\n  hugepages-1Gi:               0\n  hugepages-2Mi:               0\n  memory:                      3772716Ki\n  pods:                        110\nAllocatable:\n  attachable-volumes-aws-ebs:  25\n  cpu:                         2\n  ephemeral-storage:           46374303668\n  hugepages-1Gi:               0\n  hugepages-2Mi:               0\n  memory:                      3670316Ki\n  pods:                        110\nSystem Info:\n  Machine ID:                 ec214dee1f497e5a0c3f972da49e4684\n  System UUID:                ec27fbae-ad72-ac81-8c41-4051d40f624e\n  Boot ID:                    3ac7203e-4c67-44e0-8a0d-4d25ff869535\n  Kernel Version:             5.10.50-44.132.amzn2.x86_64\n  OS Image:                   Amazon Linux 2\n  Operating System:           linux\n  Architecture:               amd64\n  Container Runtime Version:  containerd://1.4.9\n  Kubelet Version:            v1.20.11\n  Kube-Proxy Version:         v1.20.11\nPodCIDR:                      100.96.0.0/24\nPodCIDRs:                     100.96.0.0/24\nProviderID:                   aws:///ap-northeast-1a/i-0a282cbc3f2251289\nNon-terminated Pods:          (9 in total)\n  Namespace                   Name                                                                        CPU Requests  CPU Limits  Memory Requests  Memory Limits  AGE\n  ---------                   ----                                                                        ------------  ----------  ---------------  -------------  ---\n  kube-system                 dns-controller-5779cbc678-s4p4p                                             50m (2%)      0 (0%)      50Mi (1%)        0 (0%)         19m\n  kube-system                 etcd-manager-events-ip-172-20-33-232.ap-northeast-1.compute.internal        100m (5%)     0 (0%)      100Mi (2%)       0 (0%)         19m\n  kube-system                 etcd-manager-main-ip-172-20-33-232.ap-northeast-1.compute.internal          200m (10%)    0 (0%)      100Mi (2%)       0 (0%)         19m\n  kube-system                 kops-controller-vdxm4                                                       50m (2%)      0 (0%)      50Mi (1%)        0 (0%)         19m\n  kube-system                 kube-apiserver-ip-172-20-33-232.ap-northeast-1.compute.internal             150m (7%)     0 (0%)      0 (0%)           0 (0%)         18m\n  kube-system                 kube-controller-manager-ip-172-20-33-232.ap-northeast-1.compute.internal    100m (5%)     0 (0%)      0 (0%)           0 (0%)         18m\n  kube-system                 kube-flannel-ds-ghksb                                                       100m (5%)     0 (0%)      100Mi (2%)       100Mi (2%)     19m\n  kube-system                 kube-proxy-ip-172-20-33-232.ap-northeast-1.compute.internal                 100m (5%)     0 (0%)      0 (0%)           0 (0%)         19m\n  kube-system                 kube-scheduler-ip-172-20-33-232.ap-northeast-1.compute.internal             100m (5%)     0 (0%)      0 (0%)           0 (0%)         19m\nAllocated resources:\n  (Total limits may be over 100 percent, i.e., overcommitted.)\n  Resource                    Requests     Limits\n  --------                    --------     ------\n  cpu                         950m (47%)   0 (0%)\n  memory                      400Mi (11%)  100Mi (2%)\n  ephemeral-storage           0 (0%)       0 (0%)\n  hugepages-1Gi               0 (0%)       0 (0%)\n  hugepages-2Mi               0 (0%)       0 (0%)\n  attachable-volumes-aws-ebs  0            0\nEvents:\n  Type    Reason                   Age                From        Message\n  ----    ------                   ----               ----        -------\n  Normal  NodeHasSufficientMemory  20m (x8 over 20m)  kubelet     Node ip-172-20-33-232.ap-northeast-1.compute.internal status is now: NodeHasSufficientMemory\n  Normal  NodeHasNoDiskPressure    20m (x7 over 20m)  kubelet     Node ip-172-20-33-232.ap-northeast-1.compute.internal status is now: NodeHasNoDiskPressure\n  Normal  NodeHasSufficientPID     20m (x7 over 20m)  kubelet     Node ip-172-20-33-232.ap-northeast-1.compute.internal status is now: NodeHasSufficientPID\n  Normal  Starting                 19m                kube-proxy  Starting kube-proxy.\n"
... skipping 11 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/framework.go:23
  Kubectl describe
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:1090
    should check if kubectl describe prints relevant information for rc and pods  [Conformance]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-cli] Kubectl client Kubectl describe should check if kubectl describe prints relevant information for rc and pods  [Conformance]","total":-1,"completed":17,"skipped":144,"failed":1,"failures":["[sig-network] DNS should provide DNS for pods for Subdomain [Conformance]"]}

S
------------------------------
[BeforeEach] [sig-cli] Kubectl client
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 69 lines ...
Oct  1 09:00:56.813: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:00:56.947: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:00:57.890: INFO: Unable to read jessie_udp@dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:00:58.024: INFO: Unable to read jessie_tcp@dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:00:58.162: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:00:58.297: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:00:59.105: INFO: Lookups using dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96 failed for: [wheezy_udp@dns-test-service.dns-1818.svc.cluster.local wheezy_tcp@dns-test-service.dns-1818.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local jessie_udp@dns-test-service.dns-1818.svc.cluster.local jessie_tcp@dns-test-service.dns-1818.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local]

Oct  1 09:01:04.240: INFO: Unable to read wheezy_udp@dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:04.374: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:04.508: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:04.642: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:05.585: INFO: Unable to read jessie_udp@dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:05.719: INFO: Unable to read jessie_tcp@dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:05.856: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:05.989: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:06.794: INFO: Lookups using dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96 failed for: [wheezy_udp@dns-test-service.dns-1818.svc.cluster.local wheezy_tcp@dns-test-service.dns-1818.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local jessie_udp@dns-test-service.dns-1818.svc.cluster.local jessie_tcp@dns-test-service.dns-1818.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local]

Oct  1 09:01:09.239: INFO: Unable to read wheezy_udp@dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:09.373: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:09.508: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:09.645: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:10.585: INFO: Unable to read jessie_udp@dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:10.719: INFO: Unable to read jessie_tcp@dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:10.853: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:10.987: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:11.798: INFO: Lookups using dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96 failed for: [wheezy_udp@dns-test-service.dns-1818.svc.cluster.local wheezy_tcp@dns-test-service.dns-1818.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local jessie_udp@dns-test-service.dns-1818.svc.cluster.local jessie_tcp@dns-test-service.dns-1818.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local]

Oct  1 09:01:14.240: INFO: Unable to read wheezy_udp@dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:14.374: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:14.508: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:14.643: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:15.582: INFO: Unable to read jessie_udp@dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:15.716: INFO: Unable to read jessie_tcp@dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:15.850: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:15.985: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:16.793: INFO: Lookups using dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96 failed for: [wheezy_udp@dns-test-service.dns-1818.svc.cluster.local wheezy_tcp@dns-test-service.dns-1818.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local jessie_udp@dns-test-service.dns-1818.svc.cluster.local jessie_tcp@dns-test-service.dns-1818.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local]

Oct  1 09:01:19.240: INFO: Unable to read wheezy_udp@dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:19.374: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:19.508: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:19.642: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:20.580: INFO: Unable to read jessie_udp@dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:20.714: INFO: Unable to read jessie_tcp@dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:20.848: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:20.984: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local from pod dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96: the server could not find the requested resource (get pods dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96)
Oct  1 09:01:21.801: INFO: Lookups using dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96 failed for: [wheezy_udp@dns-test-service.dns-1818.svc.cluster.local wheezy_tcp@dns-test-service.dns-1818.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local jessie_udp@dns-test-service.dns-1818.svc.cluster.local jessie_tcp@dns-test-service.dns-1818.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-1818.svc.cluster.local]

Oct  1 09:01:26.802: INFO: DNS probes using dns-1818/dns-test-e8b8a225-6c92-4e3f-9ee5-4234d1d2db96 succeeded

STEP: deleting the pod
STEP: deleting the test service
STEP: deleting the test headless service
... skipping 6 lines ...
• [SLOW TEST:36.586 seconds]
[sig-network] DNS
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
  should provide DNS for services  [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-network] DNS should provide DNS for services  [Conformance]","total":-1,"completed":34,"skipped":216,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:27.521: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
... skipping 62 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  When pod refers to non-existent ephemeral storage
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/ephemeral_volume.go:53
    should allow deletion of pod with invalid volume : projected
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/ephemeral_volume.go:55
------------------------------
{"msg":"PASSED [sig-storage] Ephemeralstorage When pod refers to non-existent ephemeral storage should allow deletion of pod with invalid volume : projected","total":-1,"completed":30,"skipped":226,"failed":0}

SSSS
------------------------------
[BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 29 lines ...
• [SLOW TEST:10.477 seconds]
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
  should be able to deny attaching pod [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny attaching pod [Conformance]","total":-1,"completed":18,"skipped":145,"failed":1,"failures":["[sig-network] DNS should provide DNS for pods for Subdomain [Conformance]"]}
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:31.173: INFO: Driver local doesn't support InlineVolume -- skipping
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 22 lines ...
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [sig-storage] Projected downwardAPI
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_downwardapi.go:41
[It] should set DefaultMode on files [LinuxOnly] [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating a pod to test downward API volume plugin
Oct  1 09:01:29.067: INFO: Waiting up to 5m0s for pod "downwardapi-volume-3e802e81-6bde-4508-9fcc-1d4a30334611" in namespace "projected-1582" to be "Succeeded or Failed"
Oct  1 09:01:29.201: INFO: Pod "downwardapi-volume-3e802e81-6bde-4508-9fcc-1d4a30334611": Phase="Pending", Reason="", readiness=false. Elapsed: 133.493856ms
Oct  1 09:01:31.337: INFO: Pod "downwardapi-volume-3e802e81-6bde-4508-9fcc-1d4a30334611": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.269279629s
STEP: Saw pod success
Oct  1 09:01:31.337: INFO: Pod "downwardapi-volume-3e802e81-6bde-4508-9fcc-1d4a30334611" satisfied condition "Succeeded or Failed"
Oct  1 09:01:31.470: INFO: Trying to get logs from node ip-172-20-35-235.ap-northeast-1.compute.internal pod downwardapi-volume-3e802e81-6bde-4508-9fcc-1d4a30334611 container client-container: <nil>
STEP: delete the pod
Oct  1 09:01:31.744: INFO: Waiting for pod downwardapi-volume-3e802e81-6bde-4508-9fcc-1d4a30334611 to disappear
Oct  1 09:01:31.877: INFO: Pod downwardapi-volume-3e802e81-6bde-4508-9fcc-1d4a30334611 no longer exists
[AfterEach] [sig-storage] Projected downwardAPI
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 09:01:31.877: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "projected-1582" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] Projected downwardAPI should set DefaultMode on files [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":31,"skipped":230,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:32.158: INFO: Driver hostPath doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 39 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 09:01:32.258: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "dns-1551" for this suite.

•
------------------------------
{"msg":"PASSED [sig-network] DNS should provide DNS for pods for Hostname [LinuxOnly] [Conformance]","total":-1,"completed":35,"skipped":221,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:32.545: INFO: Only supported for providers [gce gke] (not aws)
... skipping 148 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_volumes.go:39
    [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      Verify if offline PVC expansion works
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:169
------------------------------
{"msg":"PASSED [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand Verify if offline PVC expansion works","total":-1,"completed":27,"skipped":187,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:34.811: INFO: Only supported for providers [azure] (not aws)
... skipping 99 lines ...
Oct  1 09:00:50.184: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-6582 exec verify-service-up-exec-pod-lt6x9 -- /bin/sh -x -c for i in $(seq 1 150); do wget -q -T 1 -O - http://100.64.111.137:80 2>&1 || true; echo; done'
Oct  1 09:01:32.954: INFO: stderr: "+ seq 1 150\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n+ wget -q -T 1 -O - http://100.64.111.137:80\n+ echo\n"
Oct  1 09:01:32.955: INFO: stdout: "up-down-1-zc2tx\nup-down-1-zc2tx\nup-down-1-kg8t6\nwget: download timed out\n\nup-down-1-zc2tx\nup-down-1-kg8t6\nup-down-1-zc2tx\nup-down-1-kg8t6\nwget: download timed out\n\nup-down-1-zc2tx\nwget: download timed out\n\nup-down-1-kg8t6\nup-down-1-kg8t6\nup-down-1-kg8t6\nup-down-1-kg8t6\nwget: download timed out\n\nup-down-1-zc2tx\nup-down-1-zc2tx\nup-down-1-kg8t6\nup-down-1-kg8t6\nwget: download timed out\n\nup-down-1-zc2tx\nup-down-1-zc2tx\nup-down-1-zc2tx\nup-down-1-kg8t6\nwget: download timed out\n\nup-down-1-zc2tx\nup-down-1-zc2tx\nup-down-1-zc2tx\nwget: download timed out\n\nwget: download timed out\n\nwget: download timed out\n\nwget: download timed out\n\nup-down-1-kg8t6\nup-down-1-kg8t6\nwget: download timed out\n\nup-down-1-zc2tx\nup-down-1-zc2tx\nup-down-1-kg8t6\nwget: download timed out\n\nwget: download timed out\n\nup-down-1-zc2tx\nup-down-1-kg8t6\nwget: download timed out\n\nwget: download timed out\n\nup-down-1-kg8t6\nup-down-1-kg8t6\nup-down-1-kg8t6\nwget: download timed out\n\nwget: download timed out\n\nup-down-1-kg8t6\nup-down-1-zc2tx\nwget: download timed out\n\nup-down-1-kg8t6\nwget: download timed out\n\nup-down-1-kg8t6\nup-down-1-kg8t6\nup-down-1-kg8t6\nwget: download timed out\n\nup-down-1-zc2tx\nwget: download timed out\n\nup-down-1-kg8t6\nup-down-1-zc2tx\nwget: download timed out\n\nup-down-1-zc2tx\nup-down-1-zc2tx\nup-down-1-zc2tx\nup-down-1-kg8t6\nup-down-1-zc2tx\nwget: download timed out\n\nup-down-1-zc2tx\nwget: download timed out\n\nup-down-1-zc2tx\nup-down-1-zc2tx\nwget: download timed out\n\nup-down-1-kg8t6\nwget: download timed out\n\nwget: download timed out\n\nup-down-1-zc2tx\nup-down-1-zc2tx\nup-down-1-kg8t6\nup-down-1-zc2tx\nup-down-1-zc2tx\nwget: download timed out\n\nup-down-1-zc2tx\nup-down-1-zc2tx\nup-down-1-zc2tx\nwget: download timed out\n\nup-down-1-kg8t6\nup-down-1-kg8t6\nup-down-1-zc2tx\nup-down-1-kg8t6\nup-down-1-zc2tx\nwget: download timed out\n\nup-down-1-kg8t6\nup-down-1-zc2tx\nup-down-1-zc2tx\nwget: download timed out\n\nup-down-1-kg8t6\nup-down-1-zc2tx\nup-down-1-kg8t6\nup-down-1-zc2tx\nup-down-1-zc2tx\nup-down-1-zc2tx\nup-down-1-zc2tx\nup-down-1-zc2tx\nup-down-1-zc2tx\nwget: download timed out\n\nup-down-1-zc2tx\nup-down-1-zc2tx\nup-down-1-kg8t6\nwget: download timed out\n\nup-down-1-kg8t6\nup-down-1-zc2tx\nwget: download timed out\n\nwget: download timed out\n\nup-down-1-zc2tx\nup-down-1-zc2tx\nwget: download timed out\n\nwget: download timed out\n\nup-down-1-zc2tx\nup-down-1-kg8t6\nup-down-1-zc2tx\nwget: download timed out\n\nup-down-1-zc2tx\nup-down-1-kg8t6\nup-down-1-zc2tx\nup-down-1-kg8t6\nup-down-1-zc2tx\nup-down-1-zc2tx\nwget: download timed out\n\nup-down-1-zc2tx\nup-down-1-zc2tx\nup-down-1-kg8t6\nup-down-1-zc2tx\nwget: download timed out\n\nup-down-1-kg8t6\nup-down-1-zc2tx\nup-down-1-kg8t6\nup-down-1-zc2tx\nwget: download timed out\n\nup-down-1-zc2tx\nup-down-1-zc2tx\nup-down-1-kg8t6\nup-down-1-zc2tx\nup-down-1-kg8t6\nup-down-1-zc2tx\nup-down-1-zc2tx\nup-down-1-kg8t6\nup-down-1-zc2tx\n"
Oct  1 09:01:32.955: INFO: Unable to reach the following endpoints of service 100.64.111.137: map[up-down-1-2nc8g:{}]
STEP: Deleting pod verify-service-up-host-exec-pod in namespace services-6582
STEP: Deleting pod verify-service-up-exec-pod-lt6x9 in namespace services-6582
Oct  1 09:01:38.231: FAIL: Unexpected error:
    <*errors.errorString | 0xc00304a1a0>: {
        s: "service verification failed for: 100.64.111.137\nexpected [up-down-1-2nc8g up-down-1-kg8t6 up-down-1-zc2tx]\nreceived [up-down-1-kg8t6 up-down-1-zc2tx wget: download timed out]",
    }
    service verification failed for: 100.64.111.137
    expected [up-down-1-2nc8g up-down-1-kg8t6 up-down-1-zc2tx]
    received [up-down-1-kg8t6 up-down-1-zc2tx wget: download timed out]
occurred

Full Stack Trace
k8s.io/kubernetes/test/e2e/network.glob..func24.8()
... skipping 309 lines ...
• Failure [360.253 seconds]
[sig-network] Services
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
  should be able to up and down services [It]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:1025

  Oct  1 09:01:38.232: Unexpected error:
      <*errors.errorString | 0xc00304a1a0>: {
          s: "service verification failed for: 100.64.111.137\nexpected [up-down-1-2nc8g up-down-1-kg8t6 up-down-1-zc2tx]\nreceived [up-down-1-kg8t6 up-down-1-zc2tx wget: download timed out]",
      }
      service verification failed for: 100.64.111.137
      expected [up-down-1-2nc8g up-down-1-kg8t6 up-down-1-zc2tx]
      received [up-down-1-kg8t6 up-down-1-zc2tx wget: download timed out]
  occurred

  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:1041
------------------------------
{"msg":"FAILED [sig-network] Services should be able to up and down services","total":-1,"completed":15,"skipped":124,"failed":1,"failures":["[sig-network] Services should be able to up and down services"]}

SS
------------------------------
[BeforeEach] [sig-apps] CronJob
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 24 lines ...
• [SLOW TEST:59.594 seconds]
[sig-apps] CronJob
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23
  should remove from active list jobs that have been deleted
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/cronjob.go:223
------------------------------
{"msg":"PASSED [sig-apps] CronJob should remove from active list jobs that have been deleted","total":-1,"completed":12,"skipped":60,"failed":1,"failures":["[sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]"]}

SSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:45.590: INFO: Only supported for providers [gce gke] (not aws)
... skipping 114 lines ...
Oct  1 09:00:50.759: INFO: Waiting up to 5m0s for PersistentVolumeClaims [pvc-qw7xr] to have phase Bound
Oct  1 09:00:50.892: INFO: PersistentVolumeClaim pvc-qw7xr found and phase=Bound (132.740176ms)
STEP: Deleting the previously created pod
Oct  1 09:01:09.561: INFO: Deleting pod "pvc-volume-tester-2cr7g" in namespace "csi-mock-volumes-1057"
Oct  1 09:01:09.695: INFO: Wait up to 5m0s for pod "pvc-volume-tester-2cr7g" to be fully deleted
STEP: Checking CSI driver logs
Oct  1 09:01:22.110: INFO: Found NodeUnpublishVolume: {json: {"Method":"/csi.v1.Node/NodeUnpublishVolume","Request":{"volume_id":"4","target_path":"/var/lib/kubelet/pods/db6a4884-b80d-4aea-a238-a84ae623a945/volumes/kubernetes.io~csi/pvc-d619e10b-2be8-4782-a369-cbf8e418d172/mount"},"Response":{},"Error":"","FullError":null} Method:NodeUnpublishVolume Request:{VolumeContext:map[]} FullError:{Code:OK Message:} Error:}
STEP: Deleting pod pvc-volume-tester-2cr7g
Oct  1 09:01:22.110: INFO: Deleting pod "pvc-volume-tester-2cr7g" in namespace "csi-mock-volumes-1057"
STEP: Deleting claim pvc-qw7xr
Oct  1 09:01:22.510: INFO: Waiting up to 2m0s for PersistentVolume pvc-d619e10b-2be8-4782-a369-cbf8e418d172 to get deleted
Oct  1 09:01:22.645: INFO: PersistentVolume pvc-d619e10b-2be8-4782-a369-cbf8e418d172 was removed
STEP: Deleting storageclass csi-mock-volumes-1057-sc
... skipping 44 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  CSI workload information using mock driver
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_mock_volume.go:437
    should not be passed when podInfoOnMount=false
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_mock_volume.go:487
------------------------------
{"msg":"PASSED [sig-storage] CSI mock volume CSI workload information using mock driver should not be passed when podInfoOnMount=false","total":-1,"completed":37,"skipped":218,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:45.907: INFO: Driver supports dynamic provisioning, skipping InlineVolume pattern
... skipping 173 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 09:01:47.432: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "proxy-527" for this suite.

•
------------------------------
{"msg":"PASSED [sig-network] Proxy version v1 should proxy logs on node using proxy subresource ","total":-1,"completed":16,"skipped":126,"failed":1,"failures":["[sig-network] Services should be able to up and down services"]}

SSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ext4)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:47.732: INFO: Driver local doesn't support InlineVolume -- skipping
... skipping 69 lines ...
Oct  1 09:01:30.326: INFO: PersistentVolumeClaim pvc-7pxws found and phase=Bound (12.949303641s)
Oct  1 09:01:30.326: INFO: Waiting up to 3m0s for PersistentVolume nfs-8c9rx to have phase Bound
Oct  1 09:01:30.461: INFO: PersistentVolume nfs-8c9rx found and phase=Bound (134.94621ms)
STEP: Checking pod has write access to PersistentVolume
Oct  1 09:01:30.734: INFO: Creating nfs test pod
Oct  1 09:01:30.870: INFO: Pod should terminate with exitcode 0 (success)
Oct  1 09:01:30.871: INFO: Waiting up to 5m0s for pod "pvc-tester-g6lk2" in namespace "pv-2509" to be "Succeeded or Failed"
Oct  1 09:01:31.006: INFO: Pod "pvc-tester-g6lk2": Phase="Pending", Reason="", readiness=false. Elapsed: 135.360447ms
Oct  1 09:01:33.181: INFO: Pod "pvc-tester-g6lk2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.310078594s
Oct  1 09:01:35.316: INFO: Pod "pvc-tester-g6lk2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.445675533s
STEP: Saw pod success
Oct  1 09:01:35.316: INFO: Pod "pvc-tester-g6lk2" satisfied condition "Succeeded or Failed"
Oct  1 09:01:35.316: INFO: Pod pvc-tester-g6lk2 succeeded 
Oct  1 09:01:35.316: INFO: Deleting pod "pvc-tester-g6lk2" in namespace "pv-2509"
Oct  1 09:01:35.456: INFO: Wait up to 5m0s for pod "pvc-tester-g6lk2" to be fully deleted
STEP: Deleting the PVC to invoke the reclaim policy.
Oct  1 09:01:35.592: INFO: Deleting PVC pvc-7pxws to trigger reclamation of PV 
Oct  1 09:01:35.592: INFO: Deleting PersistentVolumeClaim "pvc-7pxws"
... skipping 83 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should be able to unmount after the subpath directory is deleted [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:441
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir-link] [Testpattern: Pre-provisioned PV (default fs)] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly]","total":-1,"completed":25,"skipped":150,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (ext4)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:49.762: INFO: Only supported for providers [openstack] (not aws)
[AfterEach] [Testpattern: Dynamic PV (ext4)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 70 lines ...
Oct  1 09:00:53.294: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Oct  1 09:00:53.433: INFO: Waiting up to 5m0s for PersistentVolumeClaims [csi-hostpathz6sbd] to have phase Bound
Oct  1 09:00:53.569: INFO: PersistentVolumeClaim csi-hostpathz6sbd found but phase is Pending instead of Bound.
Oct  1 09:00:55.705: INFO: PersistentVolumeClaim csi-hostpathz6sbd found and phase=Bound (2.272533926s)
STEP: Expanding non-expandable pvc
Oct  1 09:00:55.976: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct  1 09:00:56.248: INFO: Error updating pvc csi-hostpathz6sbd: persistentvolumeclaims "csi-hostpathz6sbd" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Oct  1 09:00:58.520: INFO: Error updating pvc csi-hostpathz6sbd: persistentvolumeclaims "csi-hostpathz6sbd" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Oct  1 09:01:00.520: INFO: Error updating pvc csi-hostpathz6sbd: persistentvolumeclaims "csi-hostpathz6sbd" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Oct  1 09:01:02.526: INFO: Error updating pvc csi-hostpathz6sbd: persistentvolumeclaims "csi-hostpathz6sbd" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Oct  1 09:01:04.520: INFO: Error updating pvc csi-hostpathz6sbd: persistentvolumeclaims "csi-hostpathz6sbd" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Oct  1 09:01:06.520: INFO: Error updating pvc csi-hostpathz6sbd: persistentvolumeclaims "csi-hostpathz6sbd" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Oct  1 09:01:08.520: INFO: Error updating pvc csi-hostpathz6sbd: persistentvolumeclaims "csi-hostpathz6sbd" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Oct  1 09:01:10.520: INFO: Error updating pvc csi-hostpathz6sbd: persistentvolumeclaims "csi-hostpathz6sbd" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Oct  1 09:01:12.521: INFO: Error updating pvc csi-hostpathz6sbd: persistentvolumeclaims "csi-hostpathz6sbd" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Oct  1 09:01:14.526: INFO: Error updating pvc csi-hostpathz6sbd: persistentvolumeclaims "csi-hostpathz6sbd" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Oct  1 09:01:16.524: INFO: Error updating pvc csi-hostpathz6sbd: persistentvolumeclaims "csi-hostpathz6sbd" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Oct  1 09:01:18.520: INFO: Error updating pvc csi-hostpathz6sbd: persistentvolumeclaims "csi-hostpathz6sbd" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Oct  1 09:01:20.520: INFO: Error updating pvc csi-hostpathz6sbd: persistentvolumeclaims "csi-hostpathz6sbd" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Oct  1 09:01:22.520: INFO: Error updating pvc csi-hostpathz6sbd: persistentvolumeclaims "csi-hostpathz6sbd" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Oct  1 09:01:24.521: INFO: Error updating pvc csi-hostpathz6sbd: persistentvolumeclaims "csi-hostpathz6sbd" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Oct  1 09:01:26.521: INFO: Error updating pvc csi-hostpathz6sbd: persistentvolumeclaims "csi-hostpathz6sbd" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Oct  1 09:01:26.793: INFO: Error updating pvc csi-hostpathz6sbd: persistentvolumeclaims "csi-hostpathz6sbd" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
STEP: Deleting pvc
Oct  1 09:01:26.794: INFO: Deleting PersistentVolumeClaim "csi-hostpathz6sbd"
Oct  1 09:01:26.931: INFO: Waiting up to 5m0s for PersistentVolume pvc-bc9c20a2-7026-4971-bcd7-1dd86ddc1f05 to get deleted
Oct  1 09:01:27.067: INFO: PersistentVolume pvc-bc9c20a2-7026-4971-bcd7-1dd86ddc1f05 was removed
STEP: Deleting sc
STEP: deleting the test namespace: volume-expand-4872
... skipping 46 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_volumes.go:39
    [Testpattern: Dynamic PV (default fs)] volume-expand
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should not allow expansion of pvcs without AllowVolumeExpansion property
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:154
------------------------------
{"msg":"PASSED [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] volume-expand should not allow expansion of pvcs without AllowVolumeExpansion property","total":-1,"completed":22,"skipped":156,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:50.402: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 61 lines ...
• [SLOW TEST:114.647 seconds]
[k8s.io] Probing container
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  should be restarted startup probe fails
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/container_probe.go:309
------------------------------
{"msg":"PASSED [k8s.io] Probing container should be restarted startup probe fails","total":-1,"completed":26,"skipped":234,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:53.887: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 102 lines ...
      Driver hostPathSymlink doesn't support DynamicPV -- skipping

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:173
------------------------------
SSSSS
------------------------------
{"msg":"PASSED [sig-cli] Kubectl client Kubectl copy should copy a file from a running Pod","total":-1,"completed":21,"skipped":153,"failed":0}
[BeforeEach] [sig-network] Networking
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 09:01:23.622: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename nettest
STEP: Waiting for a default service account to be provisioned in namespace
... skipping 85 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 09:01:53.923: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "replication-controller-859" for this suite.

•
------------------------------
{"msg":"PASSED [sig-apps] ReplicationController should adopt matching pods on creation [Conformance]","total":-1,"completed":23,"skipped":159,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 17 lines ...
Oct  1 09:01:43.786: INFO: PersistentVolumeClaim pvc-mjmm4 found but phase is Pending instead of Bound.
Oct  1 09:01:45.918: INFO: PersistentVolumeClaim pvc-mjmm4 found and phase=Bound (6.532406583s)
Oct  1 09:01:45.918: INFO: Waiting up to 3m0s for PersistentVolume local-w2zxh to have phase Bound
Oct  1 09:01:46.051: INFO: PersistentVolume local-w2zxh found and phase=Bound (132.428049ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-558x
STEP: Creating a pod to test subpath
Oct  1 09:01:46.450: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-558x" in namespace "provisioning-9873" to be "Succeeded or Failed"
Oct  1 09:01:46.583: INFO: Pod "pod-subpath-test-preprovisionedpv-558x": Phase="Pending", Reason="", readiness=false. Elapsed: 133.045206ms
Oct  1 09:01:48.716: INFO: Pod "pod-subpath-test-preprovisionedpv-558x": Phase="Pending", Reason="", readiness=false. Elapsed: 2.266061239s
Oct  1 09:01:50.856: INFO: Pod "pod-subpath-test-preprovisionedpv-558x": Phase="Pending", Reason="", readiness=false. Elapsed: 4.406060556s
Oct  1 09:01:52.989: INFO: Pod "pod-subpath-test-preprovisionedpv-558x": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.538963526s
STEP: Saw pod success
Oct  1 09:01:52.989: INFO: Pod "pod-subpath-test-preprovisionedpv-558x" satisfied condition "Succeeded or Failed"
Oct  1 09:01:53.122: INFO: Trying to get logs from node ip-172-20-41-255.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-558x container test-container-subpath-preprovisionedpv-558x: <nil>
STEP: delete the pod
Oct  1 09:01:53.414: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-558x to disappear
Oct  1 09:01:53.546: INFO: Pod pod-subpath-test-preprovisionedpv-558x no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-558x
Oct  1 09:01:53.547: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-558x" in namespace "provisioning-9873"
... skipping 19 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support existing single file [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:216
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir-bindmounted] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing single file [LinuxOnly]","total":-1,"completed":28,"skipped":194,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:55.421: INFO: Only supported for providers [azure] (not aws)
[AfterEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 70 lines ...
• [SLOW TEST:9.595 seconds]
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
  should mutate pod and apply defaults after mutation [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate pod and apply defaults after mutation [Conformance]","total":-1,"completed":38,"skipped":226,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:55.556: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 25 lines ...
[AfterEach] [sig-api-machinery] client-go should negotiate
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 09:01:55.728: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready

•
------------------------------
{"msg":"PASSED [sig-api-machinery] client-go should negotiate watch and report errors with accept \"application/vnd.kubernetes.protobuf,application/json\"","total":-1,"completed":29,"skipped":202,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:01:55.876: INFO: Driver csi-hostpath doesn't support PreprovisionedPV -- skipping
... skipping 35 lines ...
• [SLOW TEST:7.010 seconds]
[sig-api-machinery] Garbage collector
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
  should not be blocked by dependency circle [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-api-machinery] Garbage collector should not be blocked by dependency circle [Conformance]","total":-1,"completed":39,"skipped":229,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:02:02.594: INFO: Driver hostPathSymlink doesn't support PreprovisionedPV -- skipping
... skipping 118 lines ...
• [SLOW TEST:7.967 seconds]
[sig-network] Services
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
  should allow pods to hairpin back to themselves through services
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:996
------------------------------
{"msg":"PASSED [sig-network] Services should allow pods to hairpin back to themselves through services","total":-1,"completed":30,"skipped":204,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:02:03.872: INFO: Only supported for providers [gce gke] (not aws)
... skipping 54 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:151

      Driver local doesn't support DynamicPV -- skipping

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:173
------------------------------
{"msg":"PASSED [sig-storage] PersistentVolumes NFS with Single PV - PVC pairs create a PVC and non-pre-bound PV: test write access","total":-1,"completed":32,"skipped":308,"failed":0}
[BeforeEach] [sig-cli] Kubectl client
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 09:01:48.963: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename kubectl
STEP: Waiting for a default service account to be provisioned in namespace
... skipping 29 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/framework.go:23
  Kubectl client-side validation
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:988
    should create/apply a CR with unknown fields for CRD with no validation schema
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:989
------------------------------
{"msg":"PASSED [sig-cli] Kubectl client Kubectl client-side validation should create/apply a CR with unknown fields for CRD with no validation schema","total":-1,"completed":33,"skipped":308,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][sig-windows] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:02:04.686: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][sig-windows] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 185 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  CSI Volume expansion
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_mock_volume.go:555
    should not expand volume if resizingOnDriver=off, resizingOnSC=on
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_mock_volume.go:584
------------------------------
{"msg":"PASSED [sig-storage] CSI mock volume CSI Volume expansion should not expand volume if resizingOnDriver=off, resizingOnSC=on","total":-1,"completed":20,"skipped":103,"failed":1,"failures":["[sig-cli] Kubectl Port forwarding With a server listening on localhost should support forwarding over websockets"]}

S
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:02:05.234: INFO: Driver local doesn't support InlineVolume -- skipping
... skipping 93 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Inline-volume (default fs)] volumes
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should store data
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:151
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: emptydir] [Testpattern: Inline-volume (default fs)] volumes should store data","total":-1,"completed":17,"skipped":134,"failed":1,"failures":["[sig-network] Services should be able to up and down services"]}

SS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][sig-windows] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:02:08.666: INFO: Only supported for providers [azure] (not aws)
... skipping 223 lines ...
Oct  1 08:57:13.304: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-282 create -f -'
Oct  1 08:57:14.049: INFO: stderr: ""
Oct  1 08:57:14.049: INFO: stdout: "deployment.apps/agnhost-replica created\n"
STEP: validating guestbook app
Oct  1 08:57:14.049: INFO: Waiting for all frontend pods to be Running.
Oct  1 08:57:19.199: INFO: Waiting for frontend to serve content.
Oct  1 08:57:24.336: INFO: Failed to get response from guestbook. err: the server responded with the status code 417 but did not return more information (get services frontend), response: 
Oct  1 08:58:04.484: INFO: Failed to get response from guestbook. err: the server rejected our request for an unknown reason (get services frontend), response: 
Oct  1 08:58:29.651: INFO: Failed to get response from guestbook. err: the server rejected our request for an unknown reason (get services frontend), response: 
Oct  1 08:58:34.785: INFO: Trying to add a new entry to the guestbook.
Oct  1 08:58:39.918: INFO: Failed to get response from guestbook. err: the server responded with the status code 417 but did not return more information (get services frontend), response: 
Oct  1 08:59:20.056: INFO: Failed to get response from guestbook. err: the server rejected our request for an unknown reason (get services frontend), response: 
Oct  1 08:59:35.193: INFO: Failed to get response from guestbook. err: the server responded with the status code 417 but did not return more information (get services frontend), response: 
Oct  1 08:59:55.327: INFO: Failed to get response from guestbook. err: the server responded with the status code 417 but did not return more information (get services frontend), response: 
Oct  1 09:00:00.464: INFO: Verifying that added entry can be retrieved.
Oct  1 09:00:20.602: INFO: Failed to get response from guestbook. err: the server rejected our request for an unknown reason (get services frontend), response: 
Oct  1 09:01:15.740: INFO: Failed to get response from guestbook. err: the server rejected our request for an unknown reason (get services frontend), response: 
Oct  1 09:02:00.878: INFO: Failed to get response from guestbook. err: the server rejected our request for an unknown reason (get services frontend), response: 
STEP: using delete to clean up resources
Oct  1 09:02:06.015: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-282 delete --grace-period=0 --force -f -'
Oct  1 09:02:06.659: INFO: stderr: "warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely.\n"
Oct  1 09:02:06.659: INFO: stdout: "service \"agnhost-replica\" force deleted\n"
STEP: using delete to clean up resources
Oct  1 09:02:06.659: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-282 delete --grace-period=0 --force -f -'
... skipping 49 lines ...
• [SLOW TEST:5.326 seconds]
[sig-apps] Job
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23
  should run a job to completion when tasks succeed
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/job.go:48
------------------------------
{"msg":"PASSED [sig-apps] Job should run a job to completion when tasks succeed","total":-1,"completed":21,"skipped":108,"failed":1,"failures":["[sig-cli] Kubectl Port forwarding With a server listening on localhost should support forwarding over websockets"]}

SSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ntfs)][sig-windows] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:02:10.617: INFO: Only supported for providers [vsphere] (not aws)
... skipping 58 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:361

      Driver local doesn't support InlineVolume -- skipping

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:173
------------------------------
{"msg":"PASSED [sig-cli] Kubectl client Guestbook application should create and stop a working application  [Conformance]","total":-1,"completed":21,"skipped":172,"failed":0}
[BeforeEach] [k8s.io] Variable Expansion
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 09:02:10.114: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename var-expansion
STEP: Waiting for a default service account to be provisioned in namespace
[It] should allow substituting values in a container's command [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating a pod to test substitution in container's command
Oct  1 09:02:10.904: INFO: Waiting up to 5m0s for pod "var-expansion-1466d2a2-3d74-4eb9-a183-168a909c2707" in namespace "var-expansion-1699" to be "Succeeded or Failed"
Oct  1 09:02:11.035: INFO: Pod "var-expansion-1466d2a2-3d74-4eb9-a183-168a909c2707": Phase="Pending", Reason="", readiness=false. Elapsed: 130.880014ms
Oct  1 09:02:13.167: INFO: Pod "var-expansion-1466d2a2-3d74-4eb9-a183-168a909c2707": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.262276041s
STEP: Saw pod success
Oct  1 09:02:13.167: INFO: Pod "var-expansion-1466d2a2-3d74-4eb9-a183-168a909c2707" satisfied condition "Succeeded or Failed"
Oct  1 09:02:13.298: INFO: Trying to get logs from node ip-172-20-60-245.ap-northeast-1.compute.internal pod var-expansion-1466d2a2-3d74-4eb9-a183-168a909c2707 container dapi-container: <nil>
STEP: delete the pod
Oct  1 09:02:13.566: INFO: Waiting for pod var-expansion-1466d2a2-3d74-4eb9-a183-168a909c2707 to disappear
Oct  1 09:02:13.697: INFO: Pod var-expansion-1466d2a2-3d74-4eb9-a183-168a909c2707 no longer exists
[AfterEach] [k8s.io] Variable Expansion
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 09:02:13.697: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "var-expansion-1699" for this suite.

•
------------------------------
{"msg":"PASSED [k8s.io] Variable Expansion should allow substituting values in a container's command [NodeConformance] [Conformance]","total":-1,"completed":22,"skipped":172,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
[BeforeEach] [Testpattern: Inline-volume (default fs)] volumes
... skipping 7 lines ...
Oct  1 09:01:54.621: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct  1 09:01:55.655: INFO: Successfully created a new PD: "aws://ap-northeast-1a/vol-0c1e40808a183fabc".
Oct  1 09:01:55.655: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-gfml
STEP: Creating a pod to test exec-volume-test
Oct  1 09:01:55.791: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-gfml" in namespace "volume-5261" to be "Succeeded or Failed"
Oct  1 09:01:55.923: INFO: Pod "exec-volume-test-inlinevolume-gfml": Phase="Pending", Reason="", readiness=false. Elapsed: 132.338802ms
Oct  1 09:01:58.056: INFO: Pod "exec-volume-test-inlinevolume-gfml": Phase="Pending", Reason="", readiness=false. Elapsed: 2.265494042s
Oct  1 09:02:00.189: INFO: Pod "exec-volume-test-inlinevolume-gfml": Phase="Pending", Reason="", readiness=false. Elapsed: 4.398745258s
Oct  1 09:02:02.324: INFO: Pod "exec-volume-test-inlinevolume-gfml": Phase="Pending", Reason="", readiness=false. Elapsed: 6.533510294s
Oct  1 09:02:04.461: INFO: Pod "exec-volume-test-inlinevolume-gfml": Phase="Pending", Reason="", readiness=false. Elapsed: 8.670275892s
Oct  1 09:02:06.594: INFO: Pod "exec-volume-test-inlinevolume-gfml": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.803379771s
STEP: Saw pod success
Oct  1 09:02:06.594: INFO: Pod "exec-volume-test-inlinevolume-gfml" satisfied condition "Succeeded or Failed"
Oct  1 09:02:06.727: INFO: Trying to get logs from node ip-172-20-35-235.ap-northeast-1.compute.internal pod exec-volume-test-inlinevolume-gfml container exec-container-inlinevolume-gfml: <nil>
STEP: delete the pod
Oct  1 09:02:06.997: INFO: Waiting for pod exec-volume-test-inlinevolume-gfml to disappear
Oct  1 09:02:07.129: INFO: Pod exec-volume-test-inlinevolume-gfml no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-gfml
Oct  1 09:02:07.129: INFO: Deleting pod "exec-volume-test-inlinevolume-gfml" in namespace "volume-5261"
Oct  1 09:02:07.512: INFO: Couldn't delete PD "aws://ap-northeast-1a/vol-0c1e40808a183fabc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c1e40808a183fabc is currently attached to i-02ad688f57412ef93
	status code: 400, request id: 8f0aa32a-ca07-49ee-a0d7-71a76f89fffc
Oct  1 09:02:13.240: INFO: Couldn't delete PD "aws://ap-northeast-1a/vol-0c1e40808a183fabc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c1e40808a183fabc is currently attached to i-02ad688f57412ef93
	status code: 400, request id: 760147dc-a832-4549-a289-02044d91b149
Oct  1 09:02:19.008: INFO: Successfully deleted PD "aws://ap-northeast-1a/vol-0c1e40808a183fabc".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 09:02:19.008: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5261" for this suite.
... skipping 6 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Inline-volume (default fs)] volumes
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should allow exec of files on the volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:192
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: aws] [Testpattern: Inline-volume (default fs)] volumes should allow exec of files on the volume","total":-1,"completed":27,"skipped":249,"failed":0}
[BeforeEach] [Testpattern: Inline-volume (ntfs)][sig-windows] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:02:19.295: INFO: Driver local doesn't support InlineVolume -- skipping
[AfterEach] [Testpattern: Inline-volume (ntfs)][sig-windows] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 180 lines ...
[sig-storage] In-tree Volumes
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  [Driver: gluster]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Dynamic PV (immediate binding)] topology
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should fail to schedule a pod which has topologies that conflict with AllowedTopologies [BeforeEach]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Only supported for node OS distro [gci ubuntu custom] (not debian)

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/drivers/in_tree.go:265
------------------------------
... skipping 53 lines ...
• [SLOW TEST:14.730 seconds]
[k8s.io] KubeletManagedEtcHosts
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  should test kubelet managed /etc/hosts file [LinuxOnly] [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [k8s.io] KubeletManagedEtcHosts should test kubelet managed /etc/hosts file [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":34,"skipped":320,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:02:19.499: INFO: Only supported for providers [gce gke] (not aws)
... skipping 37 lines ...
I1001 08:59:59.639197    5415 runners.go:190] Created replication controller with name: affinity-nodeport-timeout, namespace: services-6630, replica count: 3
I1001 09:00:02.789725    5415 runners.go:190] affinity-nodeport-timeout Pods: 3 out of 3 created, 2 running, 1 pending, 0 waiting, 0 inactive, 0 terminating, 0 unknown, 0 runningButNotReady 
I1001 09:00:05.790099    5415 runners.go:190] affinity-nodeport-timeout Pods: 3 out of 3 created, 3 running, 0 pending, 0 waiting, 0 inactive, 0 terminating, 0 unknown, 0 runningButNotReady 
Oct  1 09:00:06.188: INFO: Creating new exec pod
Oct  1 09:00:09.874: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-6630 exec execpod-affinitygz7ln -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Oct  1 09:00:16.238: INFO: rc: 1
Oct  1 09:00:16.238: INFO: Service reachability failing with error: error running /tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-6630 exec execpod-affinitygz7ln -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:
Command stdout:

stderr:
+ nc -zv -t -w 2 affinity-nodeport-timeout 80
nc: getaddrinfo: Try again
command terminated with exit code 1

error:
exit status 1
Retrying...
Oct  1 09:00:17.238: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-6630 exec execpod-affinitygz7ln -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Oct  1 09:00:23.623: INFO: rc: 1
Oct  1 09:00:23.623: INFO: Service reachability failing with error: error running /tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-6630 exec execpod-affinitygz7ln -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:
Command stdout:

stderr:
+ nc -zv -t -w 2 affinity-nodeport-timeout 80
nc: getaddrinfo: Try again
command terminated with exit code 1

error:
exit status 1
Retrying...
Oct  1 09:00:24.238: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-6630 exec execpod-affinitygz7ln -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Oct  1 09:00:30.635: INFO: rc: 1
Oct  1 09:00:30.635: INFO: Service reachability failing with error: error running /tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-6630 exec execpod-affinitygz7ln -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:
Command stdout:

stderr:
+ nc -zv -t -w 2 affinity-nodeport-timeout 80
nc: getaddrinfo: Try again
command terminated with exit code 1

error:
exit status 1
Retrying...
Oct  1 09:00:31.238: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-6630 exec execpod-affinitygz7ln -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Oct  1 09:00:37.658: INFO: rc: 1
Oct  1 09:00:37.658: INFO: Service reachability failing with error: error running /tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-6630 exec execpod-affinitygz7ln -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:
Command stdout:

stderr:
+ nc -zv -t -w 2 affinity-nodeport-timeout 80
nc: getaddrinfo: Try again
command terminated with exit code 1

error:
exit status 1
Retrying...
Oct  1 09:00:38.238: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-6630 exec execpod-affinitygz7ln -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Oct  1 09:00:44.621: INFO: rc: 1
Oct  1 09:00:44.621: INFO: Service reachability failing with error: error running /tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-6630 exec execpod-affinitygz7ln -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:
Command stdout:

stderr:
+ nc -zv -t -w 2 affinity-nodeport-timeout 80
nc: getaddrinfo: Try again
command terminated with exit code 1

error:
exit status 1
Retrying...
Oct  1 09:00:45.238: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-6630 exec execpod-affinitygz7ln -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Oct  1 09:00:48.579: INFO: rc: 1
Oct  1 09:00:48.580: INFO: Service reachability failing with error: error running /tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-6630 exec execpod-affinitygz7ln -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:
Command stdout:

stderr:
+ nc -zv -t -w 2 affinity-nodeport-timeout 80
nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
command terminated with exit code 1

error:
exit status 1
Retrying...
Oct  1 09:00:49.238: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-6630 exec execpod-affinitygz7ln -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Oct  1 09:00:52.594: INFO: rc: 1
Oct  1 09:00:52.594: INFO: Service reachability failing with error: error running /tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-6630 exec execpod-affinitygz7ln -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:
Command stdout:

stderr:
+ nc -zv -t -w 2 affinity-nodeport-timeout 80
nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
command terminated with exit code 1

error:
exit status 1
Retrying...
Oct  1 09:00:53.238: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-6630 exec execpod-affinitygz7ln -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Oct  1 09:00:56.608: INFO: rc: 1
Oct  1 09:00:56.608: INFO: Service reachability failing with error: error running /tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-6630 exec execpod-affinitygz7ln -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:
Command stdout:

stderr:
+ nc -zv -t -w 2 affinity-nodeport-timeout 80
nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
command terminated with exit code 1

error:
exit status 1
Retrying...
Oct  1 09:00:57.238: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-6630 exec execpod-affinitygz7ln -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Oct  1 09:01:03.622: INFO: rc: 1
Oct  1 09:01:03.622: INFO: Service reachability failing with error: error running /tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-6630 exec execpod-affinitygz7ln -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:
Command stdout:

stderr:
+ nc -zv -t -w 2 affinity-nodeport-timeout 80
nc: getaddrinfo: Try again
command terminated with exit code 1

error:
exit status 1
Retrying...
Oct  1 09:01:04.239: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-6630 exec execpod-affinitygz7ln -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Oct  1 09:01:10.603: INFO: rc: 1
Oct  1 09:01:10.603: INFO: Service reachability failing with error: error running /tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-6630 exec execpod-affinitygz7ln -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:
Command stdout:

stderr:
+ nc -zv -t -w 2 affinity-nodeport-timeout 80
nc: getaddrinfo: Try again
command terminated with exit code 1

error:
exit status 1
Retrying...
Oct  1 09:01:11.238: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-6630 exec execpod-affinitygz7ln -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Oct  1 09:01:12.659: INFO: stderr: "+ nc -zv -t -w 2 affinity-nodeport-timeout 80\nConnection to affinity-nodeport-timeout 80 port [tcp/http] succeeded!\n"
Oct  1 09:01:12.659: INFO: stdout: ""
Oct  1 09:01:12.659: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-6630 exec execpod-affinitygz7ln -- /bin/sh -x -c nc -zv -t -w 2 100.68.48.53 80'
... skipping 144 lines ...
• [SLOW TEST:28.100 seconds]
[sig-network] Services
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
  should be able to switch session affinity for NodePort service [LinuxOnly] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-network] Services should be able to switch session affinity for NodePort service [LinuxOnly] [Conformance]","total":-1,"completed":24,"skipped":161,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:02:22.331: INFO: Driver hostPath doesn't support DynamicPV -- skipping
... skipping 28 lines ...
[It] should support readOnly directory specified in the volumeMount
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:361
Oct  1 09:02:14.635: INFO: In-tree plugin kubernetes.io/empty-dir is not migrated, not validating any metrics
Oct  1 09:02:14.635: INFO: Creating resource for inline volume
STEP: Creating pod pod-subpath-test-inlinevolume-2wmb
STEP: Creating a pod to test subpath
Oct  1 09:02:14.769: INFO: Waiting up to 5m0s for pod "pod-subpath-test-inlinevolume-2wmb" in namespace "provisioning-6168" to be "Succeeded or Failed"
Oct  1 09:02:14.900: INFO: Pod "pod-subpath-test-inlinevolume-2wmb": Phase="Pending", Reason="", readiness=false. Elapsed: 130.887494ms
Oct  1 09:02:17.031: INFO: Pod "pod-subpath-test-inlinevolume-2wmb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.262347514s
Oct  1 09:02:19.163: INFO: Pod "pod-subpath-test-inlinevolume-2wmb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.394270377s
Oct  1 09:02:21.294: INFO: Pod "pod-subpath-test-inlinevolume-2wmb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.525637064s
STEP: Saw pod success
Oct  1 09:02:21.294: INFO: Pod "pod-subpath-test-inlinevolume-2wmb" satisfied condition "Succeeded or Failed"
Oct  1 09:02:21.428: INFO: Trying to get logs from node ip-172-20-35-235.ap-northeast-1.compute.internal pod pod-subpath-test-inlinevolume-2wmb container test-container-subpath-inlinevolume-2wmb: <nil>
STEP: delete the pod
Oct  1 09:02:21.697: INFO: Waiting for pod pod-subpath-test-inlinevolume-2wmb to disappear
Oct  1 09:02:21.828: INFO: Pod pod-subpath-test-inlinevolume-2wmb no longer exists
STEP: Deleting pod pod-subpath-test-inlinevolume-2wmb
Oct  1 09:02:21.828: INFO: Deleting pod "pod-subpath-test-inlinevolume-2wmb" in namespace "provisioning-6168"
... skipping 12 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Inline-volume (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support readOnly directory specified in the volumeMount
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:361
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: emptydir] [Testpattern: Inline-volume (default fs)] subPath should support readOnly directory specified in the volumeMount","total":-1,"completed":23,"skipped":173,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:02:22.362: INFO: Only supported for providers [gce gke] (not aws)
[AfterEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 58 lines ...
• [SLOW TEST:33.779 seconds]
[sig-storage] PVC Protection
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  Verify that scheduling of a pod that uses PVC that is being deleted fails and the pod becomes Unschedulable
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/pvc_protection.go:143
------------------------------
{"msg":"PASSED [sig-storage] PVC Protection Verify that scheduling of a pod that uses PVC that is being deleted fails and the pod becomes Unschedulable","total":-1,"completed":26,"skipped":151,"failed":0}
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:02:23.559: INFO: Driver supports dynamic provisioning, skipping InlineVolume pattern
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 113 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 09:02:24.340: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "kubectl-7031" for this suite.

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

SS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:02:24.633: INFO: Driver supports dynamic provisioning, skipping InlineVolume pattern
... skipping 56 lines ...
STEP: Deleting pod hostexec-ip-172-20-35-235.ap-northeast-1.compute.internal-8nnk4 in namespace volumemode-1932
Oct  1 09:02:08.624: INFO: Deleting pod "pod-8525e71f-a774-4b64-9f97-d4def6c22076" in namespace "volumemode-1932"
Oct  1 09:02:08.757: INFO: Wait up to 5m0s for pod "pod-8525e71f-a774-4b64-9f97-d4def6c22076" to be fully deleted
STEP: Deleting pv and pvc
Oct  1 09:02:15.028: INFO: Deleting PersistentVolumeClaim "pvc-nszhj"
Oct  1 09:02:15.166: INFO: Deleting PersistentVolume "aws-27p75"
Oct  1 09:02:15.636: INFO: Couldn't delete PD "aws://ap-northeast-1a/vol-06372f443169992a2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06372f443169992a2 is currently attached to i-02ad688f57412ef93
	status code: 400, request id: c407bc67-d750-41cb-a5da-471ceba1d57f
Oct  1 09:02:21.386: INFO: Couldn't delete PD "aws://ap-northeast-1a/vol-06372f443169992a2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06372f443169992a2 is currently attached to i-02ad688f57412ef93
	status code: 400, request id: dc5efaae-9ada-4711-9396-738c07a96283
Oct  1 09:02:27.134: INFO: Successfully deleted PD "aws://ap-northeast-1a/vol-06372f443169992a2".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 09:02:27.134: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-1932" for this suite.
... skipping 6 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should not mount / map unused volumes in a pod [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:347
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: aws] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]","total":-1,"completed":22,"skipped":158,"failed":0}

SSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ext3)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:02:27.458: INFO: Driver hostPath doesn't support DynamicPV -- skipping
... skipping 43 lines ...
Oct  1 09:02:13.417: INFO: PersistentVolumeClaim pvc-nnf2h found but phase is Pending instead of Bound.
Oct  1 09:02:15.550: INFO: PersistentVolumeClaim pvc-nnf2h found and phase=Bound (6.531874789s)
Oct  1 09:02:15.550: INFO: Waiting up to 3m0s for PersistentVolume local-rzjqr to have phase Bound
Oct  1 09:02:15.684: INFO: PersistentVolume local-rzjqr found and phase=Bound (133.925608ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-t5d9
STEP: Creating a pod to test subpath
Oct  1 09:02:16.083: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-t5d9" in namespace "provisioning-6422" to be "Succeeded or Failed"
Oct  1 09:02:16.216: INFO: Pod "pod-subpath-test-preprovisionedpv-t5d9": Phase="Pending", Reason="", readiness=false. Elapsed: 132.430365ms
Oct  1 09:02:18.349: INFO: Pod "pod-subpath-test-preprovisionedpv-t5d9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.265952262s
Oct  1 09:02:20.482: INFO: Pod "pod-subpath-test-preprovisionedpv-t5d9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.398921335s
Oct  1 09:02:22.615: INFO: Pod "pod-subpath-test-preprovisionedpv-t5d9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.53200864s
STEP: Saw pod success
Oct  1 09:02:22.615: INFO: Pod "pod-subpath-test-preprovisionedpv-t5d9" satisfied condition "Succeeded or Failed"
Oct  1 09:02:22.748: INFO: Trying to get logs from node ip-172-20-35-235.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-t5d9 container test-container-volume-preprovisionedpv-t5d9: <nil>
STEP: delete the pod
Oct  1 09:02:23.022: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-t5d9 to disappear
Oct  1 09:02:23.157: INFO: Pod pod-subpath-test-preprovisionedpv-t5d9 no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-t5d9
Oct  1 09:02:23.157: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-t5d9" in namespace "provisioning-6422"
... skipping 26 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support existing directory
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:202
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: blockfs] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing directory","total":-1,"completed":40,"skipped":242,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
... skipping 54 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should not mount / map unused volumes in a pod [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:347
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]","total":-1,"completed":31,"skipped":209,"failed":0}

S
------------------------------
[BeforeEach] [sig-api-machinery] Watchers
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 28 lines ...
• [SLOW TEST:12.716 seconds]
[sig-api-machinery] Watchers
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
  should observe an object deletion if it stops meeting the requirements of the selector [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-api-machinery] Watchers should observe an object deletion if it stops meeting the requirements of the selector [Conformance]","total":-1,"completed":35,"skipped":324,"failed":0}

SSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:02:32.256: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 50 lines ...
• [SLOW TEST:7.246 seconds]
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
  should deny crd creation [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should deny crd creation [Conformance]","total":-1,"completed":23,"skipped":170,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:02:34.731: INFO: Driver emptydir doesn't support PreprovisionedPV -- skipping
... skipping 74 lines ...
Oct  1 09:01:34.019: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7611 exec verify-service-up-exec-pod-gzvbx -- /bin/sh -x -c for i in $(seq 1 150); do wget -q -T 1 -O - http://100.68.112.30:80 2>&1 || true; echo; done'
Oct  1 09:02:26.667: INFO: stderr: "+ seq 1 150\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ echo\n+ wget -q -T 1 -O - http://100.68.112.30:80\n+ true\n+ echo\n"
Oct  1 09:02:26.667: INFO: stdout: "wget: download timed out\n\nservice-proxy-toggled-slq8z\nwget: download timed out\n\nwget: download timed out\n\nwget: download timed out\n\nwget: download timed out\n\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-slq8z\nwget: download timed out\n\nwget: download timed out\n\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-pkfx5\nwget: download timed out\n\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-pkfx5\nwget: download timed out\n\nwget: download timed out\n\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-slq8z\nwget: download timed out\n\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-slq8z\nwget: download timed out\n\nwget: download timed out\n\nwget: download timed out\n\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-slq8z\nwget: download timed out\n\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-pkfx5\nwget: download timed out\n\nservice-proxy-toggled-pkfx5\nwget: download timed out\n\nservice-proxy-toggled-slq8z\nwget: download timed out\n\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-pkfx5\nwget: download timed out\n\nservice-proxy-toggled-pkfx5\nwget: download timed out\n\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-slq8z\nwget: download timed out\n\nwget: download timed out\n\nservice-proxy-toggled-slq8z\nwget: download timed out\n\nwget: download timed out\n\nservice-proxy-toggled-pkfx5\nwget: download timed out\n\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-pkfx5\nwget: download timed out\n\nwget: download timed out\n\nwget: download timed out\n\nwget: download timed out\n\nservice-proxy-toggled-slq8z\nwget: download timed out\n\nservice-proxy-toggled-slq8z\nwget: download timed out\n\nservice-proxy-toggled-pkfx5\nwget: download timed out\n\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-pkfx5\nwget: download timed out\n\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-pkfx5\nwget: download timed out\n\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-pkfx5\nwget: download timed out\n\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-pkfx5\nwget: download timed out\n\nservice-proxy-toggled-pkfx5\nwget: download timed out\n\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-slq8z\nwget: download timed out\n\nwget: download timed out\n\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-slq8z\nwget: download timed out\n\nwget: download timed out\n\nwget: download timed out\n\nwget: download timed out\n\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-slq8z\nwget: download timed out\n\nwget: download timed out\n\nservice-proxy-toggled-slq8z\nwget: download timed out\n\nwget: download timed out\n\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-slq8z\nwget: download timed out\n\nwget: download timed out\n\nwget: download timed out\n\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-pkfx5\nservice-proxy-toggled-slq8z\nservice-proxy-toggled-slq8z\nwget: download timed out\n\n"
Oct  1 09:02:26.667: INFO: Unable to reach the following endpoints of service 100.68.112.30: map[service-proxy-toggled-p2mnb:{}]
STEP: Deleting pod verify-service-up-host-exec-pod in namespace services-7611
STEP: Deleting pod verify-service-up-exec-pod-gzvbx in namespace services-7611
Oct  1 09:02:31.944: FAIL: Unexpected error:
    <*errors.errorString | 0xc003114070>: {
        s: "service verification failed for: 100.68.112.30\nexpected [service-proxy-toggled-p2mnb service-proxy-toggled-pkfx5 service-proxy-toggled-slq8z]\nreceived [service-proxy-toggled-pkfx5 service-proxy-toggled-slq8z wget: download timed out]",
    }
    service verification failed for: 100.68.112.30
    expected [service-proxy-toggled-p2mnb service-proxy-toggled-pkfx5 service-proxy-toggled-slq8z]
    received [service-proxy-toggled-pkfx5 service-proxy-toggled-slq8z wget: download timed out]
occurred

Full Stack Trace
k8s.io/kubernetes/test/e2e/network.glob..func24.35()
... skipping 282 lines ...
• Failure [338.310 seconds]
[sig-network] Services
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
  should implement service.kubernetes.io/service-proxy-name [It]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:2536

  Oct  1 09:02:31.944: Unexpected error:
      <*errors.errorString | 0xc003114070>: {
          s: "service verification failed for: 100.68.112.30\nexpected [service-proxy-toggled-p2mnb service-proxy-toggled-pkfx5 service-proxy-toggled-slq8z]\nreceived [service-proxy-toggled-pkfx5 service-proxy-toggled-slq8z wget: download timed out]",
      }
      service verification failed for: 100.68.112.30
      expected [service-proxy-toggled-p2mnb service-proxy-toggled-pkfx5 service-proxy-toggled-slq8z]
      received [service-proxy-toggled-pkfx5 service-proxy-toggled-slq8z wget: download timed out]
  occurred

  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:2560
------------------------------
{"msg":"FAILED [sig-network] Services should implement service.kubernetes.io/service-proxy-name","total":-1,"completed":31,"skipped":262,"failed":1,"failures":["[sig-network] Services should implement service.kubernetes.io/service-proxy-name"]}

S
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ext3)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:02:37.629: INFO: Driver aws doesn't support ext3 -- skipping
... skipping 45 lines ...
STEP: Building a namespace api object, basename projected
STEP: Waiting for a default service account to be provisioned in namespace
[It] should be consumable from pods in volume with mappings and Item Mode set [LinuxOnly] [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating projection with secret that has name projected-secret-test-map-9f56876c-8f6a-4be0-a4aa-391d40f8bbde
STEP: Creating a pod to test consume secrets
Oct  1 09:02:35.676: INFO: Waiting up to 5m0s for pod "pod-projected-secrets-8812f11a-017b-4a8f-b9d0-f39ca60a5a1f" in namespace "projected-1450" to be "Succeeded or Failed"
Oct  1 09:02:35.808: INFO: Pod "pod-projected-secrets-8812f11a-017b-4a8f-b9d0-f39ca60a5a1f": Phase="Pending", Reason="", readiness=false. Elapsed: 132.199962ms
Oct  1 09:02:37.941: INFO: Pod "pod-projected-secrets-8812f11a-017b-4a8f-b9d0-f39ca60a5a1f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.264739944s
STEP: Saw pod success
Oct  1 09:02:37.941: INFO: Pod "pod-projected-secrets-8812f11a-017b-4a8f-b9d0-f39ca60a5a1f" satisfied condition "Succeeded or Failed"
Oct  1 09:02:38.074: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod pod-projected-secrets-8812f11a-017b-4a8f-b9d0-f39ca60a5a1f container projected-secret-volume-test: <nil>
STEP: delete the pod
Oct  1 09:02:38.348: INFO: Waiting for pod pod-projected-secrets-8812f11a-017b-4a8f-b9d0-f39ca60a5a1f to disappear
Oct  1 09:02:38.480: INFO: Pod pod-projected-secrets-8812f11a-017b-4a8f-b9d0-f39ca60a5a1f no longer exists
[AfterEach] [sig-storage] Projected secret
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 09:02:38.480: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "projected-1450" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] Projected secret should be consumable from pods in volume with mappings and Item Mode set [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":24,"skipped":174,"failed":0}
[BeforeEach] [Testpattern: Pre-provisioned PV (ntfs)][sig-windows] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:02:38.756: INFO: Only supported for node OS distro [gci ubuntu custom] (not debian)
[AfterEach] [Testpattern: Pre-provisioned PV (ntfs)][sig-windows] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 24 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/subpath.go:38
STEP: Setting up data
[It] should support subpaths with secret pod [LinuxOnly] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating pod pod-subpath-test-secret-clc7
STEP: Creating a pod to test atomic-volume-subpath
Oct  1 09:02:20.474: INFO: Waiting up to 5m0s for pod "pod-subpath-test-secret-clc7" in namespace "subpath-6998" to be "Succeeded or Failed"
Oct  1 09:02:20.607: INFO: Pod "pod-subpath-test-secret-clc7": Phase="Pending", Reason="", readiness=false. Elapsed: 132.546394ms
Oct  1 09:02:22.740: INFO: Pod "pod-subpath-test-secret-clc7": Phase="Running", Reason="", readiness=true. Elapsed: 2.265196495s
Oct  1 09:02:24.873: INFO: Pod "pod-subpath-test-secret-clc7": Phase="Running", Reason="", readiness=true. Elapsed: 4.398250761s
Oct  1 09:02:27.005: INFO: Pod "pod-subpath-test-secret-clc7": Phase="Running", Reason="", readiness=true. Elapsed: 6.531008758s
Oct  1 09:02:29.138: INFO: Pod "pod-subpath-test-secret-clc7": Phase="Running", Reason="", readiness=true. Elapsed: 8.663982079s
Oct  1 09:02:31.272: INFO: Pod "pod-subpath-test-secret-clc7": Phase="Running", Reason="", readiness=true. Elapsed: 10.797607996s
Oct  1 09:02:33.405: INFO: Pod "pod-subpath-test-secret-clc7": Phase="Running", Reason="", readiness=true. Elapsed: 12.930071866s
Oct  1 09:02:35.537: INFO: Pod "pod-subpath-test-secret-clc7": Phase="Running", Reason="", readiness=true. Elapsed: 15.062739609s
Oct  1 09:02:37.670: INFO: Pod "pod-subpath-test-secret-clc7": Phase="Running", Reason="", readiness=true. Elapsed: 17.195546794s
Oct  1 09:02:39.803: INFO: Pod "pod-subpath-test-secret-clc7": Phase="Running", Reason="", readiness=true. Elapsed: 19.328357049s
Oct  1 09:02:41.936: INFO: Pod "pod-subpath-test-secret-clc7": Phase="Running", Reason="", readiness=true. Elapsed: 21.461093342s
Oct  1 09:02:44.069: INFO: Pod "pod-subpath-test-secret-clc7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.594342383s
STEP: Saw pod success
Oct  1 09:02:44.069: INFO: Pod "pod-subpath-test-secret-clc7" satisfied condition "Succeeded or Failed"
Oct  1 09:02:44.202: INFO: Trying to get logs from node ip-172-20-35-235.ap-northeast-1.compute.internal pod pod-subpath-test-secret-clc7 container test-container-subpath-secret-clc7: <nil>
STEP: delete the pod
Oct  1 09:02:44.476: INFO: Waiting for pod pod-subpath-test-secret-clc7 to disappear
Oct  1 09:02:44.609: INFO: Pod pod-subpath-test-secret-clc7 no longer exists
STEP: Deleting pod pod-subpath-test-secret-clc7
Oct  1 09:02:44.609: INFO: Deleting pod "pod-subpath-test-secret-clc7" in namespace "subpath-6998"
... skipping 8 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  Atomic writer volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/subpath.go:34
    should support subpaths with secret pod [LinuxOnly] [Conformance]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-storage] Subpath Atomic writer volumes should support subpaths with secret pod [LinuxOnly] [Conformance]","total":-1,"completed":28,"skipped":269,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:02:45.027: INFO: Only supported for providers [vsphere] (not aws)
[AfterEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 71 lines ...
Oct  1 09:02:11.314: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7707-aws-scwt5gh
STEP: creating a claim
Oct  1 09:02:11.449: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gdln
STEP: Creating a pod to test subpath
Oct  1 09:02:11.848: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-gdln" in namespace "provisioning-7707" to be "Succeeded or Failed"
Oct  1 09:02:11.980: INFO: Pod "pod-subpath-test-dynamicpv-gdln": Phase="Pending", Reason="", readiness=false. Elapsed: 131.927792ms
Oct  1 09:02:14.112: INFO: Pod "pod-subpath-test-dynamicpv-gdln": Phase="Pending", Reason="", readiness=false. Elapsed: 2.264231653s
Oct  1 09:02:16.245: INFO: Pod "pod-subpath-test-dynamicpv-gdln": Phase="Pending", Reason="", readiness=false. Elapsed: 4.396649725s
Oct  1 09:02:18.377: INFO: Pod "pod-subpath-test-dynamicpv-gdln": Phase="Pending", Reason="", readiness=false. Elapsed: 6.529134315s
Oct  1 09:02:20.509: INFO: Pod "pod-subpath-test-dynamicpv-gdln": Phase="Pending", Reason="", readiness=false. Elapsed: 8.661318977s
Oct  1 09:02:22.642: INFO: Pod "pod-subpath-test-dynamicpv-gdln": Phase="Pending", Reason="", readiness=false. Elapsed: 10.793579704s
Oct  1 09:02:24.774: INFO: Pod "pod-subpath-test-dynamicpv-gdln": Phase="Pending", Reason="", readiness=false. Elapsed: 12.926038731s
Oct  1 09:02:26.907: INFO: Pod "pod-subpath-test-dynamicpv-gdln": Phase="Pending", Reason="", readiness=false. Elapsed: 15.05833241s
Oct  1 09:02:29.039: INFO: Pod "pod-subpath-test-dynamicpv-gdln": Phase="Pending", Reason="", readiness=false. Elapsed: 17.190821483s
Oct  1 09:02:31.171: INFO: Pod "pod-subpath-test-dynamicpv-gdln": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.323094138s
STEP: Saw pod success
Oct  1 09:02:31.171: INFO: Pod "pod-subpath-test-dynamicpv-gdln" satisfied condition "Succeeded or Failed"
Oct  1 09:02:31.303: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod pod-subpath-test-dynamicpv-gdln container test-container-volume-dynamicpv-gdln: <nil>
STEP: delete the pod
Oct  1 09:02:31.624: INFO: Waiting for pod pod-subpath-test-dynamicpv-gdln to disappear
Oct  1 09:02:31.757: INFO: Pod pod-subpath-test-dynamicpv-gdln no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-gdln
Oct  1 09:02:31.757: INFO: Deleting pod "pod-subpath-test-dynamicpv-gdln" in namespace "provisioning-7707"
... skipping 20 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Dynamic PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support existing directory
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:202
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: aws] [Testpattern: Dynamic PV (default fs)] subPath should support existing directory","total":-1,"completed":22,"skipped":120,"failed":1,"failures":["[sig-cli] Kubectl Port forwarding With a server listening on localhost should support forwarding over websockets"]}

S
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
[BeforeEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
... skipping 78 lines ...
Oct  1 09:02:42.496: INFO: Waiting for pod aws-client to disappear
Oct  1 09:02:42.632: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct  1 09:02:42.632: INFO: Deleting PersistentVolumeClaim "pvc-mrrcr"
Oct  1 09:02:42.770: INFO: Deleting PersistentVolume "aws-l69pf"
Oct  1 09:02:43.627: INFO: Couldn't delete PD "aws://ap-northeast-1a/vol-00bc5012d728435ea", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00bc5012d728435ea is currently attached to i-029bd822c8d7a82f8
	status code: 400, request id: fb55d36a-6b22-4c36-82bb-c9d7fd9bff4a
Oct  1 09:02:49.397: INFO: Successfully deleted PD "aws://ap-northeast-1a/vol-00bc5012d728435ea".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 09:02:49.397: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1734" for this suite.
... skipping 6 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (ext4)] volumes
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should store data
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:151
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: aws] [Testpattern: Pre-provisioned PV (ext4)] volumes should store data","total":-1,"completed":19,"skipped":147,"failed":1,"failures":["[sig-network] DNS should provide DNS for pods for Subdomain [Conformance]"]}

S
------------------------------
[BeforeEach] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 13 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 09:02:49.429: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "custom-resource-definition-4336" for this suite.

•
------------------------------
{"msg":"PASSED [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] should include custom resource definition resources in discovery documents [Conformance]","total":-1,"completed":23,"skipped":121,"failed":1,"failures":["[sig-cli] Kubectl Port forwarding With a server listening on localhost should support forwarding over websockets"]}

SS
------------------------------
[BeforeEach] [sig-cli] Kubectl Port forwarding
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 33 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/portforward.go:474
    that expects a client request
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/portforward.go:475
      should support a client that connects, sends NO DATA, and disconnects
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/portforward.go:476
------------------------------
{"msg":"PASSED [sig-cli] Kubectl Port forwarding With a server listening on localhost that expects a client request should support a client that connects, sends NO DATA, and disconnects","total":-1,"completed":32,"skipped":273,"failed":1,"failures":["[sig-network] Services should implement service.kubernetes.io/service-proxy-name"]}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:02:50.471: INFO: Only supported for providers [openstack] (not aws)
... skipping 98 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should be able to unmount after the subpath directory is deleted [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:441
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: tmpfs] [Testpattern: Pre-provisioned PV (default fs)] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly]","total":-1,"completed":18,"skipped":142,"failed":1,"failures":["[sig-network] Services should be able to up and down services"]}

SSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
... skipping 20 lines ...
Oct  1 09:02:44.226: INFO: PersistentVolumeClaim pvc-8mqs2 found but phase is Pending instead of Bound.
Oct  1 09:02:46.359: INFO: PersistentVolumeClaim pvc-8mqs2 found and phase=Bound (12.930302165s)
Oct  1 09:02:46.359: INFO: Waiting up to 3m0s for PersistentVolume local-g8brb to have phase Bound
Oct  1 09:02:46.492: INFO: PersistentVolume local-g8brb found and phase=Bound (132.481217ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-xs5v
STEP: Creating a pod to test exec-volume-test
Oct  1 09:02:46.891: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-xs5v" in namespace "volume-6386" to be "Succeeded or Failed"
Oct  1 09:02:47.023: INFO: Pod "exec-volume-test-preprovisionedpv-xs5v": Phase="Pending", Reason="", readiness=false. Elapsed: 132.788944ms
Oct  1 09:02:49.157: INFO: Pod "exec-volume-test-preprovisionedpv-xs5v": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.265957325s
STEP: Saw pod success
Oct  1 09:02:49.157: INFO: Pod "exec-volume-test-preprovisionedpv-xs5v" satisfied condition "Succeeded or Failed"
Oct  1 09:02:49.289: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod exec-volume-test-preprovisionedpv-xs5v container exec-container-preprovisionedpv-xs5v: <nil>
STEP: delete the pod
Oct  1 09:02:49.562: INFO: Waiting for pod exec-volume-test-preprovisionedpv-xs5v to disappear
Oct  1 09:02:49.694: INFO: Pod exec-volume-test-preprovisionedpv-xs5v no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-xs5v
Oct  1 09:02:49.694: INFO: Deleting pod "exec-volume-test-preprovisionedpv-xs5v" in namespace "volume-6386"
... skipping 17 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] volumes
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should allow exec of files on the volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:192
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir-link] [Testpattern: Pre-provisioned PV (default fs)] volumes should allow exec of files on the volume","total":-1,"completed":32,"skipped":210,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
... skipping 50 lines ...
Oct  1 09:01:38.681: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Oct  1 09:01:38.817: INFO: Waiting up to 5m0s for PersistentVolumeClaims [csi-hostpathdjkrv] to have phase Bound
Oct  1 09:01:38.950: INFO: PersistentVolumeClaim csi-hostpathdjkrv found but phase is Pending instead of Bound.
Oct  1 09:01:41.083: INFO: PersistentVolumeClaim csi-hostpathdjkrv found and phase=Bound (2.266767543s)
STEP: Creating pod pod-subpath-test-dynamicpv-whpk
STEP: Creating a pod to test atomic-volume-subpath
Oct  1 09:01:41.485: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-whpk" in namespace "provisioning-2546" to be "Succeeded or Failed"
Oct  1 09:01:41.618: INFO: Pod "pod-subpath-test-dynamicpv-whpk": Phase="Pending", Reason="", readiness=false. Elapsed: 133.482364ms
Oct  1 09:01:43.752: INFO: Pod "pod-subpath-test-dynamicpv-whpk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.267014786s
Oct  1 09:01:45.886: INFO: Pod "pod-subpath-test-dynamicpv-whpk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.400828495s
Oct  1 09:01:48.019: INFO: Pod "pod-subpath-test-dynamicpv-whpk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.53431005s
Oct  1 09:01:50.153: INFO: Pod "pod-subpath-test-dynamicpv-whpk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.668071008s
Oct  1 09:01:52.287: INFO: Pod "pod-subpath-test-dynamicpv-whpk": Phase="Running", Reason="", readiness=true. Elapsed: 10.801622363s
... skipping 4 lines ...
Oct  1 09:02:02.962: INFO: Pod "pod-subpath-test-dynamicpv-whpk": Phase="Running", Reason="", readiness=true. Elapsed: 21.476999903s
Oct  1 09:02:05.098: INFO: Pod "pod-subpath-test-dynamicpv-whpk": Phase="Running", Reason="", readiness=true. Elapsed: 23.612783425s
Oct  1 09:02:07.232: INFO: Pod "pod-subpath-test-dynamicpv-whpk": Phase="Running", Reason="", readiness=true. Elapsed: 25.746686951s
Oct  1 09:02:09.366: INFO: Pod "pod-subpath-test-dynamicpv-whpk": Phase="Running", Reason="", readiness=true. Elapsed: 27.880596639s
Oct  1 09:02:11.499: INFO: Pod "pod-subpath-test-dynamicpv-whpk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.014470543s
STEP: Saw pod success
Oct  1 09:02:11.500: INFO: Pod "pod-subpath-test-dynamicpv-whpk" satisfied condition "Succeeded or Failed"
Oct  1 09:02:11.634: INFO: Trying to get logs from node ip-172-20-41-255.ap-northeast-1.compute.internal pod pod-subpath-test-dynamicpv-whpk container test-container-subpath-dynamicpv-whpk: <nil>
STEP: delete the pod
Oct  1 09:02:11.910: INFO: Waiting for pod pod-subpath-test-dynamicpv-whpk to disappear
Oct  1 09:02:12.044: INFO: Pod pod-subpath-test-dynamicpv-whpk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-whpk
Oct  1 09:02:12.044: INFO: Deleting pod "pod-subpath-test-dynamicpv-whpk" in namespace "provisioning-2546"
... skipping 53 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_volumes.go:39
    [Testpattern: Dynamic PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support file as subpath [LinuxOnly]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:227
------------------------------
{"msg":"PASSED [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support file as subpath [LinuxOnly]","total":-1,"completed":36,"skipped":227,"failed":0}

S
------------------------------
[BeforeEach] [sig-apps] DisruptionController
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 20 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 in multiple volumes in the same pod [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating configMap with name configmap-test-volume-8d32c05c-c8b0-41d6-8928-d734dd33a672
STEP: Creating a pod to test consume configMaps
Oct  1 09:02:50.643: INFO: Waiting up to 5m0s for pod "pod-configmaps-9fbf21d6-3d3a-4032-acef-b5891e5a60a8" in namespace "configmap-6100" to be "Succeeded or Failed"
Oct  1 09:02:50.775: INFO: Pod "pod-configmaps-9fbf21d6-3d3a-4032-acef-b5891e5a60a8": Phase="Pending", Reason="", readiness=false. Elapsed: 131.847007ms
Oct  1 09:02:52.909: INFO: Pod "pod-configmaps-9fbf21d6-3d3a-4032-acef-b5891e5a60a8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.26579479s
STEP: Saw pod success
Oct  1 09:02:52.909: INFO: Pod "pod-configmaps-9fbf21d6-3d3a-4032-acef-b5891e5a60a8" satisfied condition "Succeeded or Failed"
Oct  1 09:02:53.041: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod pod-configmaps-9fbf21d6-3d3a-4032-acef-b5891e5a60a8 container configmap-volume-test: <nil>
STEP: delete the pod
Oct  1 09:02:53.311: INFO: Waiting for pod pod-configmaps-9fbf21d6-3d3a-4032-acef-b5891e5a60a8 to disappear
Oct  1 09:02:53.444: INFO: Pod pod-configmaps-9fbf21d6-3d3a-4032-acef-b5891e5a60a8 no longer exists
[AfterEach] [sig-storage] ConfigMap
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 09:02:53.444: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "configmap-6100" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] ConfigMap should be consumable in multiple volumes in the same pod [NodeConformance] [Conformance]","total":-1,"completed":24,"skipped":123,"failed":1,"failures":["[sig-cli] Kubectl Port forwarding With a server listening on localhost should support forwarding over websockets"]}
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:02:53.719: INFO: Only supported for providers [openstack] (not aws)
[AfterEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 56 lines ...
Oct  1 09:02:42.778: INFO: PersistentVolumeClaim pvc-f7gdv found but phase is Pending instead of Bound.
Oct  1 09:02:44.914: INFO: PersistentVolumeClaim pvc-f7gdv found and phase=Bound (2.270773548s)
Oct  1 09:02:44.914: INFO: Waiting up to 3m0s for PersistentVolume local-clspd to have phase Bound
Oct  1 09:02:45.050: INFO: PersistentVolume local-clspd found and phase=Bound (136.105349ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-6jr5
STEP: Creating a pod to test subpath
Oct  1 09:02:45.458: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-6jr5" in namespace "provisioning-9231" to be "Succeeded or Failed"
Oct  1 09:02:45.594: INFO: Pod "pod-subpath-test-preprovisionedpv-6jr5": Phase="Pending", Reason="", readiness=false. Elapsed: 135.173458ms
Oct  1 09:02:47.729: INFO: Pod "pod-subpath-test-preprovisionedpv-6jr5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.270936084s
Oct  1 09:02:49.870: INFO: Pod "pod-subpath-test-preprovisionedpv-6jr5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.411181291s
Oct  1 09:02:52.006: INFO: Pod "pod-subpath-test-preprovisionedpv-6jr5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.547597703s
STEP: Saw pod success
Oct  1 09:02:52.006: INFO: Pod "pod-subpath-test-preprovisionedpv-6jr5" satisfied condition "Succeeded or Failed"
Oct  1 09:02:52.141: INFO: Trying to get logs from node ip-172-20-60-245.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-6jr5 container test-container-volume-preprovisionedpv-6jr5: <nil>
STEP: delete the pod
Oct  1 09:02:52.418: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-6jr5 to disappear
Oct  1 09:02:52.553: INFO: Pod pod-subpath-test-preprovisionedpv-6jr5 no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-6jr5
Oct  1 09:02:52.553: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-6jr5" in namespace "provisioning-9231"
... skipping 19 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support existing directory
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:202
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir-link] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing directory","total":-1,"completed":36,"skipped":333,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:02:54.391: INFO: Only supported for providers [gce gke] (not aws)
... skipping 32 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 09:02:56.053: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "tables-1890" for this suite.

•
------------------------------
{"msg":"PASSED [sig-api-machinery] Servers with support for Table transformation should return chunks of table results for list calls","total":-1,"completed":37,"skipped":340,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:02:56.340: INFO: Only supported for node OS distro [gci ubuntu custom] (not debian)
[AfterEach] [Testpattern: Dynamic PV (block volmode)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 19 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 [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating configMap with name configmap-test-volume-d07421be-1ad9-46d0-82da-10a42a83a042
STEP: Creating a pod to test consume configMaps
Oct  1 09:02:54.676: INFO: Waiting up to 5m0s for pod "pod-configmaps-db04ecc9-b458-4bc1-9673-5711b71d69e0" in namespace "configmap-3445" to be "Succeeded or Failed"
Oct  1 09:02:54.808: INFO: Pod "pod-configmaps-db04ecc9-b458-4bc1-9673-5711b71d69e0": Phase="Pending", Reason="", readiness=false. Elapsed: 132.037338ms
Oct  1 09:02:56.940: INFO: Pod "pod-configmaps-db04ecc9-b458-4bc1-9673-5711b71d69e0": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.264449549s
STEP: Saw pod success
Oct  1 09:02:56.940: INFO: Pod "pod-configmaps-db04ecc9-b458-4bc1-9673-5711b71d69e0" satisfied condition "Succeeded or Failed"
Oct  1 09:02:57.072: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod pod-configmaps-db04ecc9-b458-4bc1-9673-5711b71d69e0 container agnhost-container: <nil>
STEP: delete the pod
Oct  1 09:02:57.343: INFO: Waiting for pod pod-configmaps-db04ecc9-b458-4bc1-9673-5711b71d69e0 to disappear
Oct  1 09:02:57.475: INFO: Pod pod-configmaps-db04ecc9-b458-4bc1-9673-5711b71d69e0 no longer exists
[AfterEach] [sig-storage] ConfigMap
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 09:02:57.475: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "configmap-3445" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume as non-root [NodeConformance] [Conformance]","total":-1,"completed":25,"skipped":128,"failed":1,"failures":["[sig-cli] Kubectl Port forwarding With a server listening on localhost should support forwarding over websockets"]}
[BeforeEach] [sig-windows] Hybrid cluster network
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/windows/framework.go:28
Oct  1 09:02:57.751: INFO: Only supported for node OS distro [windows] (not debian)
[AfterEach] [sig-windows] Hybrid cluster network
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 71 lines ...
Oct  1 09:01:50.005: INFO: Creating new exec pod
Oct  1 09:01:55.680: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-8514 exec execpod8hsfx -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80'
Oct  1 09:01:57.233: INFO: stderr: "+ nc -zv -t -w 2 nodeport-update-service 80\nConnection to nodeport-update-service 80 port [tcp/http] succeeded!\n"
Oct  1 09:01:57.233: INFO: stdout: ""
Oct  1 09:01:57.233: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-8514 exec execpod8hsfx -- /bin/sh -x -c nc -zv -t -w 2 100.66.191.51 80'
Oct  1 09:02:00.608: INFO: rc: 1
Oct  1 09:02:00.608: INFO: Service reachability failing with error: error running /tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-8514 exec execpod8hsfx -- /bin/sh -x -c nc -zv -t -w 2 100.66.191.51 80:
Command stdout:

stderr:
+ nc -zv -t -w 2 100.66.191.51 80
nc: connect to 100.66.191.51 port 80 (tcp) timed out: Operation in progress
command terminated with exit code 1

error:
exit status 1
Retrying...
Oct  1 09:02:01.608: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-8514 exec execpod8hsfx -- /bin/sh -x -c nc -zv -t -w 2 100.66.191.51 80'
Oct  1 09:02:04.995: INFO: rc: 1
Oct  1 09:02:04.995: INFO: Service reachability failing with error: error running /tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-8514 exec execpod8hsfx -- /bin/sh -x -c nc -zv -t -w 2 100.66.191.51 80:
Command stdout:

stderr:
+ nc -zv -t -w 2 100.66.191.51 80
nc: connect to 100.66.191.51 port 80 (tcp) timed out: Operation in progress
command terminated with exit code 1

error:
exit status 1
Retrying...
Oct  1 09:02:05.608: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-8514 exec execpod8hsfx -- /bin/sh -x -c nc -zv -t -w 2 100.66.191.51 80'
Oct  1 09:02:07.037: INFO: stderr: "+ nc -zv -t -w 2 100.66.191.51 80\nConnection to 100.66.191.51 80 port [tcp/http] succeeded!\n"
Oct  1 09:02:07.037: INFO: stdout: ""
Oct  1 09:02:07.037: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-8514 exec execpod8hsfx -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.245 30396'
... skipping 8 lines ...
Oct  1 09:02:11.272: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-8514 exec execpod8hsfx -- /bin/sh -x -c nc -zv -t -w 2 13.231.170.104 30396'
Oct  1 09:02:12.707: INFO: stderr: "+ nc -zv -t -w 2 13.231.170.104 30396\nConnection to 13.231.170.104 30396 port [tcp/30396] succeeded!\n"
Oct  1 09:02:12.707: INFO: stdout: ""
STEP: Updating NodePort service to listen TCP and UDP based requests over same Port
Oct  1 09:02:14.250: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-8514 exec execpod8hsfx -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80'
Oct  1 09:02:17.659: INFO: rc: 1
Oct  1 09:02:17.660: INFO: Service reachability failing with error: error running /tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-8514 exec execpod8hsfx -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80:
Command stdout:

stderr:
+ nc -zv -t -w 2 nodeport-update-service 80
nc: connect to nodeport-update-service port 80 (tcp) timed out: Operation in progress
command terminated with exit code 1

error:
exit status 1
Retrying...
Oct  1 09:02:18.660: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-8514 exec execpod8hsfx -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80'
Oct  1 09:02:22.072: INFO: rc: 1
Oct  1 09:02:22.072: INFO: Service reachability failing with error: error running /tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-8514 exec execpod8hsfx -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80:
Command stdout:

stderr:
+ nc -zv -t -w 2 nodeport-update-service 80
nc: connect to nodeport-update-service port 80 (tcp) timed out: Operation in progress
command terminated with exit code 1

error:
exit status 1
Retrying...
Oct  1 09:02:22.660: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-8514 exec execpod8hsfx -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80'
Oct  1 09:02:26.018: INFO: rc: 1
Oct  1 09:02:26.018: INFO: Service reachability failing with error: error running /tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-8514 exec execpod8hsfx -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80:
Command stdout:

stderr:
+ nc -zv -t -w 2 nodeport-update-service 80
nc: connect to nodeport-update-service port 80 (tcp) timed out: Operation in progress
command terminated with exit code 1

error:
exit status 1
Retrying...
Oct  1 09:02:26.660: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-8514 exec execpod8hsfx -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80'
Oct  1 09:02:30.048: INFO: rc: 1
Oct  1 09:02:30.048: INFO: Service reachability failing with error: error running /tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-8514 exec execpod8hsfx -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80:
Command stdout:

stderr:
+ nc -zv -t -w 2 nodeport-update-service 80
nc: connect to nodeport-update-service port 80 (tcp) timed out: Operation in progress
command terminated with exit code 1

error:
exit status 1
Retrying...
Oct  1 09:02:30.660: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-8514 exec execpod8hsfx -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80'
Oct  1 09:02:32.031: INFO: stderr: "+ nc -zv -t -w 2 nodeport-update-service 80\nConnection to nodeport-update-service 80 port [tcp/http] succeeded!\n"
Oct  1 09:02:32.031: INFO: stdout: ""
Oct  1 09:02:32.032: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-8514 exec execpod8hsfx -- /bin/sh -x -c nc -zv -t -w 2 100.66.191.51 80'
... skipping 43 lines ...
• [SLOW TEST:74.362 seconds]
[sig-network] Services
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
  should be able to update service type to NodePort listening on same port number but different protocols
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:1562
------------------------------
{"msg":"PASSED [sig-network] Services should be able to update service type to NodePort listening on same port number but different protocols","total":-1,"completed":13,"skipped":71,"failed":1,"failures":["[sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]"]}
[BeforeEach] [Testpattern: Pre-provisioned PV (ntfs)][sig-windows] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:03:00.002: INFO: Driver hostPathSymlink doesn't support PreprovisionedPV -- skipping
[AfterEach] [Testpattern: Pre-provisioned PV (ntfs)][sig-windows] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 39 lines ...
• [SLOW TEST:8.848 seconds]
[sig-apps] ReplicationController
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23
  should serve a basic image on each replica with a public image  [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","total":-1,"completed":19,"skipped":147,"failed":1,"failures":["[sig-network] Services should be able to up and down services"]}
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:03:00.056: INFO: Driver local doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (default fs)] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 42 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 [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating configMap with name configmap-test-volume-b162e1e8-0390-4078-becf-a687ed4c279b
STEP: Creating a pod to test consume configMaps
Oct  1 09:02:58.705: INFO: Waiting up to 5m0s for pod "pod-configmaps-d3f2d52a-80d8-49fc-bbe9-d7d267d2a67e" in namespace "configmap-3911" to be "Succeeded or Failed"
Oct  1 09:02:58.836: INFO: Pod "pod-configmaps-d3f2d52a-80d8-49fc-bbe9-d7d267d2a67e": Phase="Pending", Reason="", readiness=false. Elapsed: 131.833791ms
Oct  1 09:03:00.969: INFO: Pod "pod-configmaps-d3f2d52a-80d8-49fc-bbe9-d7d267d2a67e": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.264366411s
STEP: Saw pod success
Oct  1 09:03:00.969: INFO: Pod "pod-configmaps-d3f2d52a-80d8-49fc-bbe9-d7d267d2a67e" satisfied condition "Succeeded or Failed"
Oct  1 09:03:01.101: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod pod-configmaps-d3f2d52a-80d8-49fc-bbe9-d7d267d2a67e container agnhost-container: <nil>
STEP: delete the pod
Oct  1 09:03:01.373: INFO: Waiting for pod pod-configmaps-d3f2d52a-80d8-49fc-bbe9-d7d267d2a67e to disappear
Oct  1 09:03:01.504: INFO: Pod pod-configmaps-d3f2d52a-80d8-49fc-bbe9-d7d267d2a67e no longer exists
[AfterEach] [sig-storage] ConfigMap
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 09:03:01.504: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "configmap-3911" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume [NodeConformance] [Conformance]","total":-1,"completed":26,"skipped":131,"failed":1,"failures":["[sig-cli] Kubectl Port forwarding With a server listening on localhost should support forwarding over websockets"]}

SSS
------------------------------
{"msg":"PASSED [sig-apps] DisruptionController evictions: no PDB =\u003e should allow an eviction","total":-1,"completed":20,"skipped":148,"failed":1,"failures":["[sig-network] DNS should provide DNS for pods for Subdomain [Conformance]"]}
[BeforeEach] [sig-apps] ReplicaSet
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 09:02:53.333: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename replicaset
STEP: Waiting for a default service account to be provisioned in namespace
... skipping 41 lines ...
• [SLOW TEST:244.675 seconds]
[k8s.io] Probing container
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  should *not* be restarted with a /healthz http liveness probe [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [k8s.io] Probing container should *not* be restarted with a /healthz http liveness probe [NodeConformance] [Conformance]","total":-1,"completed":17,"skipped":170,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/fsgroupchangepolicy.go:81
Oct  1 09:03:02.386: INFO: Driver "csi-hostpath" does not support FsGroup - skipping
[AfterEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
... skipping 288 lines ...
Oct  1 09:02:58.732: INFO: PersistentVolumeClaim pvc-xwn6j found but phase is Pending instead of Bound.
Oct  1 09:03:00.865: INFO: PersistentVolumeClaim pvc-xwn6j found and phase=Bound (6.531124206s)
Oct  1 09:03:00.865: INFO: Waiting up to 3m0s for PersistentVolume local-djgcj to have phase Bound
Oct  1 09:03:00.998: INFO: PersistentVolume local-djgcj found and phase=Bound (132.465418ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-gphm
STEP: Creating a pod to test subpath
Oct  1 09:03:01.397: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-gphm" in namespace "provisioning-7768" to be "Succeeded or Failed"
Oct  1 09:03:01.529: INFO: Pod "pod-subpath-test-preprovisionedpv-gphm": Phase="Pending", Reason="", readiness=false. Elapsed: 132.489976ms
Oct  1 09:03:03.662: INFO: Pod "pod-subpath-test-preprovisionedpv-gphm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.26536545s
Oct  1 09:03:05.795: INFO: Pod "pod-subpath-test-preprovisionedpv-gphm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.398127301s
STEP: Saw pod success
Oct  1 09:03:05.795: INFO: Pod "pod-subpath-test-preprovisionedpv-gphm" satisfied condition "Succeeded or Failed"
Oct  1 09:03:05.927: INFO: Trying to get logs from node ip-172-20-60-245.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-gphm container test-container-subpath-preprovisionedpv-gphm: <nil>
STEP: delete the pod
Oct  1 09:03:06.201: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-gphm to disappear
Oct  1 09:03:06.333: INFO: Pod pod-subpath-test-preprovisionedpv-gphm no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-gphm
Oct  1 09:03:06.333: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-gphm" in namespace "provisioning-7768"
STEP: Creating pod pod-subpath-test-preprovisionedpv-gphm
STEP: Creating a pod to test subpath
Oct  1 09:03:06.599: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-gphm" in namespace "provisioning-7768" to be "Succeeded or Failed"
Oct  1 09:03:06.731: INFO: Pod "pod-subpath-test-preprovisionedpv-gphm": Phase="Pending", Reason="", readiness=false. Elapsed: 132.227976ms
Oct  1 09:03:08.864: INFO: Pod "pod-subpath-test-preprovisionedpv-gphm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.265000139s
STEP: Saw pod success
Oct  1 09:03:08.864: INFO: Pod "pod-subpath-test-preprovisionedpv-gphm" satisfied condition "Succeeded or Failed"
Oct  1 09:03:08.996: INFO: Trying to get logs from node ip-172-20-60-245.ap-northeast-1.compute.internal pod pod-subpath-test-preprovisionedpv-gphm container test-container-subpath-preprovisionedpv-gphm: <nil>
STEP: delete the pod
Oct  1 09:03:09.267: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-gphm to disappear
Oct  1 09:03:09.400: INFO: Pod pod-subpath-test-preprovisionedpv-gphm no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-gphm
Oct  1 09:03:09.400: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-gphm" in namespace "provisioning-7768"
... skipping 24 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should support existing directories when readOnly specified in the volumeSource
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:391
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: block] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing directories when readOnly specified in the volumeSource","total":-1,"completed":29,"skipped":274,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ntfs)][sig-windows] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:03:13.447: INFO: Driver csi-hostpath doesn't support InlineVolume -- skipping
... skipping 116 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Pre-provisioned PV (block volmode)] volumes
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:129
      should store data
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:151
------------------------------
{"msg":"PASSED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: block] [Testpattern: Pre-provisioned PV (block volmode)] volumes should store data","total":-1,"completed":24,"skipped":174,"failed":0}

SSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:03:15.063: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 34 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 09:03:16.237: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "kubectl-6244" for this suite.

•
------------------------------
{"msg":"PASSED [sig-cli] Kubectl client Kubectl version should check is all data is printed  [Conformance]","total":-1,"completed":25,"skipped":184,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ext3)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:03:16.532: INFO: Only supported for providers [openstack] (not aws)
... skipping 79 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:441

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:833
------------------------------
{"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a validating webhook should work [Conformance]","total":-1,"completed":14,"skipped":77,"failed":1,"failures":["[sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]"]}
[BeforeEach] [k8s.io] Security Context
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 09:03:08.534: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename security-context-test
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [k8s.io] Security Context
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/security_context.go:41
[It] should run the container with uid 65534 [LinuxOnly] [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
Oct  1 09:03:09.348: INFO: Waiting up to 5m0s for pod "busybox-user-65534-0dce4858-f20c-4f2b-a9f0-a3d62bd1a2c3" in namespace "security-context-test-738" to be "Succeeded or Failed"
Oct  1 09:03:09.483: INFO: Pod "busybox-user-65534-0dce4858-f20c-4f2b-a9f0-a3d62bd1a2c3": Phase="Pending", Reason="", readiness=false. Elapsed: 134.424488ms
Oct  1 09:03:11.618: INFO: Pod "busybox-user-65534-0dce4858-f20c-4f2b-a9f0-a3d62bd1a2c3": Phase="Pending", Reason="", readiness=false. Elapsed: 2.269479776s
Oct  1 09:03:13.753: INFO: Pod "busybox-user-65534-0dce4858-f20c-4f2b-a9f0-a3d62bd1a2c3": Phase="Pending", Reason="", readiness=false. Elapsed: 4.40467795s
Oct  1 09:03:15.888: INFO: Pod "busybox-user-65534-0dce4858-f20c-4f2b-a9f0-a3d62bd1a2c3": Phase="Running", Reason="", readiness=true. Elapsed: 6.539533094s
Oct  1 09:03:18.023: INFO: Pod "busybox-user-65534-0dce4858-f20c-4f2b-a9f0-a3d62bd1a2c3": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.674353096s
Oct  1 09:03:18.023: INFO: Pod "busybox-user-65534-0dce4858-f20c-4f2b-a9f0-a3d62bd1a2c3" satisfied condition "Succeeded or Failed"
[AfterEach] [k8s.io] Security Context
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Oct  1 09:03:18.023: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "security-context-test-738" for this suite.


... skipping 2 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  When creating a container with runAsUser
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/security_context.go:45
    should run the container with uid 65534 [LinuxOnly] [NodeConformance] [Conformance]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [k8s.io] Security Context When creating a container with runAsUser should run the container with uid 65534 [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":15,"skipped":77,"failed":1,"failures":["[sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]"]}
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:03:18.303: INFO: Only supported for providers [azure] (not aws)
[AfterEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] provisioning
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 11 lines ...
      Only supported for providers [azure] (not aws)

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/drivers/in_tree.go:1570
------------------------------
SSSSS
------------------------------
{"msg":"PASSED [sig-network] DNS should provide DNS for the cluster  [Conformance]","total":-1,"completed":32,"skipped":294,"failed":0}
[BeforeEach] [sig-apps] CronJob
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Oct  1 09:01:04.844: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename cronjob
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [sig-apps] CronJob
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/cronjob.go:58
[It] should delete failed finished jobs with limit of one job
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/cronjob.go:273
STEP: Creating an AllowConcurrent cronjob with custom history limit
STEP: Ensuring a finished job exists
STEP: Ensuring a finished job exists by listing jobs explicitly
STEP: Ensuring this job and its pods does not exist anymore
STEP: Ensuring there is 1 finished job by listing jobs explicitly
... skipping 4 lines ...
STEP: Destroying namespace "cronjob-6195" for this suite.


• [SLOW TEST:133.968 seconds]
[sig-apps] CronJob
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23
  should delete failed finished jobs with limit of one job
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/cronjob.go:273
------------------------------
{"msg":"PASSED [sig-apps] CronJob should delete failed finished jobs with limit of one job","total":-1,"completed":33,"skipped":294,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][sig-windows] volume-expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:03:18.835: INFO: Driver hostPath doesn't support DynamicPV -- skipping
... skipping 159 lines ...
Oct  1 09:02:06.616: INFO: Running '/tmp/kubectl4243106637/kubectl --server=https://api.e2e-3e65cd3106-93705.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-9936 exec verify-service-up-exec-pod-8htbm -- /bin/sh -x -c for i in $(seq 1 150); do wget -q -T 1 -O - http://100.71.204.57:80 2>&1 || true; echo; done'
Oct  1 09:03:07.252: INFO: stderr: "+ seq 1 150\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ echo\n+ wget -q -T 1 -O - http://100.71.204.57:80\n+ true\n+ echo\n"
Oct  1 09:03:07.253: INFO: stdout: "service-headless-toggled-jff4w\nwget: download timed out\n\nservice-headless-toggled-4zfql\nservice-headless-toggled-jff4w\nservice-headless-toggled-4zfql\nservice-headless-toggled-jff4w\nservice-headless-toggled-4zfql\nwget: download timed out\n\nservice-headless-toggled-jff4w\nwget: download timed out\n\nservice-headless-toggled-4zfql\nwget: download timed out\n\nwget: download timed out\n\nservice-headless-toggled-jff4w\nservice-headless-toggled-jff4w\nservice-headless-toggled-4zfql\nwget: download timed out\n\nwget: download timed out\n\nservice-headless-toggled-jff4w\nservice-headless-toggled-jff4w\nwget: download timed out\n\nservice-headless-toggled-4zfql\nservice-headless-toggled-4zfql\nwget: download timed out\n\nservice-headless-toggled-4zfql\nservice-headless-toggled-4zfql\nwget: download timed out\n\nservice-headless-toggled-jff4w\nwget: download timed out\n\nwget: download timed out\n\nservice-headless-toggled-jff4w\nservice-headless-toggled-4zfql\nservice-headless-toggled-jff4w\nwget: download timed out\n\nwget: download timed out\n\nservice-headless-toggled-jff4w\nwget: download timed out\n\nservice-headless-toggled-jff4w\nservice-headless-toggled-4zfql\nservice-headless-toggled-jff4w\nservice-headless-toggled-4zfql\nservice-headless-toggled-jff4w\nservice-headless-toggled-4zfql\nwget: download timed out\n\nservice-headless-toggled-4zfql\nservice-headless-toggled-jff4w\nservice-headless-toggled-4zfql\nservice-headless-toggled-4zfql\nservice-headless-toggled-4zfql\nservice-headless-toggled-4zfql\nservice-headless-toggled-4zfql\nwget: download timed out\n\nservice-headless-toggled-4zfql\nwget: download timed out\n\nservice-headless-toggled-4zfql\nwget: download timed out\n\nservice-headless-toggled-jff4w\nwget: download timed out\n\nwget: download timed out\n\nservice-headless-toggled-4zfql\nservice-headless-toggled-jff4w\nwget: download timed out\n\nwget: download timed out\n\nwget: download timed out\n\nservice-headless-toggled-jff4w\nwget: download timed out\n\nservice-headless-toggled-jff4w\nservice-headless-toggled-4zfql\nservice-headless-toggled-4zfql\nservice-headless-toggled-4zfql\nservice-headless-toggled-4zfql\nwget: download timed out\n\nservice-headless-toggled-4zfql\nservice-headless-toggled-4zfql\nservice-headless-toggled-4zfql\nservice-headless-toggled-4zfql\nwget: download timed out\n\nservice-headless-toggled-jff4w\nservice-headless-toggled-jff4w\nservice-headless-toggled-4zfql\nservice-headless-toggled-4zfql\nservice-headless-toggled-4zfql\nwget: download timed out\n\nwget: download timed out\n\nservice-headless-toggled-4zfql\nwget: download timed out\n\nwget: download timed out\n\nservice-headless-toggled-4zfql\nservice-headless-toggled-jff4w\nservice-headless-toggled-4zfql\nwget: download timed out\n\nservice-headless-toggled-4zfql\nwget: download timed out\n\nservice-headless-toggled-jff4w\nwget: download timed out\n\nservice-headless-toggled-4zfql\nwget: download timed out\n\nservice-headless-toggled-jff4w\nservice-headless-toggled-jff4w\nwget: download timed out\n\nwget: download timed out\n\nservice-headless-toggled-jff4w\nwget: download timed out\n\nservice-headless-toggled-4zfql\nwget: download timed out\n\nservice-headless-toggled-jff4w\nwget: download timed out\n\nwget: download timed out\n\nwget: download timed out\n\nwget: download timed out\n\nservice-headless-toggled-jff4w\nwget: download timed out\n\nservice-headless-toggled-jff4w\nwget: download timed out\n\nwget: download timed out\n\nwget: download timed out\n\nservice-headless-toggled-jff4w\nwget: download timed out\n\nservice-headless-toggled-jff4w\nwget: download timed out\n\nwget: download timed out\n\nservice-headless-toggled-jff4w\nservice-headless-toggled-4zfql\nservice-headless-toggled-4zfql\nservice-headless-toggled-jff4w\nservice-headless-toggled-4zfql\nwget: download timed out\n\nwget: download timed out\n\nservice-headless-toggled-jff4w\nservice-headless-toggled-jff4w\nservice-headless-toggled-4zfql\nservice-headless-toggled-4zfql\nservice-headless-toggled-jff4w\nservice-headless-toggled-4zfql\nwget: download timed out\n\nservice-headless-toggled-4zfql\nwget: download timed out\n\nservice-headless-toggled-4zfql\nwget: download timed out\n\nwget: download timed out\n\nservice-headless-toggled-jff4w\nservice-headless-toggled-jff4w\nservice-headless-toggled-jff4w\nservice-headless-toggled-4zfql\nwget: download timed out\n\nwget: download timed out\n\nservice-headless-toggled-4zfql\nservice-headless-toggled-4zfql\nservice-headless-toggled-jff4w\nwget: download timed out\n\n"
Oct  1 09:03:07.253: INFO: Unable to reach the following endpoints of service 100.71.204.57: map[service-headless-toggled-l5vwm:{}]
STEP: Deleting pod verify-service-up-host-exec-pod in namespace services-9936
STEP: Deleting pod verify-service-up-exec-pod-8htbm in namespace services-9936
Oct  1 09:03:12.537: FAIL: Unexpected error:
    <*errors.errorString | 0xc00157e070>: {
        s: "service verification failed for: 100.71.204.57\nexpected [service-headless-toggled-4zfql service-headless-toggled-jff4w service-headless-toggled-l5vwm]\nreceived [service-headless-toggled-4zfql service-headless-toggled-jff4w wget: download timed out]",
    }
    service verification failed for: 100.71.204.57
    expected [service-headless-toggled-4zfql service-headless-toggled-jff4w service-headless-toggled-l5vwm]
    received [service-headless-toggled-4zfql service-headless-toggled-jff4w wget: download timed out]
occurred

Full Stack Trace
k8s.io/kubernetes/test/e2e/network.glob..func24.36()
... skipping 312 lines ...
• Failure [355.217 seconds]
[sig-network] Services
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
  should implement service.kubernetes.io/headless [It]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:2587

  Oct  1 09:03:12.537: Unexpected error:
      <*errors.errorString | 0xc00157e070>: {
          s: "service verification failed for: 100.71.204.57\nexpected [service-headless-toggled-4zfql service-headless-toggled-jff4w service-headless-toggled-l5vwm]\nreceived [service-headless-toggled-4zfql service-headless-toggled-jff4w wget: download timed out]",
      }
      service verification failed for: 100.71.204.57
      expected [service-headless-toggled-4zfql service-headless-toggled-jff4w service-headless-toggled-l5vwm]
      received [service-headless-toggled-4zfql service-headless-toggled-jff4w wget: download timed out]
  occurred

  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:2612
------------------------------
{"msg":"FAILED [sig-network] Services should implement service.kubernetes.io/headless","total":-1,"completed":19,"skipped":148,"failed":1,"failures":["[sig-network] Services should implement service.kubernetes.io/headless"]}

SS
------------------------------
[BeforeEach] [sig-storage] PersistentVolumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 21 lines ...
Oct  1 09:02:59.909: INFO: PersistentVolumeClaim pvc-clgw9 found and phase=Bound (4.397641699s)
Oct  1 09:02:59.909: INFO: Waiting up to 3m0s for PersistentVolume nfs-j7p2g to have phase Bound
Oct  1 09:03:00.042: INFO: PersistentVolume nfs-j7p2g found and phase=Bound (132.582986ms)
STEP: Checking pod has write access to PersistentVolume
Oct  1 09:03:00.308: INFO: Creating nfs test pod
Oct  1 09:03:00.441: INFO: Pod should terminate with exitcode 0 (success)
Oct  1 09:03:00.441: INFO: Waiting up to 5m0s for pod "pvc-tester-fx224" in namespace "pv-924" to be "Succeeded or Failed"
Oct  1 09:03:00.573: INFO: Pod "pvc-tester-fx224": Phase="Pending", Reason="", readiness=false. Elapsed: 132.251231ms
Oct  1 09:03:02.706: INFO: Pod "pvc-tester-fx224": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.26529209s
STEP: Saw pod success
Oct  1 09:03:02.706: INFO: Pod "pvc-tester-fx224" satisfied condition "Succeeded or Failed"
Oct  1 09:03:02.707: INFO: Pod pvc-tester-fx224 succeeded 
Oct  1 09:03:02.707: INFO: Deleting pod "pvc-tester-fx224" in namespace "pv-924"
Oct  1 09:03:02.852: INFO: Wait up to 5m0s for pod "pvc-tester-fx224" to be fully deleted
STEP: Deleting the PVC to invoke the reclaim policy.
Oct  1 09:03:02.989: INFO: Deleting PVC pvc-clgw9 to trigger reclamation of PV nfs-j7p2g
Oct  1 09:03:02.989: INFO: Deleting PersistentVolumeClaim "pvc-clgw9"
... skipping 23 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes.go:122
    with Single PV - PVC pairs
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes.go:155
      create a PV and a pre-bound PVC: test write access
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes.go:196
------------------------------
{"msg":"PASSED [sig-storage] PersistentVolumes NFS with Single PV - PVC pairs create a PV and a pre-bound PVC: test write access","total":-1,"completed":33,"skipped":211,"failed":0}
[BeforeEach] [Testpattern: Pre-provisioned PV (ntfs)][sig-windows] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:130
Oct  1 09:03:20.354: INFO: Driver local doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Pre-provisioned PV (ntfs)][sig-windows] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 36 lines ...
• [SLOW TEST:41.875 seconds]
[sig-apps] Job
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23
  should delete a job [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-apps] Job should delete a job [Conformance]","total":-1,"completed":25,"skipped":188,"failed":0}

SSSSSSSS
------------------------------
[BeforeEach] [sig-network] Networking
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 55 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 via environment variable [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
STEP: Creating configMap configmap-8443/configmap-test-53f97f6b-fc35-4a6f-8f93-541fa7981a99
STEP: Creating a pod to test consume configMaps
Oct  1 09:03:14.394: INFO: Waiting up to 5m0s for pod "pod-configmaps-56acb7cc-6c7e-40c8-9211-c4202398d02c" in namespace "configmap-8443" to be "Succeeded or Failed"
Oct  1 09:03:14.527: INFO: Pod "pod-configmaps-56acb7cc-6c7e-40c8-9211-c4202398d02c": Phase="Pending", Reason="", readiness=false. Elapsed: 133.077109ms
Oct  1 09:03:16.659: INFO: Pod "pod-configmaps-56acb7cc-6c7e-40c8-9211-c4202398d02c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.265728328s
Oct  1 09:03:18.793: INFO: Pod "pod-configmaps-56acb7cc-6c7e-40c8-9211-c4202398d02c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.398884695s
Oct  1 09:03:20.926: INFO: Pod "pod-configmaps-56acb7cc-6c7e-40c8-9211-c4202398d02c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.531889478s
Oct  1 09:03:23.059: INFO: Pod "pod-configmaps-56acb7cc-6c7e-40c8-9211-c4202398d02c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.664881749s
STEP: Saw pod success
Oct  1 09:03:23.059: INFO: Pod "pod-configmaps-56acb7cc-6c7e-40c8-9211-c4202398d02c" satisfied condition "Succeeded or Failed"
Oct  1 09:03:23.191: INFO: Trying to get logs from node ip-172-20-37-175.ap-northeast-1.compute.internal pod pod-configmaps-56acb7cc-6c7e-40c8-9211-c4202398d02c container env-test: <nil>
STEP: delete the pod
Oct  1 09:03:23.462: INFO: Waiting for pod pod-configmaps-56acb7cc-6c7e-40c8-9211-c4202398d02c to disappear
Oct  1 09:03:23.594: INFO: Pod pod-configmaps-56acb7cc-6c7e-40c8-9211-c4202398d02c no longer exists
[AfterEach] [sig-node] ConfigMap
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 26 lines ...
Oct  1 08:53:17.061: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:17.193: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:17.347: INFO: Unable to read jessie_hosts@dns-querier-1.dns-test-service.dns-3404.svc.cluster.local from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:17.479: INFO: Unable to read jessie_hosts@dns-querier-1 from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:17.611: INFO: Unable to read jessie_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:17.744: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:17.744: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_hosts@dns-querier-1.dns-test-service.dns-3404.svc.cluster.local jessie_hosts@dns-querier-1 jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:53:23.141: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:23.274: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:23.406: INFO: Unable to read jessie_hosts@dns-querier-1.dns-test-service.dns-3404.svc.cluster.local from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:23.542: INFO: Unable to read jessie_hosts@dns-querier-1 from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:23.675: INFO: Unable to read jessie_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:23.808: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:23.808: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_hosts@dns-querier-1.dns-test-service.dns-3404.svc.cluster.local jessie_hosts@dns-querier-1 jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:53:28.154: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:28.289: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:28.553: INFO: Unable to read jessie_hosts@dns-querier-1 from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:28.685: INFO: Unable to read jessie_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:28.818: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:28.818: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_hosts@dns-querier-1 jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:53:33.141: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:33.274: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:33.541: INFO: Unable to read jessie_hosts@dns-querier-1 from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:33.673: INFO: Unable to read jessie_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:33.805: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:33.805: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_hosts@dns-querier-1 jessie_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:53:38.141: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:38.275: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:38.813: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:38.813: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:53:43.141: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:43.273: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:43.803: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:43.803: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:53:48.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:48.280: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:48.818: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:48.818: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:53:53.151: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:53.286: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:53.816: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:53.816: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:53:58.143: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:58.277: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:58.812: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:53:58.812: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:54:03.148: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:03.282: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:03.829: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:03.829: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:54:08.143: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:08.281: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:08.831: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:08.831: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:54:13.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:13.274: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:13.809: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:13.809: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:54:18.141: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:18.274: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:18.804: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:18.805: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:54:23.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:23.275: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:23.805: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:23.805: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:54:28.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:28.274: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:28.805: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:28.805: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:54:33.146: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:33.278: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:33.809: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:33.809: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:54:38.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:38.822: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:38.822: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:54:43.141: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:43.804: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:43.804: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:54:48.141: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:48.812: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:48.812: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:54:53.141: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:53.805: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:53.805: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:54:58.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:58.810: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:54:58.810: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord jessie_tcp@PodARecord]

Oct  1 08:55:03.149: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:55:03.812: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:55:08.141: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:55:08.804: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:55:13.141: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:55:13.803: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:55:18.141: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:55:18.803: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:55:23.141: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:55:23.802: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:55:28.146: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:55:28.810: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:55:33.149: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:55:33.816: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:55:38.141: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:55:38.803: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:55:43.168: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:55:43.834: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:55:48.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:55:48.803: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:55:53.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:55:53.804: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:55:58.144: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:55:58.806: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:56:03.141: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:56:03.803: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:56:08.141: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:56:08.802: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:56:13.143: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:56:13.819: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:56:18.141: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:56:18.803: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:56:23.150: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:56:23.811: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:56:28.150: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:56:28.819: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:56:33.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:56:33.805: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:56:38.165: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:56:38.830: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:56:43.143: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:56:43.804: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:56:48.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:56:48.805: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:56:53.144: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:56:53.817: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:56:58.141: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:56:58.818: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:57:03.149: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:57:03.815: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:57:08.147: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:57:08.810: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:57:13.141: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:57:13.808: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:57:18.141: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:57:18.803: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:57:23.178: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:57:23.847: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:57:28.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:57:28.804: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:57:33.144: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:57:33.807: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:57:38.145: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:57:38.811: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:57:43.141: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:57:43.812: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:57:48.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:57:48.806: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:57:53.144: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:57:53.810: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:57:58.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:57:58.804: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:58:03.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:58:03.805: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:58:08.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:58:08.810: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:58:13.145: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:58:13.816: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:58:18.201: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:58:18.870: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:58:23.141: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:58:23.805: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:58:28.149: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:58:28.817: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:58:33.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:58:33.805: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:58:38.149: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:58:38.813: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:58:43.145: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:58:43.810: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:58:48.145: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:58:48.809: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:58:53.141: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:58:53.804: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:58:58.148: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:58:58.813: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:59:03.145: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:59:03.818: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:59:08.150: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:59:08.821: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:59:13.150: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:59:13.817: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:59:18.178: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:59:18.875: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:59:23.143: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:59:23.821: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:59:28.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:59:28.807: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:59:33.153: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:59:33.831: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:59:38.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:59:38.813: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:59:43.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:59:43.804: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:59:48.149: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:59:48.818: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:59:53.141: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:59:53.805: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 08:59:58.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 08:59:58.807: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:00:03.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:00:03.807: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:00:08.146: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:00:08.818: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:00:13.150: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:00:13.823: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:00:18.146: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:00:18.812: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:00:23.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:00:23.819: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:00:28.143: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:00:28.810: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:00:33.148: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:00:33.815: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:00:38.143: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:00:38.810: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:00:43.143: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:00:43.807: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:00:48.146: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:00:48.812: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:00:53.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:00:53.817: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:00:58.143: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:00:58.809: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:01:03.144: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:01:03.808: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:01:08.143: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:01:08.809: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:01:13.143: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:01:13.807: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:01:18.143: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:01:18.810: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:01:23.144: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:01:23.811: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:01:28.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:01:28.807: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:01:33.183: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:01:33.848: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:01:38.157: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:01:38.865: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:01:43.143: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:01:43.808: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:01:48.143: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:01:48.809: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:01:53.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:01:53.806: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:01:58.143: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:01:58.812: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:02:03.142: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource (get pods dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b)
Oct  1 09:02:03.810: INFO: Lookups using dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b failed for: [wheezy_udp@PodARecord]

Oct  1 09:02:08.143: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3404/dns-test-405236eb-f9a9-4dcd-b0df-e11cbe51e48b: the server could not find the requested resource