This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-07-30 11:45
Elapsed45m15s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 126 lines ...
I0730 11:46:23.226516    4018 up.go:43] Cleaning up any leaked resources from previous cluster
I0730 11:46:23.226561    4018 dumplogs.go:38] /logs/artifacts/93cb88a6-f12b-11eb-9ae3-22193179c208/kops toolbox dump --name e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0730 11:46:23.240155    4036 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0730 11:46:23.240326    4036 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io" not found
W0730 11:46:23.726773    4018 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0730 11:46:23.726830    4018 down.go:48] /logs/artifacts/93cb88a6-f12b-11eb-9ae3-22193179c208/kops delete cluster --name e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --yes
I0730 11:46:23.739780    4047 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0730 11:46:23.739855    4047 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io" not found
I0730 11:46:24.236629    4018 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/07/30 11:46:24 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
I0730 11:46:24.244328    4018 http.go:37] curl https://ip.jsb.workers.dev
I0730 11:46:24.344980    4018 up.go:144] /logs/artifacts/93cb88a6-f12b-11eb-9ae3-22193179c208/kops create cluster --name e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.20.9 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=309956199498/RHEL-7.9_HVM_GA-20200917-x86_64-0-Hourly2-GP2 --channel=alpha --networking=kopeio --container-runtime=containerd --admin-access 35.239.121.220/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-2a --master-size c5.large
I0730 11:46:24.358565    4057 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0730 11:46:24.358738    4057 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0730 11:46:24.401481    4057 create_cluster.go:724] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0730 11:46:24.871469    4057 new_cluster.go:962]  Cloud Provider ID = aws
... skipping 48 lines ...

I0730 11:46:42.234439    4018 up.go:181] /logs/artifacts/93cb88a6-f12b-11eb-9ae3-22193179c208/kops validate cluster --name e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0730 11:46:42.248274    4077 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0730 11:46:42.248353    4077 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io

W0730 11:46:43.899804    4077 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:46:53.929988    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:47:03.963005    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:47:14.000496    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:47:24.038649    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:47:34.068971    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:47:44.113222    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:47:54.150531    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:48:04.179019    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:48:14.210559    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:48:24.240001    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:48:34.276244    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:48:44.307065    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:48:54.436803    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:49:04.466132    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:49:14.497610    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:49:24.544478    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
W0730 11:49:34.575432    4077 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:49:44.623514    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:49:54.680048    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:50:04.724717    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:50:14.755420    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:50:24.797009    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:50:34.830009    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:50:44.862705    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:50:54.918191    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:51:04.954986    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:51:14.990290    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:51:25.018949    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:51:35.051035    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:51:45.095952    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0730 11:51:55.131657    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 10 lines ...
Node	ip-172-20-45-65.ap-southeast-2.compute.internal	node "ip-172-20-45-65.ap-southeast-2.compute.internal" is not ready
Pod	kube-system/coredns-5489b75945-89kxv		system-cluster-critical pod "coredns-5489b75945-89kxv" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-w6v74	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-w6v74" is pending
Pod	kube-system/kopeio-networking-agent-dsjvk	system-node-critical pod "kopeio-networking-agent-dsjvk" is pending
Pod	kube-system/kopeio-networking-agent-rbsqx	system-node-critical pod "kopeio-networking-agent-rbsqx" is pending

Validation Failed
W0730 11:52:09.236223    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5489b75945-89kxv		system-cluster-critical pod "coredns-5489b75945-89kxv" is not ready (coredns)
Pod	kube-system/coredns-5489b75945-h9vdc		system-cluster-critical pod "coredns-5489b75945-h9vdc" is pending
Pod	kube-system/kopeio-networking-agent-n64pp	system-node-critical pod "kopeio-networking-agent-n64pp" is pending

Validation Failed
W0730 11:52:21.744524    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 21 lines ...
ip-172-20-60-194.ap-southeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-proxy-ip-172-20-45-65.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-45-65.ap-southeast-2.compute.internal" is pending

Validation Failed
W0730 11:52:46.780510    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 6 lines ...
ip-172-20-60-194.ap-southeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-proxy-ip-172-20-35-124.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-35-124.ap-southeast-2.compute.internal" is pending

Validation Failed
W0730 11:52:59.376107    4077 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 1144 lines ...
STEP: Destroying namespace "node-problem-detector-7467" for this suite.


S [SKIPPING] in Spec Setup (BeforeEach) [1.725 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 34 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 11:55:33.777: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-limits-on-node-8929" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] Volume limits should verify that all nodes have volume limits","total":-1,"completed":1,"skipped":3,"failed":0}

SSSSSSSS
------------------------------
[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
Jul 30 11:55:34.202: INFO: Driver local doesn't support InlineVolume -- skipping
... skipping 49 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 44 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 11:55:34.296: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "events-7005" for this suite.

•
------------------------------
{"msg":"PASSED [sig-api-machinery] Events should delete a collection of events [Conformance]","total":-1,"completed":1,"skipped":2,"failed":0}

SSSS
------------------------------
[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
Jul 30 11:55:34.891: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 123 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 11:55:36.280: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "tables-3937" 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":1,"skipped":19,"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
Jul 30 11:55:36.668: INFO: Driver local 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 222 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 11:55:36.378: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "events-9844" 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":1,"skipped":10,"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
Jul 30 11:55:36.957: INFO: Driver emptydir 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 160 lines ...
Jul 30 11:55:32.760: INFO: No PodSecurityPolicies found; 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 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
Jul 30 11:55:33.333: INFO: Waiting up to 5m0s for pod "alpine-nnp-false-31bd51b7-4710-4cc6-afd9-67f42eb79513" in namespace "security-context-test-5457" to be "Succeeded or Failed"
Jul 30 11:55:33.526: INFO: Pod "alpine-nnp-false-31bd51b7-4710-4cc6-afd9-67f42eb79513": Phase="Pending", Reason="", readiness=false. Elapsed: 191.976929ms
Jul 30 11:55:35.715: INFO: Pod "alpine-nnp-false-31bd51b7-4710-4cc6-afd9-67f42eb79513": Phase="Pending", Reason="", readiness=false. Elapsed: 2.381049181s
Jul 30 11:55:37.904: INFO: Pod "alpine-nnp-false-31bd51b7-4710-4cc6-afd9-67f42eb79513": Phase="Pending", Reason="", readiness=false. Elapsed: 4.570757535s
Jul 30 11:55:40.094: INFO: Pod "alpine-nnp-false-31bd51b7-4710-4cc6-afd9-67f42eb79513": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.760024334s
Jul 30 11:55:40.094: INFO: Pod "alpine-nnp-false-31bd51b7-4710-4cc6-afd9-67f42eb79513" 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
Jul 30 11:55:40.301: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "security-context-test-5457" for this suite.


... skipping 22 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 11:55:41.082: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "disruption-7215" for this suite.

•
------------------------------
{"msg":"PASSED [sig-apps] DisruptionController evictions: maxUnavailable allow single eviction, percentage =\u003e should allow an eviction","total":-1,"completed":2,"skipped":45,"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
Jul 30 11:55:41.541: INFO: Driver emptydir doesn't support PreprovisionedPV -- skipping
[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 112 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
Jul 30 11:55:32.665: INFO: In-tree plugin kubernetes.io/host-path is not migrated, not validating any metrics
Jul 30 11:55:32.856: INFO: Creating resource for inline volume
STEP: Creating pod pod-subpath-test-inlinevolume-8w99
STEP: Creating a pod to test subpath
Jul 30 11:55:33.050: INFO: Waiting up to 5m0s for pod "pod-subpath-test-inlinevolume-8w99" in namespace "provisioning-4938" to be "Succeeded or Failed"
Jul 30 11:55:33.241: INFO: Pod "pod-subpath-test-inlinevolume-8w99": Phase="Pending", Reason="", readiness=false. Elapsed: 190.849136ms
Jul 30 11:55:35.432: INFO: Pod "pod-subpath-test-inlinevolume-8w99": Phase="Pending", Reason="", readiness=false. Elapsed: 2.381827081s
Jul 30 11:55:37.623: INFO: Pod "pod-subpath-test-inlinevolume-8w99": Phase="Pending", Reason="", readiness=false. Elapsed: 4.573548363s
Jul 30 11:55:39.814: INFO: Pod "pod-subpath-test-inlinevolume-8w99": Phase="Pending", Reason="", readiness=false. Elapsed: 6.764518191s
Jul 30 11:55:42.006: INFO: Pod "pod-subpath-test-inlinevolume-8w99": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.956046106s
STEP: Saw pod success
Jul 30 11:55:42.006: INFO: Pod "pod-subpath-test-inlinevolume-8w99" satisfied condition "Succeeded or Failed"
Jul 30 11:55:42.197: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod pod-subpath-test-inlinevolume-8w99 container test-container-volume-inlinevolume-8w99: <nil>
STEP: delete the pod
Jul 30 11:55:42.593: INFO: Waiting for pod pod-subpath-test-inlinevolume-8w99 to disappear
Jul 30 11:55:42.785: INFO: Pod pod-subpath-test-inlinevolume-8w99 no longer exists
STEP: Deleting pod pod-subpath-test-inlinevolume-8w99
Jul 30 11:55:42.785: INFO: Deleting pod "pod-subpath-test-inlinevolume-8w99" in namespace "provisioning-4938"
... 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":1,"skipped":4,"failed":0}

SS
------------------------------
[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
... skipping 2 lines ...
Jul 30 11:55:32.765: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should be consumable from pods in volume with defaultMode 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-891dfb6c-89c5-4be6-ab68-3328c242ca8d
STEP: Creating a pod to test consume secrets
Jul 30 11:55:33.523: INFO: Waiting up to 5m0s for pod "pod-secrets-463b38fe-f73f-4146-9ca8-89b36bc30371" in namespace "secrets-2954" to be "Succeeded or Failed"
Jul 30 11:55:33.749: INFO: Pod "pod-secrets-463b38fe-f73f-4146-9ca8-89b36bc30371": Phase="Pending", Reason="", readiness=false. Elapsed: 226.639777ms
Jul 30 11:55:35.952: INFO: Pod "pod-secrets-463b38fe-f73f-4146-9ca8-89b36bc30371": Phase="Pending", Reason="", readiness=false. Elapsed: 2.429349238s
Jul 30 11:55:38.141: INFO: Pod "pod-secrets-463b38fe-f73f-4146-9ca8-89b36bc30371": Phase="Pending", Reason="", readiness=false. Elapsed: 4.618306793s
Jul 30 11:55:40.330: INFO: Pod "pod-secrets-463b38fe-f73f-4146-9ca8-89b36bc30371": Phase="Pending", Reason="", readiness=false. Elapsed: 6.807223455s
Jul 30 11:55:42.519: INFO: Pod "pod-secrets-463b38fe-f73f-4146-9ca8-89b36bc30371": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.99629286s
STEP: Saw pod success
Jul 30 11:55:42.519: INFO: Pod "pod-secrets-463b38fe-f73f-4146-9ca8-89b36bc30371" satisfied condition "Succeeded or Failed"
Jul 30 11:55:42.708: INFO: Trying to get logs from node ip-172-20-33-146.ap-southeast-2.compute.internal pod pod-secrets-463b38fe-f73f-4146-9ca8-89b36bc30371 container secret-volume-test: <nil>
STEP: delete the pod
Jul 30 11:55:43.105: INFO: Waiting for pod pod-secrets-463b38fe-f73f-4146-9ca8-89b36bc30371 to disappear
Jul 30 11:55:43.294: INFO: Pod pod-secrets-463b38fe-f73f-4146-9ca8-89b36bc30371 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:11.875 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 defaultMode 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 defaultMode set [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":1,"skipped":2,"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
Jul 30 11:55:43.875: INFO: Only supported for providers [azure] (not aws)
... skipping 96 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 11:55:43.724: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "endpointslice-3028" for this suite.

•
------------------------------
{"msg":"PASSED [sig-network] EndpointSlice should create and delete Endpoints and EndpointSlices for a Service with a selector specified","total":-1,"completed":3,"skipped":65,"failed":0}
[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
Jul 30 11:55:44.110: INFO: Only supported for providers [vsphere] (not aws)
[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

... skipping 90 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 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 projected-configmap-test-volume-e8bdf914-6f67-4cef-9db7-04ce06bd8e7a
STEP: Creating a pod to test consume configMaps
Jul 30 11:55:45.239: INFO: Waiting up to 5m0s for pod "pod-projected-configmaps-40b3846a-7b67-4552-81d0-c8e806614430" in namespace "projected-9566" to be "Succeeded or Failed"
Jul 30 11:55:45.428: INFO: Pod "pod-projected-configmaps-40b3846a-7b67-4552-81d0-c8e806614430": Phase="Pending", Reason="", readiness=false. Elapsed: 188.918332ms
Jul 30 11:55:47.617: INFO: Pod "pod-projected-configmaps-40b3846a-7b67-4552-81d0-c8e806614430": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.378766799s
STEP: Saw pod success
Jul 30 11:55:47.618: INFO: Pod "pod-projected-configmaps-40b3846a-7b67-4552-81d0-c8e806614430" satisfied condition "Succeeded or Failed"
Jul 30 11:55:47.806: INFO: Trying to get logs from node ip-172-20-45-65.ap-southeast-2.compute.internal pod pod-projected-configmaps-40b3846a-7b67-4552-81d0-c8e806614430 container agnhost-container: <nil>
STEP: delete the pod
Jul 30 11:55:48.195: INFO: Waiting for pod pod-projected-configmaps-40b3846a-7b67-4552-81d0-c8e806614430 to disappear
Jul 30 11:55:48.388: INFO: Pod pod-projected-configmaps-40b3846a-7b67-4552-81d0-c8e806614430 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
Jul 30 11:55:48.388: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "projected-9566" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] Projected configMap should be consumable from pods in volume as non-root [NodeConformance] [Conformance]","total":-1,"completed":2,"skipped":9,"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
Jul 30 11:55:48.777: INFO: Only supported for providers [azure] (not aws)
[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 18 lines ...
Jul 30 11:55:44.931: 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
Jul 30 11:55:46.079: INFO: Waiting up to 5m0s for pod "pod-f551fb5d-0bc4-4035-b1e9-2b9ea77f3daa" in namespace "emptydir-5188" to be "Succeeded or Failed"
Jul 30 11:55:46.270: INFO: Pod "pod-f551fb5d-0bc4-4035-b1e9-2b9ea77f3daa": Phase="Pending", Reason="", readiness=false. Elapsed: 190.722084ms
Jul 30 11:55:48.460: INFO: Pod "pod-f551fb5d-0bc4-4035-b1e9-2b9ea77f3daa": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.38163448s
STEP: Saw pod success
Jul 30 11:55:48.461: INFO: Pod "pod-f551fb5d-0bc4-4035-b1e9-2b9ea77f3daa" satisfied condition "Succeeded or Failed"
Jul 30 11:55:48.652: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod pod-f551fb5d-0bc4-4035-b1e9-2b9ea77f3daa container test-container: <nil>
STEP: delete the pod
Jul 30 11:55:49.038: INFO: Waiting for pod pod-f551fb5d-0bc4-4035-b1e9-2b9ea77f3daa to disappear
Jul 30 11:55:49.229: INFO: Pod pod-f551fb5d-0bc4-4035-b1e9-2b9ea77f3daa 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
Jul 30 11:55:49.229: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "emptydir-5188" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] EmptyDir volumes should support (non-root,0666,default) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":2,"skipped":10,"failed":0}
[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
Jul 30 11:55:49.621: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename services
STEP: Waiting for a default service account to be provisioned in namespace
... skipping 20 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
Jul 30 11:55:34.349: INFO: Waiting up to 5m0s for pod "downwardapi-volume-f515ae9a-3a9a-47e3-919d-545e165ac5ec" in namespace "downward-api-5642" to be "Succeeded or Failed"
Jul 30 11:55:34.539: INFO: Pod "downwardapi-volume-f515ae9a-3a9a-47e3-919d-545e165ac5ec": Phase="Pending", Reason="", readiness=false. Elapsed: 189.775577ms
Jul 30 11:55:36.729: INFO: Pod "downwardapi-volume-f515ae9a-3a9a-47e3-919d-545e165ac5ec": Phase="Pending", Reason="", readiness=false. Elapsed: 2.380370034s
Jul 30 11:55:38.919: INFO: Pod "downwardapi-volume-f515ae9a-3a9a-47e3-919d-545e165ac5ec": Phase="Pending", Reason="", readiness=false. Elapsed: 4.570541975s
Jul 30 11:55:41.109: INFO: Pod "downwardapi-volume-f515ae9a-3a9a-47e3-919d-545e165ac5ec": Phase="Pending", Reason="", readiness=false. Elapsed: 6.760602411s
Jul 30 11:55:43.299: INFO: Pod "downwardapi-volume-f515ae9a-3a9a-47e3-919d-545e165ac5ec": Phase="Pending", Reason="", readiness=false. Elapsed: 8.950712162s
Jul 30 11:55:45.490: INFO: Pod "downwardapi-volume-f515ae9a-3a9a-47e3-919d-545e165ac5ec": Phase="Pending", Reason="", readiness=false. Elapsed: 11.1410274s
Jul 30 11:55:47.691: INFO: Pod "downwardapi-volume-f515ae9a-3a9a-47e3-919d-545e165ac5ec": Phase="Pending", Reason="", readiness=false. Elapsed: 13.342026775s
Jul 30 11:55:49.881: INFO: Pod "downwardapi-volume-f515ae9a-3a9a-47e3-919d-545e165ac5ec": Phase="Pending", Reason="", readiness=false. Elapsed: 15.532209448s
Jul 30 11:55:52.071: INFO: Pod "downwardapi-volume-f515ae9a-3a9a-47e3-919d-545e165ac5ec": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.722699226s
STEP: Saw pod success
Jul 30 11:55:52.072: INFO: Pod "downwardapi-volume-f515ae9a-3a9a-47e3-919d-545e165ac5ec" satisfied condition "Succeeded or Failed"
Jul 30 11:55:52.261: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod downwardapi-volume-f515ae9a-3a9a-47e3-919d-545e165ac5ec container client-container: <nil>
STEP: delete the pod
Jul 30 11:55:52.647: INFO: Waiting for pod downwardapi-volume-f515ae9a-3a9a-47e3-919d-545e165ac5ec to disappear
Jul 30 11:55:52.837: INFO: Pod downwardapi-volume-f515ae9a-3a9a-47e3-919d-545e165ac5ec 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:21.372 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 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
------------------------------
{"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":1,"skipped":9,"failed":0}

SS
------------------------------
[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
... skipping 32 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
  should support configurable pod DNS nameservers [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
S
------------------------------
{"msg":"PASSED [sig-network] DNS should support configurable pod DNS nameservers [Conformance]","total":-1,"completed":1,"skipped":10,"failed":0}

SSSS
------------------------------
[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
Jul 30 11:55:53.434: INFO: Driver local doesn't support InlineVolume -- skipping
... skipping 63 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/framework.go:23
  Kubectl expose
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:1229
    should create services for rc  [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 expose should create services for rc  [Conformance]","total":-1,"completed":4,"skipped":71,"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
Jul 30 11:55:56.553: 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 42 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 11:55:57.649: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "ingressclass-2798" for this suite.

•
------------------------------
{"msg":"PASSED [sig-network] IngressClass API  should support creating IngressClass API operations [Conformance]","total":-1,"completed":2,"skipped":15,"failed":0}

SS
------------------------------
[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
Jul 30 11:55:59.565: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "custom-resource-definition-9423" 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":3,"skipped":17,"failed":0}

S
------------------------------
[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
Jul 30 11:55:59.961: INFO: Driver local doesn't support InlineVolume -- skipping
... skipping 69 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
Jul 30 11:55:57.713: INFO: Waiting up to 5m0s for pod "pod-39ce9605-e931-4276-8679-9bb61c16600d" in namespace "emptydir-1449" to be "Succeeded or Failed"
Jul 30 11:55:57.902: INFO: Pod "pod-39ce9605-e931-4276-8679-9bb61c16600d": Phase="Pending", Reason="", readiness=false. Elapsed: 188.475806ms
Jul 30 11:56:00.091: INFO: Pod "pod-39ce9605-e931-4276-8679-9bb61c16600d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.377075532s
STEP: Saw pod success
Jul 30 11:56:00.091: INFO: Pod "pod-39ce9605-e931-4276-8679-9bb61c16600d" satisfied condition "Succeeded or Failed"
Jul 30 11:56:00.279: INFO: Trying to get logs from node ip-172-20-35-124.ap-southeast-2.compute.internal pod pod-39ce9605-e931-4276-8679-9bb61c16600d container test-container: <nil>
STEP: delete the pod
Jul 30 11:56:00.664: INFO: Waiting for pod pod-39ce9605-e931-4276-8679-9bb61c16600d to disappear
Jul 30 11:56:00.853: INFO: Pod pod-39ce9605-e931-4276-8679-9bb61c16600d 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
Jul 30 11:56:00.853: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "emptydir-1449" for this suite.

•
------------------------------
{"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":5,"skipped":77,"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
Jul 30 11:56:01.240: INFO: Driver emptydir doesn't support ntfs -- 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 94 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/framework.go:23
  Kubectl copy
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:1351
    should copy a file from a running Pod
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:1368
------------------------------
{"msg":"PASSED [sig-cli] Kubectl client Kubectl copy should copy a file from a running Pod","total":-1,"completed":1,"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
Jul 30 11:56:01.844: INFO: Driver csi-hostpath 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 119 lines ...
• [SLOW TEST:28.764 seconds]
[sig-network] Services
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
  should serve a basic endpoint from pods  [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 serve a basic endpoint from pods  [Conformance]","total":-1,"completed":1,"skipped":3,"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
Jul 30 11:56:02.428: 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 107 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 writable rootfs when readOnlyRootFilesystem=false [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
Jul 30 11:56:01.139: INFO: Waiting up to 5m0s for pod "busybox-readonly-false-4db7baef-079b-4240-a4ff-9060e209fcd1" in namespace "security-context-test-6331" to be "Succeeded or Failed"
Jul 30 11:56:01.329: INFO: Pod "busybox-readonly-false-4db7baef-079b-4240-a4ff-9060e209fcd1": Phase="Pending", Reason="", readiness=false. Elapsed: 189.851641ms
Jul 30 11:56:03.519: INFO: Pod "busybox-readonly-false-4db7baef-079b-4240-a4ff-9060e209fcd1": Phase="Pending", Reason="", readiness=false. Elapsed: 2.380222852s
Jul 30 11:56:05.709: INFO: Pod "busybox-readonly-false-4db7baef-079b-4240-a4ff-9060e209fcd1": Phase="Pending", Reason="", readiness=false. Elapsed: 4.570436991s
Jul 30 11:56:07.899: INFO: Pod "busybox-readonly-false-4db7baef-079b-4240-a4ff-9060e209fcd1": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.7603848s
Jul 30 11:56:07.899: INFO: Pod "busybox-readonly-false-4db7baef-079b-4240-a4ff-9060e209fcd1" 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
Jul 30 11:56:07.899: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "security-context-test-6331" 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 writable rootfs when readOnlyRootFilesystem=false [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 pod with readOnlyRootFilesystem should run the container with writable rootfs when readOnlyRootFilesystem=false [NodeConformance] [Conformance]","total":-1,"completed":4,"skipped":25,"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
Jul 30 11:56:08.290: 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 147 lines ...
[It] should support existing directory
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:202
Jul 30 11:55:34.847: INFO: In-tree plugin kubernetes.io/host-path is not migrated, not validating any metrics
Jul 30 11:55:35.225: INFO: Creating resource for inline volume
STEP: Creating pod pod-subpath-test-inlinevolume-5g7h
STEP: Creating a pod to test subpath
Jul 30 11:55:35.417: INFO: Waiting up to 5m0s for pod "pod-subpath-test-inlinevolume-5g7h" in namespace "provisioning-2077" to be "Succeeded or Failed"
Jul 30 11:55:35.606: INFO: Pod "pod-subpath-test-inlinevolume-5g7h": Phase="Pending", Reason="", readiness=false. Elapsed: 189.533501ms
Jul 30 11:55:37.797: INFO: Pod "pod-subpath-test-inlinevolume-5g7h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.37993501s
Jul 30 11:55:39.987: INFO: Pod "pod-subpath-test-inlinevolume-5g7h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.569894425s
Jul 30 11:55:42.177: INFO: Pod "pod-subpath-test-inlinevolume-5g7h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.759924129s
Jul 30 11:55:44.367: INFO: Pod "pod-subpath-test-inlinevolume-5g7h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.950179153s
Jul 30 11:55:46.558: INFO: Pod "pod-subpath-test-inlinevolume-5g7h": Phase="Pending", Reason="", readiness=false. Elapsed: 11.140613918s
... skipping 6 lines ...
Jul 30 11:56:01.890: INFO: Pod "pod-subpath-test-inlinevolume-5g7h": Phase="Pending", Reason="", readiness=false. Elapsed: 26.472885222s
Jul 30 11:56:04.080: INFO: Pod "pod-subpath-test-inlinevolume-5g7h": Phase="Pending", Reason="", readiness=false. Elapsed: 28.662926877s
Jul 30 11:56:06.270: INFO: Pod "pod-subpath-test-inlinevolume-5g7h": Phase="Pending", Reason="", readiness=false. Elapsed: 30.852953662s
Jul 30 11:56:08.460: INFO: Pod "pod-subpath-test-inlinevolume-5g7h": Phase="Pending", Reason="", readiness=false. Elapsed: 33.043093959s
Jul 30 11:56:10.650: INFO: Pod "pod-subpath-test-inlinevolume-5g7h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 35.233073205s
STEP: Saw pod success
Jul 30 11:56:10.650: INFO: Pod "pod-subpath-test-inlinevolume-5g7h" satisfied condition "Succeeded or Failed"
Jul 30 11:56:10.843: INFO: Trying to get logs from node ip-172-20-35-124.ap-southeast-2.compute.internal pod pod-subpath-test-inlinevolume-5g7h container test-container-volume-inlinevolume-5g7h: <nil>
STEP: delete the pod
Jul 30 11:56:11.235: INFO: Waiting for pod pod-subpath-test-inlinevolume-5g7h to disappear
Jul 30 11:56:11.425: INFO: Pod pod-subpath-test-inlinevolume-5g7h no longer exists
STEP: Deleting pod pod-subpath-test-inlinevolume-5g7h
Jul 30 11:56:11.425: INFO: Deleting pod "pod-subpath-test-inlinevolume-5g7h" in namespace "provisioning-2077"
... 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 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: hostPath] [Testpattern: Inline-volume (default fs)] subPath should support existing directory","total":-1,"completed":1,"skipped":13,"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
Jul 30 11:56:12.196: INFO: Only supported for providers [openstack] (not aws)
[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 40 lines ...
Jul 30 11:56:04.052: INFO: PersistentVolumeClaim pvc-v677g found but phase is Pending instead of Bound.
Jul 30 11:56:06.245: INFO: PersistentVolumeClaim pvc-v677g found and phase=Bound (11.142065415s)
Jul 30 11:56:06.245: INFO: Waiting up to 3m0s for PersistentVolume local-hhmp8 to have phase Bound
Jul 30 11:56:06.434: INFO: PersistentVolume local-hhmp8 found and phase=Bound (189.44345ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-g28b
STEP: Creating a pod to test subpath
Jul 30 11:56:07.004: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-g28b" in namespace "provisioning-7478" to be "Succeeded or Failed"
Jul 30 11:56:07.194: INFO: Pod "pod-subpath-test-preprovisionedpv-g28b": Phase="Pending", Reason="", readiness=false. Elapsed: 189.601695ms
Jul 30 11:56:09.384: INFO: Pod "pod-subpath-test-preprovisionedpv-g28b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.379672959s
Jul 30 11:56:11.574: INFO: Pod "pod-subpath-test-preprovisionedpv-g28b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.569793599s
STEP: Saw pod success
Jul 30 11:56:11.574: INFO: Pod "pod-subpath-test-preprovisionedpv-g28b" satisfied condition "Succeeded or Failed"
Jul 30 11:56:11.764: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod pod-subpath-test-preprovisionedpv-g28b container test-container-volume-preprovisionedpv-g28b: <nil>
STEP: delete the pod
Jul 30 11:56:12.150: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-g28b to disappear
Jul 30 11:56:12.340: INFO: Pod pod-subpath-test-preprovisionedpv-g28b no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-g28b
Jul 30 11:56:12.340: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-g28b" in namespace "provisioning-7478"
... 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] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing directory","total":-1,"completed":1,"skipped":13,"failed":0}

SS
------------------------------
[BeforeEach] [k8s.io] Pods
  /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 ...
Jul 30 11:55:34.314: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [k8s.io] Pods
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/pods.go:187
[It] should contain environment variables for services [NodeConformance] [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
Jul 30 11:55:53.831: INFO: Waiting up to 5m0s for pod "client-envvars-f34a8494-b5ff-4b0e-b90e-d623b3d4c1a0" in namespace "pods-2881" to be "Succeeded or Failed"
Jul 30 11:55:54.019: INFO: Pod "client-envvars-f34a8494-b5ff-4b0e-b90e-d623b3d4c1a0": Phase="Pending", Reason="", readiness=false. Elapsed: 187.853044ms
Jul 30 11:55:56.208: INFO: Pod "client-envvars-f34a8494-b5ff-4b0e-b90e-d623b3d4c1a0": Phase="Pending", Reason="", readiness=false. Elapsed: 2.377148537s
Jul 30 11:55:58.397: INFO: Pod "client-envvars-f34a8494-b5ff-4b0e-b90e-d623b3d4c1a0": Phase="Pending", Reason="", readiness=false. Elapsed: 4.565438087s
Jul 30 11:56:00.585: INFO: Pod "client-envvars-f34a8494-b5ff-4b0e-b90e-d623b3d4c1a0": Phase="Pending", Reason="", readiness=false. Elapsed: 6.753659348s
Jul 30 11:56:02.773: INFO: Pod "client-envvars-f34a8494-b5ff-4b0e-b90e-d623b3d4c1a0": Phase="Pending", Reason="", readiness=false. Elapsed: 8.941678156s
Jul 30 11:56:04.963: INFO: Pod "client-envvars-f34a8494-b5ff-4b0e-b90e-d623b3d4c1a0": Phase="Pending", Reason="", readiness=false. Elapsed: 11.131963009s
Jul 30 11:56:07.152: INFO: Pod "client-envvars-f34a8494-b5ff-4b0e-b90e-d623b3d4c1a0": Phase="Pending", Reason="", readiness=false. Elapsed: 13.320385168s
Jul 30 11:56:09.340: INFO: Pod "client-envvars-f34a8494-b5ff-4b0e-b90e-d623b3d4c1a0": Phase="Pending", Reason="", readiness=false. Elapsed: 15.508893016s
Jul 30 11:56:11.528: INFO: Pod "client-envvars-f34a8494-b5ff-4b0e-b90e-d623b3d4c1a0": Phase="Pending", Reason="", readiness=false. Elapsed: 17.69728314s
Jul 30 11:56:13.717: INFO: Pod "client-envvars-f34a8494-b5ff-4b0e-b90e-d623b3d4c1a0": Phase="Pending", Reason="", readiness=false. Elapsed: 19.88561984s
Jul 30 11:56:15.908: INFO: Pod "client-envvars-f34a8494-b5ff-4b0e-b90e-d623b3d4c1a0": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.076765476s
STEP: Saw pod success
Jul 30 11:56:15.908: INFO: Pod "client-envvars-f34a8494-b5ff-4b0e-b90e-d623b3d4c1a0" satisfied condition "Succeeded or Failed"
Jul 30 11:56:16.096: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod client-envvars-f34a8494-b5ff-4b0e-b90e-d623b3d4c1a0 container env3cont: <nil>
STEP: delete the pod
Jul 30 11:56:16.481: INFO: Waiting for pod client-envvars-f34a8494-b5ff-4b0e-b90e-d623b3d4c1a0 to disappear
Jul 30 11:56:16.669: INFO: Pod client-envvars-f34a8494-b5ff-4b0e-b90e-d623b3d4c1a0 no longer exists
[AfterEach] [k8s.io] Pods
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 4 lines ...
• [SLOW TEST:45.168 seconds]
[k8s.io] Pods
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  should contain environment variables for services [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 contain environment variables for services [NodeConformance] [Conformance]","total":-1,"completed":1,"skipped":17,"failed":0}

S
------------------------------
[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: block] One pod requesting one prebound PVC should be able to mount volume and read from pod1","total":-1,"completed":2,"skipped":18,"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
Jul 30 11:56:20.019: 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 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 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-link] Two pods mounting a local volume at the same time should be able to write from pod1 and read from pod2","total":-1,"completed":3,"skipped":10,"failed":0}

SSSS
------------------------------
[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
Jul 30 11:56:21.619: INFO: Driver supports dynamic provisioning, skipping InlineVolume pattern
... skipping 49 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: dir-link]
  /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 72 lines ...
Jul 30 11:56:20.035: 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 volume subpath [sig-storage] [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 volume subpath
Jul 30 11:56:21.180: INFO: Waiting up to 5m0s for pod "var-expansion-0a710646-5383-41e5-b6c6-24af7819195d" in namespace "var-expansion-3971" to be "Succeeded or Failed"
Jul 30 11:56:21.370: INFO: Pod "var-expansion-0a710646-5383-41e5-b6c6-24af7819195d": Phase="Pending", Reason="", readiness=false. Elapsed: 189.908571ms
Jul 30 11:56:23.560: INFO: Pod "var-expansion-0a710646-5383-41e5-b6c6-24af7819195d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.380541481s
STEP: Saw pod success
Jul 30 11:56:23.560: INFO: Pod "var-expansion-0a710646-5383-41e5-b6c6-24af7819195d" satisfied condition "Succeeded or Failed"
Jul 30 11:56:23.751: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod var-expansion-0a710646-5383-41e5-b6c6-24af7819195d container dapi-container: <nil>
STEP: delete the pod
Jul 30 11:56:24.137: INFO: Waiting for pod var-expansion-0a710646-5383-41e5-b6c6-24af7819195d to disappear
Jul 30 11:56:24.327: INFO: Pod var-expansion-0a710646-5383-41e5-b6c6-24af7819195d 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
Jul 30 11:56:24.327: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "var-expansion-3971" for this suite.

•
------------------------------
{"msg":"PASSED [k8s.io] Variable Expansion should allow substituting values in a volume subpath [sig-storage] [Conformance]","total":-1,"completed":3,"skipped":20,"failed":0}

SSS
------------------------------
[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 88 lines ...
• [SLOW TEST:15.698 seconds]
[sig-apps] Deployment
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23
  should run the lifecycle of a Deployment [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-apps] Deployment should run the lifecycle of a Deployment [Conformance]","total":-1,"completed":2,"skipped":15,"failed":0}

SS
------------------------------
[BeforeEach] [sig-storage] PVC 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 31 lines ...
• [SLOW TEST:58.402 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 "immediate" deletion of a PVC that is not in active use by a pod
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/pvc_protection.go:112
------------------------------
{"msg":"PASSED [sig-storage] PVC Protection Verify \"immediate\" deletion of a PVC that is not in active use by a pod","total":-1,"completed":1,"skipped":0,"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
Jul 30 11:56:30.376: INFO: Driver local doesn't support InlineVolume -- skipping
... skipping 69 lines ...
Jul 30 11:56:04.924: INFO: PersistentVolumeClaim pvc-ndh78 found but phase is Pending instead of Bound.
Jul 30 11:56:07.114: INFO: PersistentVolumeClaim pvc-ndh78 found and phase=Bound (6.764762274s)
Jul 30 11:56:07.114: INFO: Waiting up to 3m0s for PersistentVolume local-q5hqh to have phase Bound
Jul 30 11:56:07.304: INFO: PersistentVolume local-q5hqh found and phase=Bound (190.064737ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-9sr7
STEP: Creating a pod to test subpath
Jul 30 11:56:07.876: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-9sr7" in namespace "provisioning-5930" to be "Succeeded or Failed"
Jul 30 11:56:08.067: INFO: Pod "pod-subpath-test-preprovisionedpv-9sr7": Phase="Pending", Reason="", readiness=false. Elapsed: 190.799806ms
Jul 30 11:56:10.258: INFO: Pod "pod-subpath-test-preprovisionedpv-9sr7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.381534389s
Jul 30 11:56:12.453: INFO: Pod "pod-subpath-test-preprovisionedpv-9sr7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.576378421s
Jul 30 11:56:14.643: INFO: Pod "pod-subpath-test-preprovisionedpv-9sr7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.766958133s
STEP: Saw pod success
Jul 30 11:56:14.643: INFO: Pod "pod-subpath-test-preprovisionedpv-9sr7" satisfied condition "Succeeded or Failed"
Jul 30 11:56:14.833: INFO: Trying to get logs from node ip-172-20-45-65.ap-southeast-2.compute.internal pod pod-subpath-test-preprovisionedpv-9sr7 container test-container-subpath-preprovisionedpv-9sr7: <nil>
STEP: delete the pod
Jul 30 11:56:15.227: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-9sr7 to disappear
Jul 30 11:56:15.417: INFO: Pod pod-subpath-test-preprovisionedpv-9sr7 no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-9sr7
Jul 30 11:56:15.417: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-9sr7" in namespace "provisioning-5930"
... skipping 13 lines ...
Jul 30 11:56:19.846: INFO: ExecWithOptions {Command:[nsenter --mount=/rootfs/proc/1/ns/mnt -- sh -c rm -r /tmp/local-driver-45c303d7-4df5-4791-820b-77dd2a7837a7] Namespace:provisioning-5930 PodName:hostexec-ip-172-20-45-65.ap-southeast-2.compute.internal-x74cg ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:true Quiet:false}
Jul 30 11:56:19.846: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:56:21.061: INFO: exec ip-172-20-45-65.ap-southeast-2.compute.internal: command:   rm -r /tmp/local-driver-45c303d7-4df5-4791-820b-77dd2a7837a7
Jul 30 11:56:21.061: INFO: exec ip-172-20-45-65.ap-southeast-2.compute.internal: stdout:    ""
Jul 30 11:56:21.061: INFO: exec ip-172-20-45-65.ap-southeast-2.compute.internal: stderr:    "rm: cannot remove '/tmp/local-driver-45c303d7-4df5-4791-820b-77dd2a7837a7': Device or resource busy\n"
Jul 30 11:56:21.061: INFO: exec ip-172-20-45-65.ap-southeast-2.compute.internal: exit code: 0
Jul 30 11:56:21.062: FAIL: Unexpected error:
    <exec.CodeExitError>: {
        Err: {
            s: "command terminated with exit code 1",
        },
        Code: 1,
    }
... skipping 281 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] [It]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:376

      Jul 30 11:56:21.062: Unexpected error:
          <exec.CodeExitError>: {
              Err: {
                  s: "command terminated with exit code 1",
              },
              Code: 1,
          }
          command terminated with exit code 1
      occurred

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/local.go:170
------------------------------
{"msg":"FAILED [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":0,"skipped":2,"failed":1,"failures":["[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]"]}

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 17 lines ...
• [SLOW TEST:6.877 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":4,"skipped":23,"failed":0}

SSSS
------------------------------
[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
Jul 30 11:56:31.631: INFO: Driver local doesn't support InlineVolume -- skipping
... skipping 283 lines ...
Jul 30 11:56:24.215: INFO: ExecWithOptions {Command:[nsenter --mount=/rootfs/proc/1/ns/mnt -- sh -c rm /tmp/local-volume-test-5c003804-86fa-47a7-a288-a367437c8add && umount /tmp/local-volume-test-5c003804-86fa-47a7-a288-a367437c8add-backend && rm -r /tmp/local-volume-test-5c003804-86fa-47a7-a288-a367437c8add-backend] Namespace:persistent-local-volumes-test-1821 PodName:hostexec-ip-172-20-33-146.ap-southeast-2.compute.internal-jxlqc ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:true Quiet:false}
Jul 30 11:56:24.215: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:56:25.434: INFO: exec ip-172-20-33-146.ap-southeast-2.compute.internal: command:   rm /tmp/local-volume-test-5c003804-86fa-47a7-a288-a367437c8add && umount /tmp/local-volume-test-5c003804-86fa-47a7-a288-a367437c8add-backend && rm -r /tmp/local-volume-test-5c003804-86fa-47a7-a288-a367437c8add-backend
Jul 30 11:56:25.434: INFO: exec ip-172-20-33-146.ap-southeast-2.compute.internal: stdout:    ""
Jul 30 11:56:25.434: INFO: exec ip-172-20-33-146.ap-southeast-2.compute.internal: stderr:    "rm: cannot remove '/tmp/local-volume-test-5c003804-86fa-47a7-a288-a367437c8add-backend': Device or resource busy\n"
Jul 30 11:56:25.434: INFO: exec ip-172-20-33-146.ap-southeast-2.compute.internal: exit code: 0
Jul 30 11:56:25.434: FAIL: Unexpected error:
    <exec.CodeExitError>: {
        Err: {
            s: "command terminated with exit code 1",
        },
        Code: 1,
    }
... skipping 34 lines ...
Jul 30 11:56:25.626: INFO: At 2021-07-30 11:56:16 +0000 UTC - event for pod-92e567af-fe3f-4aee-a698-071df11df942: {default-scheduler } Scheduled: Successfully assigned persistent-local-volumes-test-1821/pod-92e567af-fe3f-4aee-a698-071df11df942 to ip-172-20-33-146.ap-southeast-2.compute.internal
Jul 30 11:56:25.626: INFO: At 2021-07-30 11:56:17 +0000 UTC - event for pod-92e567af-fe3f-4aee-a698-071df11df942: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} Started: Started container write-pod
Jul 30 11:56:25.626: INFO: At 2021-07-30 11:56:17 +0000 UTC - event for pod-92e567af-fe3f-4aee-a698-071df11df942: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} Created: Created container write-pod
Jul 30 11:56:25.626: INFO: At 2021-07-30 11:56:17 +0000 UTC - event for pod-92e567af-fe3f-4aee-a698-071df11df942: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} Pulled: Container image "docker.io/library/busybox:1.29" already present on machine
Jul 30 11:56:25.626: INFO: At 2021-07-30 11:56:23 +0000 UTC - event for pod-92e567af-fe3f-4aee-a698-071df11df942: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} Killing: Stopping container write-pod
Jul 30 11:56:25.626: INFO: At 2021-07-30 11:56:23 +0000 UTC - event for pod-b02f3d38-46e8-4fa6-b288-50eb893455e0: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} Killing: Stopping container write-pod
Jul 30 11:56:25.626: INFO: At 2021-07-30 11:56:24 +0000 UTC - event for pod-b02f3d38-46e8-4fa6-b288-50eb893455e0: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} FailedKillPod: error killing pod: failed to "KillPodSandbox" for "33a48c04-7e95-4943-adbc-c4302f93324c" with KillPodSandboxError: "rpc error: code = Unknown desc = failed to remove network namespace for sandbox \"b797dc1af70fe98999c5917b95117ee77b8a49b97d429231d7f9388771a42d72\": failed to remove netns: unlinkat /run/netns/cni-47f7389a-169a-7a14-1d58-da25fa9b69e4: device or resource busy"
Jul 30 11:56:25.817: INFO: POD                                                              NODE                                              PHASE      GRACE  CONDITIONS
Jul 30 11:56:25.817: INFO: hostexec-ip-172-20-33-146.ap-southeast-2.compute.internal-jxlqc  ip-172-20-33-146.ap-southeast-2.compute.internal  Running           [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2021-07-30 11:55:38 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2021-07-30 11:55:53 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2021-07-30 11:55:53 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2021-07-30 11:55:38 +0000 UTC  }]
Jul 30 11:56:25.817: INFO: pod-92e567af-fe3f-4aee-a698-071df11df942                         ip-172-20-33-146.ap-southeast-2.compute.internal  Succeeded  30s    [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2021-07-30 11:56:16 +0000 UTC PodCompleted } {Ready False 0001-01-01 00:00:00 +0000 UTC 2021-07-30 11:56:25 +0000 UTC PodCompleted } {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2021-07-30 11:56:25 +0000 UTC PodCompleted } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2021-07-30 11:56:16 +0000 UTC  }]
Jul 30 11:56:25.817: INFO: pod-b02f3d38-46e8-4fa6-b288-50eb893455e0                         ip-172-20-33-146.ap-southeast-2.compute.internal  Running    30s    [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2021-07-30 11:55:57 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2021-07-30 11:56:12 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2021-07-30 11:56:12 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2021-07-30 11:55:57 +0000 UTC  }]
Jul 30 11:56:25.817: INFO: 
Jul 30 11:56:26.015: INFO: 
... skipping 240 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 [AfterEach]
    /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

      Jul 30 11:56:25.434: Unexpected error:
          <exec.CodeExitError>: {
              Err: {
                  s: "command terminated with exit code 1",
              },
              Code: 1,
          }
          command terminated with exit code 1
      occurred

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/local.go:271
------------------------------
{"msg":"FAILED [sig-storage] PersistentVolumes-local  [Volume type: dir-link-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":1,"skipped":33,"failed":1,"failures":["[sig-storage] PersistentVolumes-local  [Volume type: dir-link-bindmounted] Two pods mounting a local volume at the same time should be able to write from pod1 and read from pod2"]}
[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
Jul 30 11:56:33.558: INFO: Driver local 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 114 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":1,"skipped":8,"failed":0}

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
Jul 30 11:56:35.987: INFO: Only supported for providers [gce gke] (not aws)
... skipping 157 lines ...
Jul 30 11:56:20.653: INFO: PersistentVolumeClaim pvc-ckltq found but phase is Pending instead of Bound.
Jul 30 11:56:22.843: INFO: PersistentVolumeClaim pvc-ckltq found and phase=Bound (13.333914743s)
Jul 30 11:56:22.844: INFO: Waiting up to 3m0s for PersistentVolume local-lwtkm to have phase Bound
Jul 30 11:56:23.033: INFO: PersistentVolume local-lwtkm found and phase=Bound (189.707255ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-czls
STEP: Creating a pod to test subpath
Jul 30 11:56:23.604: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-czls" in namespace "provisioning-3983" to be "Succeeded or Failed"
Jul 30 11:56:23.795: INFO: Pod "pod-subpath-test-preprovisionedpv-czls": Phase="Pending", Reason="", readiness=false. Elapsed: 190.158284ms
Jul 30 11:56:25.988: INFO: Pod "pod-subpath-test-preprovisionedpv-czls": Phase="Pending", Reason="", readiness=false. Elapsed: 2.38340059s
Jul 30 11:56:28.178: INFO: Pod "pod-subpath-test-preprovisionedpv-czls": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.573783514s
STEP: Saw pod success
Jul 30 11:56:28.178: INFO: Pod "pod-subpath-test-preprovisionedpv-czls" satisfied condition "Succeeded or Failed"
Jul 30 11:56:28.368: INFO: Trying to get logs from node ip-172-20-45-65.ap-southeast-2.compute.internal pod pod-subpath-test-preprovisionedpv-czls container test-container-subpath-preprovisionedpv-czls: <nil>
STEP: delete the pod
Jul 30 11:56:28.758: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-czls to disappear
Jul 30 11:56:28.948: INFO: Pod pod-subpath-test-preprovisionedpv-czls no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-czls
Jul 30 11:56:28.949: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-czls" in namespace "provisioning-3983"
STEP: Creating pod pod-subpath-test-preprovisionedpv-czls
STEP: Creating a pod to test subpath
Jul 30 11:56:29.330: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-czls" in namespace "provisioning-3983" to be "Succeeded or Failed"
Jul 30 11:56:29.520: INFO: Pod "pod-subpath-test-preprovisionedpv-czls": Phase="Pending", Reason="", readiness=false. Elapsed: 189.917453ms
Jul 30 11:56:31.710: INFO: Pod "pod-subpath-test-preprovisionedpv-czls": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.380257883s
STEP: Saw pod success
Jul 30 11:56:31.710: INFO: Pod "pod-subpath-test-preprovisionedpv-czls" satisfied condition "Succeeded or Failed"
Jul 30 11:56:31.900: INFO: Trying to get logs from node ip-172-20-45-65.ap-southeast-2.compute.internal pod pod-subpath-test-preprovisionedpv-czls container test-container-subpath-preprovisionedpv-czls: <nil>
STEP: delete the pod
Jul 30 11:56:32.285: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-czls to disappear
Jul 30 11:56:32.475: INFO: Pod pod-subpath-test-preprovisionedpv-czls no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-czls
Jul 30 11:56:32.475: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-czls" in namespace "provisioning-3983"
... 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":2,"skipped":24,"failed":0}

SSSS
------------------------------
[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
Jul 30 11:56:36.312: INFO: Driver emptydir doesn't support DynamicPV -- skipping
... skipping 104 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-link-bindmounted] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]","total":-1,"completed":6,"skipped":80,"failed":0}

SSSSSSS
------------------------------
[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
Jul 30 11:56:38.862: INFO: Driver hostPath doesn't support PreprovisionedPV -- skipping
... skipping 26 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
Jul 30 11:56:32.956: INFO: In-tree plugin kubernetes.io/empty-dir is not migrated, not validating any metrics
Jul 30 11:56:32.957: INFO: Creating resource for inline volume
STEP: Creating pod pod-subpath-test-inlinevolume-24p8
STEP: Creating a pod to test subpath
Jul 30 11:56:33.148: INFO: Waiting up to 5m0s for pod "pod-subpath-test-inlinevolume-24p8" in namespace "provisioning-1537" to be "Succeeded or Failed"
Jul 30 11:56:33.338: INFO: Pod "pod-subpath-test-inlinevolume-24p8": Phase="Pending", Reason="", readiness=false. Elapsed: 189.935936ms
Jul 30 11:56:35.529: INFO: Pod "pod-subpath-test-inlinevolume-24p8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.380190888s
Jul 30 11:56:37.719: INFO: Pod "pod-subpath-test-inlinevolume-24p8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.570722031s
STEP: Saw pod success
Jul 30 11:56:37.719: INFO: Pod "pod-subpath-test-inlinevolume-24p8" satisfied condition "Succeeded or Failed"
Jul 30 11:56:37.911: INFO: Trying to get logs from node ip-172-20-33-146.ap-southeast-2.compute.internal pod pod-subpath-test-inlinevolume-24p8 container test-container-volume-inlinevolume-24p8: <nil>
STEP: delete the pod
Jul 30 11:56:38.298: INFO: Waiting for pod pod-subpath-test-inlinevolume-24p8 to disappear
Jul 30 11:56:38.487: INFO: Pod pod-subpath-test-inlinevolume-24p8 no longer exists
STEP: Deleting pod pod-subpath-test-inlinevolume-24p8
Jul 30 11:56:38.488: INFO: Deleting pod "pod-subpath-test-inlinevolume-24p8" in namespace "provisioning-1537"
... 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":4,"failed":1,"failures":["[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]"]}

SS
------------------------------
[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
Jul 30 11:56:39.273: INFO: Driver hostPathSymlink doesn't support ext3 -- skipping
... skipping 154 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-d1ebbd91-8472-4d7d-a399-795ed606c72d
STEP: Creating a pod to test consume configMaps
Jul 30 11:56:31.735: INFO: Waiting up to 5m0s for pod "pod-projected-configmaps-f6c93c93-ba35-4b0c-9e45-a126f6bc4d01" in namespace "projected-8444" to be "Succeeded or Failed"
Jul 30 11:56:31.923: INFO: Pod "pod-projected-configmaps-f6c93c93-ba35-4b0c-9e45-a126f6bc4d01": Phase="Pending", Reason="", readiness=false. Elapsed: 188.597417ms
Jul 30 11:56:34.112: INFO: Pod "pod-projected-configmaps-f6c93c93-ba35-4b0c-9e45-a126f6bc4d01": Phase="Pending", Reason="", readiness=false. Elapsed: 2.37769516s
Jul 30 11:56:36.301: INFO: Pod "pod-projected-configmaps-f6c93c93-ba35-4b0c-9e45-a126f6bc4d01": Phase="Pending", Reason="", readiness=false. Elapsed: 4.566681431s
Jul 30 11:56:38.490: INFO: Pod "pod-projected-configmaps-f6c93c93-ba35-4b0c-9e45-a126f6bc4d01": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.755635789s
STEP: Saw pod success
Jul 30 11:56:38.490: INFO: Pod "pod-projected-configmaps-f6c93c93-ba35-4b0c-9e45-a126f6bc4d01" satisfied condition "Succeeded or Failed"
Jul 30 11:56:38.681: INFO: Trying to get logs from node ip-172-20-35-124.ap-southeast-2.compute.internal pod pod-projected-configmaps-f6c93c93-ba35-4b0c-9e45-a126f6bc4d01 container agnhost-container: <nil>
STEP: delete the pod
Jul 30 11:56:39.075: INFO: Waiting for pod pod-projected-configmaps-f6c93c93-ba35-4b0c-9e45-a126f6bc4d01 to disappear
Jul 30 11:56:39.263: INFO: Pod pod-projected-configmaps-f6c93c93-ba35-4b0c-9e45-a126f6bc4d01 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:9.236 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":2,"skipped":7,"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
Jul 30 11:56:39.664: INFO: Only supported for providers [vsphere] (not aws)
... 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
Jul 30 11:56:36.070: 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 fail when exceeds active deadline
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/job.go:139
STEP: Creating a job
STEP: Ensuring job past active deadline
[AfterEach] [sig-apps] Job
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 11:56:39.420: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "job-2746" for this suite.

•
------------------------------
{"msg":"PASSED [sig-apps] Job should fail when exceeds active deadline","total":-1,"completed":2,"skipped":26,"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
Jul 30 11:56:39.815: INFO: Only supported for providers [azure] (not aws)
[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 71 lines ...
• [SLOW TEST:8.558 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":5,"skipped":46,"failed":0}
[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
Jul 30 11:56:40.303: INFO: Only supported for node OS distro [gci ubuntu custom] (not debian)
[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

... skipping 78 lines ...
Jul 30 11:56:41.680: INFO: pv is nil


S [SKIPPING] in Spec Setup (BeforeEach) [1.336 seconds]
[sig-storage] PersistentVolumes GCEPD
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  should test that deleting the PV before the pod does not cause pod deletion to fail on PD detach [BeforeEach]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-gce.go:141

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

  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-gce.go:85
------------------------------
... skipping 28 lines ...
Jul 30 11:56:39.834: 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,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
Jul 30 11:56:41.225: INFO: Waiting up to 5m0s for pod "pod-9ccfda35-5028-4bfb-a5fe-3b5b89ee891d" in namespace "emptydir-938" to be "Succeeded or Failed"
Jul 30 11:56:41.420: INFO: Pod "pod-9ccfda35-5028-4bfb-a5fe-3b5b89ee891d": Phase="Pending", Reason="", readiness=false. Elapsed: 195.29559ms
Jul 30 11:56:43.613: INFO: Pod "pod-9ccfda35-5028-4bfb-a5fe-3b5b89ee891d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.388043563s
STEP: Saw pod success
Jul 30 11:56:43.613: INFO: Pod "pod-9ccfda35-5028-4bfb-a5fe-3b5b89ee891d" satisfied condition "Succeeded or Failed"
Jul 30 11:56:43.805: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod pod-9ccfda35-5028-4bfb-a5fe-3b5b89ee891d container test-container: <nil>
STEP: delete the pod
Jul 30 11:56:44.196: INFO: Waiting for pod pod-9ccfda35-5028-4bfb-a5fe-3b5b89ee891d to disappear
Jul 30 11:56:44.392: INFO: Pod pod-9ccfda35-5028-4bfb-a5fe-3b5b89ee891d 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
Jul 30 11:56:44.392: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "emptydir-938" for this suite.

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

SSSSS
------------------------------
[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
Jul 30 11:56:44.807: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 54 lines ...
Jul 30 11:56:18.189: INFO: Creating resource for dynamic PV
Jul 30 11:56:18.189: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-9710-aws-sc4hzkw
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jul 30 11:56:18.761: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jul 30 11:56:19.144: INFO: Error updating pvc awsrvhw2: PersistentVolumeClaim "awsrvhw2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9710-aws-sc4hzkw",
  	... // 2 identical fields
  }

Jul 30 11:56:21.522: INFO: Error updating pvc awsrvhw2: PersistentVolumeClaim "awsrvhw2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9710-aws-sc4hzkw",
  	... // 2 identical fields
  }

Jul 30 11:56:23.522: INFO: Error updating pvc awsrvhw2: PersistentVolumeClaim "awsrvhw2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9710-aws-sc4hzkw",
  	... // 2 identical fields
  }

Jul 30 11:56:25.521: INFO: Error updating pvc awsrvhw2: PersistentVolumeClaim "awsrvhw2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9710-aws-sc4hzkw",
  	... // 2 identical fields
  }

Jul 30 11:56:27.523: INFO: Error updating pvc awsrvhw2: PersistentVolumeClaim "awsrvhw2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9710-aws-sc4hzkw",
  	... // 2 identical fields
  }

Jul 30 11:56:29.523: INFO: Error updating pvc awsrvhw2: PersistentVolumeClaim "awsrvhw2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9710-aws-sc4hzkw",
  	... // 2 identical fields
  }

Jul 30 11:56:31.521: INFO: Error updating pvc awsrvhw2: PersistentVolumeClaim "awsrvhw2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9710-aws-sc4hzkw",
  	... // 2 identical fields
  }

Jul 30 11:56:33.522: INFO: Error updating pvc awsrvhw2: PersistentVolumeClaim "awsrvhw2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9710-aws-sc4hzkw",
  	... // 2 identical fields
  }

Jul 30 11:56:35.521: INFO: Error updating pvc awsrvhw2: PersistentVolumeClaim "awsrvhw2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9710-aws-sc4hzkw",
  	... // 2 identical fields
  }

Jul 30 11:56:37.521: INFO: Error updating pvc awsrvhw2: PersistentVolumeClaim "awsrvhw2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9710-aws-sc4hzkw",
  	... // 2 identical fields
  }

Jul 30 11:56:39.522: INFO: Error updating pvc awsrvhw2: PersistentVolumeClaim "awsrvhw2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9710-aws-sc4hzkw",
  	... // 2 identical fields
  }

Jul 30 11:56:41.524: INFO: Error updating pvc awsrvhw2: PersistentVolumeClaim "awsrvhw2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9710-aws-sc4hzkw",
  	... // 2 identical fields
  }

Jul 30 11:56:43.522: INFO: Error updating pvc awsrvhw2: PersistentVolumeClaim "awsrvhw2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9710-aws-sc4hzkw",
  	... // 2 identical fields
  }

Jul 30 11:56:45.521: INFO: Error updating pvc awsrvhw2: PersistentVolumeClaim "awsrvhw2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9710-aws-sc4hzkw",
  	... // 2 identical fields
  }

Jul 30 11:56:47.524: INFO: Error updating pvc awsrvhw2: PersistentVolumeClaim "awsrvhw2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9710-aws-sc4hzkw",
  	... // 2 identical fields
  }

Jul 30 11:56:49.524: INFO: Error updating pvc awsrvhw2: PersistentVolumeClaim "awsrvhw2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9710-aws-sc4hzkw",
  	... // 2 identical fields
  }

Jul 30 11:56:49.900: INFO: Error updating pvc awsrvhw2: PersistentVolumeClaim "awsrvhw2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 24 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)] 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] In-tree Volumes [Driver: aws] [Testpattern: Dynamic PV (block volmode)] volume-expand should not allow expansion of pvcs without AllowVolumeExpansion property","total":-1,"completed":2,"skipped":18,"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
Jul 30 11:56:50.856: INFO: Only supported for node OS distro [gci ubuntu custom] (not debian)
[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 99 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 11:56:54.285: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "lease-test-9012" for this suite.

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

SSSSS
------------------------------
[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
Jul 30 11:56:54.691: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 102 lines ...
• [SLOW TEST:58.302 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 ready until startupProbe succeeds
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/container_probe.go:396
------------------------------
{"msg":"PASSED [k8s.io] Probing container should not be ready until startupProbe succeeds","total":-1,"completed":2,"skipped":18,"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
Jul 30 11:57:00.208: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 57 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/framework.go:23
  Kubectl replace
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:1551
    should update a single-container pod's image  [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 replace should update a single-container pod's image  [Conformance]","total":-1,"completed":7,"skipped":88,"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
Jul 30 11:57:00.790: INFO: Driver supports dynamic provisioning, skipping InlineVolume pattern
... skipping 132 lines ...
Jul 30 11:56:50.722: INFO: PersistentVolumeClaim pvc-zxfxq found but phase is Pending instead of Bound.
Jul 30 11:56:52.913: INFO: PersistentVolumeClaim pvc-zxfxq found and phase=Bound (4.571291002s)
Jul 30 11:56:52.913: INFO: Waiting up to 3m0s for PersistentVolume local-btqsx to have phase Bound
Jul 30 11:56:53.103: INFO: PersistentVolume local-btqsx found and phase=Bound (190.11017ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-hc6p
STEP: Creating a pod to test subpath
Jul 30 11:56:53.675: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-hc6p" in namespace "provisioning-3116" to be "Succeeded or Failed"
Jul 30 11:56:53.866: INFO: Pod "pod-subpath-test-preprovisionedpv-hc6p": Phase="Pending", Reason="", readiness=false. Elapsed: 190.606795ms
Jul 30 11:56:56.056: INFO: Pod "pod-subpath-test-preprovisionedpv-hc6p": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.381049922s
STEP: Saw pod success
Jul 30 11:56:56.057: INFO: Pod "pod-subpath-test-preprovisionedpv-hc6p" satisfied condition "Succeeded or Failed"
Jul 30 11:56:56.247: INFO: Trying to get logs from node ip-172-20-45-65.ap-southeast-2.compute.internal pod pod-subpath-test-preprovisionedpv-hc6p container test-container-subpath-preprovisionedpv-hc6p: <nil>
STEP: delete the pod
Jul 30 11:56:56.635: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-hc6p to disappear
Jul 30 11:56:56.825: INFO: Pod pod-subpath-test-preprovisionedpv-hc6p no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-hc6p
Jul 30 11:56:56.825: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-hc6p" in namespace "provisioning-3116"
... 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":6,"skipped":61,"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
Jul 30 11:57:01.897: INFO: Only supported for providers [gce gke] (not aws)
... skipping 111 lines ...
Jul 30 11:57:00.854: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename containers
STEP: Waiting for a default service account to be provisioned in namespace
[It] should be able to override the image's default command (docker entrypoint) [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 override command
Jul 30 11:57:01.987: INFO: Waiting up to 5m0s for pod "client-containers-2f17ab90-bcf7-4d1e-8426-3e4c22056689" in namespace "containers-2694" to be "Succeeded or Failed"
Jul 30 11:57:02.175: INFO: Pod "client-containers-2f17ab90-bcf7-4d1e-8426-3e4c22056689": Phase="Pending", Reason="", readiness=false. Elapsed: 188.130814ms
Jul 30 11:57:04.365: INFO: Pod "client-containers-2f17ab90-bcf7-4d1e-8426-3e4c22056689": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.377401136s
STEP: Saw pod success
Jul 30 11:57:04.365: INFO: Pod "client-containers-2f17ab90-bcf7-4d1e-8426-3e4c22056689" satisfied condition "Succeeded or Failed"
Jul 30 11:57:04.553: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod client-containers-2f17ab90-bcf7-4d1e-8426-3e4c22056689 container agnhost-container: <nil>
STEP: delete the pod
Jul 30 11:57:04.935: INFO: Waiting for pod client-containers-2f17ab90-bcf7-4d1e-8426-3e4c22056689 to disappear
Jul 30 11:57:05.128: INFO: Pod client-containers-2f17ab90-bcf7-4d1e-8426-3e4c22056689 no longer exists
[AfterEach] [k8s.io] Docker Containers
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 11:57:05.128: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "containers-2694" for this suite.

•
------------------------------
{"msg":"PASSED [k8s.io] Docker Containers should be able to override the image's default command (docker entrypoint) [NodeConformance] [Conformance]","total":-1,"completed":8,"skipped":101,"failed":0}

S
------------------------------
{"msg":"PASSED [sig-cli] Kubectl client Kubectl server-side dry-run should check if kubectl can dry-run update Pods [Conformance]","total":-1,"completed":4,"skipped":40,"failed":0}
[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
Jul 30 11:56:58.689: 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
... skipping 12 lines ...
• [SLOW TEST:7.592 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 annotations 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 annotations on modification [NodeConformance] [Conformance]","total":-1,"completed":5,"skipped":40,"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
Jul 30 11:57:06.290: 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 20 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
Jul 30 11:57:03.106: INFO: Waiting up to 5m0s for pod "downwardapi-volume-35732975-37f5-44d4-b631-6e17a2f42887" in namespace "projected-8223" to be "Succeeded or Failed"
Jul 30 11:57:03.297: INFO: Pod "downwardapi-volume-35732975-37f5-44d4-b631-6e17a2f42887": Phase="Pending", Reason="", readiness=false. Elapsed: 190.45727ms
Jul 30 11:57:05.487: INFO: Pod "downwardapi-volume-35732975-37f5-44d4-b631-6e17a2f42887": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.380960897s
STEP: Saw pod success
Jul 30 11:57:05.487: INFO: Pod "downwardapi-volume-35732975-37f5-44d4-b631-6e17a2f42887" satisfied condition "Succeeded or Failed"
Jul 30 11:57:05.678: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod downwardapi-volume-35732975-37f5-44d4-b631-6e17a2f42887 container client-container: <nil>
STEP: delete the pod
Jul 30 11:57:06.066: INFO: Waiting for pod downwardapi-volume-35732975-37f5-44d4-b631-6e17a2f42887 to disappear
Jul 30 11:57:06.257: INFO: Pod downwardapi-volume-35732975-37f5-44d4-b631-6e17a2f42887 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
Jul 30 11:57:06.257: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "projected-8223" for this suite.

•
------------------------------
{"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":7,"skipped":73,"failed":0}

SS
------------------------------
[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 57 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-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}

S
------------------------------
[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
Jul 30 11:57:06.713: INFO: Driver emptydir 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: emptydir]
  /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 emptydir 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 4 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 env vars [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-4e64b797-4175-427f-829f-4e4e0e5a600e
STEP: Creating a pod to test consume secrets
Jul 30 11:57:06.844: INFO: Waiting up to 5m0s for pod "pod-secrets-c5f1d2d8-5caf-4b3c-84c8-da8bab8a5b52" in namespace "secrets-9145" to be "Succeeded or Failed"
Jul 30 11:57:07.033: INFO: Pod "pod-secrets-c5f1d2d8-5caf-4b3c-84c8-da8bab8a5b52": Phase="Pending", Reason="", readiness=false. Elapsed: 188.230088ms
Jul 30 11:57:09.221: INFO: Pod "pod-secrets-c5f1d2d8-5caf-4b3c-84c8-da8bab8a5b52": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.377004645s
STEP: Saw pod success
Jul 30 11:57:09.221: INFO: Pod "pod-secrets-c5f1d2d8-5caf-4b3c-84c8-da8bab8a5b52" satisfied condition "Succeeded or Failed"
Jul 30 11:57:09.410: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod pod-secrets-c5f1d2d8-5caf-4b3c-84c8-da8bab8a5b52 container secret-env-test: <nil>
STEP: delete the pod
Jul 30 11:57:09.792: INFO: Waiting for pod pod-secrets-c5f1d2d8-5caf-4b3c-84c8-da8bab8a5b52 to disappear
Jul 30 11:57:09.983: INFO: Pod pod-secrets-c5f1d2d8-5caf-4b3c-84c8-da8bab8a5b52 no longer exists
[AfterEach] [sig-api-machinery] Secrets
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 11:57:09.983: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "secrets-9145" for this suite.

•
------------------------------
{"msg":"PASSED [sig-api-machinery] Secrets should be consumable from pods in env vars [NodeConformance] [Conformance]","total":-1,"completed":9,"skipped":102,"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
Jul 30 11:57:10.390: INFO: Driver hostPathSymlink doesn't support PreprovisionedPV -- 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 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
Jul 30 11:57:07.456: INFO: Waiting up to 5m0s for pod "downwardapi-volume-1f9529f1-c301-4a52-99aa-465e6874d876" in namespace "projected-8957" to be "Succeeded or Failed"
Jul 30 11:57:07.648: INFO: Pod "downwardapi-volume-1f9529f1-c301-4a52-99aa-465e6874d876": Phase="Pending", Reason="", readiness=false. Elapsed: 192.30584ms
Jul 30 11:57:09.841: INFO: Pod "downwardapi-volume-1f9529f1-c301-4a52-99aa-465e6874d876": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.384763065s
STEP: Saw pod success
Jul 30 11:57:09.841: INFO: Pod "downwardapi-volume-1f9529f1-c301-4a52-99aa-465e6874d876" satisfied condition "Succeeded or Failed"
Jul 30 11:57:10.034: INFO: Trying to get logs from node ip-172-20-35-124.ap-southeast-2.compute.internal pod downwardapi-volume-1f9529f1-c301-4a52-99aa-465e6874d876 container client-container: <nil>
STEP: delete the pod
Jul 30 11:57:10.432: INFO: Waiting for pod downwardapi-volume-1f9529f1-c301-4a52-99aa-465e6874d876 to disappear
Jul 30 11:57:10.627: INFO: Pod downwardapi-volume-1f9529f1-c301-4a52-99aa-465e6874d876 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
Jul 30 11:57:10.627: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "projected-8957" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] Projected downwardAPI should set DefaultMode on files [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":6,"skipped":41,"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
Jul 30 11:57:11.022: 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 30 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 11:57:15.575: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "configmap-3945" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] ConfigMap binary data should be reflected in volume [NodeConformance] [Conformance]","total":-1,"completed":7,"skipped":43,"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 17 lines ...
Jul 30 11:57:04.592: INFO: PersistentVolumeClaim pvc-h5wvw found but phase is Pending instead of Bound.
Jul 30 11:57:06.781: INFO: PersistentVolumeClaim pvc-h5wvw found and phase=Bound (6.753646977s)
Jul 30 11:57:06.781: INFO: Waiting up to 3m0s for PersistentVolume local-jnzrd to have phase Bound
Jul 30 11:57:06.969: INFO: PersistentVolume local-jnzrd found and phase=Bound (188.457825ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-ffw7
STEP: Creating a pod to test subpath
Jul 30 11:57:07.536: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-ffw7" in namespace "provisioning-7580" to be "Succeeded or Failed"
Jul 30 11:57:07.724: INFO: Pod "pod-subpath-test-preprovisionedpv-ffw7": Phase="Pending", Reason="", readiness=false. Elapsed: 188.473231ms
Jul 30 11:57:09.915: INFO: Pod "pod-subpath-test-preprovisionedpv-ffw7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.379156308s
Jul 30 11:57:12.111: INFO: Pod "pod-subpath-test-preprovisionedpv-ffw7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.574744984s
STEP: Saw pod success
Jul 30 11:57:12.111: INFO: Pod "pod-subpath-test-preprovisionedpv-ffw7" satisfied condition "Succeeded or Failed"
Jul 30 11:57:12.299: INFO: Trying to get logs from node ip-172-20-45-65.ap-southeast-2.compute.internal pod pod-subpath-test-preprovisionedpv-ffw7 container test-container-volume-preprovisionedpv-ffw7: <nil>
STEP: delete the pod
Jul 30 11:57:12.685: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-ffw7 to disappear
Jul 30 11:57:13.467: INFO: Pod pod-subpath-test-preprovisionedpv-ffw7 no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-ffw7
Jul 30 11:57:13.467: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-ffw7" in namespace "provisioning-7580"
... 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":4,"skipped":29,"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
Jul 30 11:57:16.078: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 180 lines ...
STEP: Destroying namespace "services-4848" 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 check NodePort out-of-range","total":-1,"completed":5,"skipped":40,"failed":0}

S
------------------------------
[BeforeEach] [sig-network] Service endpoints latency
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 422 lines ...
• [SLOW TEST:12.190 seconds]
[sig-network] Service endpoints latency
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
  should not be very high  [Conformance]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
------------------------------
{"msg":"PASSED [sig-network] Service endpoints latency should not be very high  [Conformance]","total":-1,"completed":4,"skipped":23,"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
Jul 30 11:57:18.922: INFO: Only supported for providers [openstack] (not aws)
[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 11 lines ...
      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
------------------------------
SSSSS
------------------------------
{"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":2,"skipped":47,"failed":1,"failures":["[sig-storage] PersistentVolumes-local  [Volume type: dir-link-bindmounted] Two pods mounting a local volume at the same time should be able to write from pod1 and read from pod2"]}
[BeforeEach] [sig-scheduling] Multi-AZ Cluster Volumes [sig-storage]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Jul 30 11:57:17.663: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename multi-az
STEP: Waiting for a default service account to be provisioned in namespace
... skipping 83 lines ...
STEP: Creating a validating webhook configuration
Jul 30 11:56:19.792: INFO: Waiting for webhook configuration to be ready...
Jul 30 11:56:30.282: INFO: Waiting for webhook configuration to be ready...
Jul 30 11:56:40.676: INFO: Waiting for webhook configuration to be ready...
Jul 30 11:56:51.093: INFO: Waiting for webhook configuration to be ready...
Jul 30 11:57:01.476: INFO: Waiting for webhook configuration to be ready...
Jul 30 11:57:01.476: FAIL: waiting for webhook configuration to be ready
Unexpected error:
    <*errors.errorString | 0xc000202200>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred

... skipping 485 lines ...
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
  patching/updating a validating webhook should work [Conformance] [It]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629

  Jul 30 11:57:01.476: waiting for webhook configuration to be ready
  Unexpected error:
      <*errors.errorString | 0xc000202200>: {
          s: "timed out waiting for the condition",
      }
      timed out waiting for the condition
  occurred

... skipping 69 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":"FAILED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a validating webhook should work [Conformance]","total":-1,"completed":1,"skipped":12,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a validating webhook should work [Conformance]"]}
[BeforeEach] [sig-api-machinery] Events
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Jul 30 11:57:19.905: 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 9 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 11:57:22.017: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "events-6657" 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":2,"skipped":12,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a validating webhook should work [Conformance]"]}

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
Jul 30 11:57:22.414: INFO: Only supported for node OS distro [gci ubuntu custom] (not debian)
... skipping 44 lines ...
Jul 30 11:57:20.349: 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
Jul 30 11:57:21.490: INFO: Waiting up to 5m0s for pod "security-context-6c630c9a-040f-4c5e-92cf-b9ae67afc018" in namespace "security-context-4478" to be "Succeeded or Failed"
Jul 30 11:57:21.679: INFO: Pod "security-context-6c630c9a-040f-4c5e-92cf-b9ae67afc018": Phase="Pending", Reason="", readiness=false. Elapsed: 189.773452ms
Jul 30 11:57:23.870: INFO: Pod "security-context-6c630c9a-040f-4c5e-92cf-b9ae67afc018": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.380047407s
STEP: Saw pod success
Jul 30 11:57:23.870: INFO: Pod "security-context-6c630c9a-040f-4c5e-92cf-b9ae67afc018" satisfied condition "Succeeded or Failed"
Jul 30 11:57:24.076: INFO: Trying to get logs from node ip-172-20-45-65.ap-southeast-2.compute.internal pod security-context-6c630c9a-040f-4c5e-92cf-b9ae67afc018 container test-container: <nil>
STEP: delete the pod
Jul 30 11:57:24.511: INFO: Waiting for pod security-context-6c630c9a-040f-4c5e-92cf-b9ae67afc018 to disappear
Jul 30 11:57:24.706: INFO: Pod security-context-6c630c9a-040f-4c5e-92cf-b9ae67afc018 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 144 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":1,"skipped":9,"failed":0}

SSSSS
------------------------------
[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
Jul 30 11:57:25.934: INFO: Only supported for providers [gce gke] (not aws)
... 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: gcepd]
  /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 [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 10 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
Jul 30 11:57:19.999: INFO: In-tree plugin kubernetes.io/host-path is not migrated, not validating any metrics
Jul 30 11:57:20.190: INFO: Creating resource for inline volume
STEP: Creating pod pod-subpath-test-inlinevolume-wjtt
STEP: Creating a pod to test subpath
Jul 30 11:57:20.385: INFO: Waiting up to 5m0s for pod "pod-subpath-test-inlinevolume-wjtt" in namespace "provisioning-674" to be "Succeeded or Failed"
Jul 30 11:57:20.576: INFO: Pod "pod-subpath-test-inlinevolume-wjtt": Phase="Pending", Reason="", readiness=false. Elapsed: 190.551013ms
Jul 30 11:57:22.768: INFO: Pod "pod-subpath-test-inlinevolume-wjtt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.382694506s
Jul 30 11:57:24.971: INFO: Pod "pod-subpath-test-inlinevolume-wjtt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.585325369s
STEP: Saw pod success
Jul 30 11:57:24.971: INFO: Pod "pod-subpath-test-inlinevolume-wjtt" satisfied condition "Succeeded or Failed"
Jul 30 11:57:25.161: INFO: Trying to get logs from node ip-172-20-33-146.ap-southeast-2.compute.internal pod pod-subpath-test-inlinevolume-wjtt container test-container-subpath-inlinevolume-wjtt: <nil>
STEP: delete the pod
Jul 30 11:57:25.563: INFO: Waiting for pod pod-subpath-test-inlinevolume-wjtt to disappear
Jul 30 11:57:25.754: INFO: Pod pod-subpath-test-inlinevolume-wjtt no longer exists
STEP: Deleting pod pod-subpath-test-inlinevolume-wjtt
Jul 30 11:57:25.754: INFO: Deleting pod "pod-subpath-test-inlinevolume-wjtt" in namespace "provisioning-674"
... 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: hostPath] [Testpattern: Inline-volume (default fs)] subPath should support readOnly directory specified in the volumeMount","total":-1,"completed":3,"skipped":57,"failed":1,"failures":["[sig-storage] PersistentVolumes-local  [Volume type: dir-link-bindmounted] Two pods mounting a local volume at the same time should be able to write from pod1 and read from pod2"]}

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
Jul 30 11:57:26.549: INFO: Driver hostPathSymlink 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
Jul 30 11:57:26.945: 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/json\"","total":-1,"completed":4,"skipped":61,"failed":1,"failures":["[sig-storage] PersistentVolumes-local  [Volume type: dir-link-bindmounted] Two pods mounting a local volume at the same time should be able to write from pod1 and read from pod2"]}
[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
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:88
Jul 30 11:57:27.147: INFO: Driver "csi-hostpath" does not support topology - skipping
[AfterEach] [Testpattern: Dynamic PV (immediate binding)] topology
... skipping 4 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 196 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_volumes.go:39
    [Testpattern: Dynamic 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] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]","total":-1,"completed":4,"skipped":42,"failed":0}

SS
------------------------------
[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
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumes
... skipping 97 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)] 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: Dynamic PV (block volmode)] volumes should store data","total":-1,"completed":2,"skipped":12,"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
Jul 30 11:57:28.275: INFO: Only supported for providers [openstack] (not aws)
... skipping 88 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
Jul 30 11:57:29.448: INFO: Waiting up to 5m0s for pod "downwardapi-volume-399d56fc-d315-40a3-8486-9a3f84306474" in namespace "downward-api-990" to be "Succeeded or Failed"
Jul 30 11:57:29.637: INFO: Pod "downwardapi-volume-399d56fc-d315-40a3-8486-9a3f84306474": Phase="Pending", Reason="", readiness=false. Elapsed: 189.360486ms
Jul 30 11:57:31.827: INFO: Pod "downwardapi-volume-399d56fc-d315-40a3-8486-9a3f84306474": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.37914669s
STEP: Saw pod success
Jul 30 11:57:31.827: INFO: Pod "downwardapi-volume-399d56fc-d315-40a3-8486-9a3f84306474" satisfied condition "Succeeded or Failed"
Jul 30 11:57:32.016: INFO: Trying to get logs from node ip-172-20-33-146.ap-southeast-2.compute.internal pod downwardapi-volume-399d56fc-d315-40a3-8486-9a3f84306474 container client-container: <nil>
STEP: delete the pod
Jul 30 11:57:32.403: INFO: Waiting for pod downwardapi-volume-399d56fc-d315-40a3-8486-9a3f84306474 to disappear
Jul 30 11:57:32.592: INFO: Pod downwardapi-volume-399d56fc-d315-40a3-8486-9a3f84306474 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
Jul 30 11:57:32.593: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "downward-api-990" 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":3,"skipped":18,"failed":0}

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
Jul 30 11:57:32.988: INFO: Driver csi-hostpath doesn't support InlineVolume -- skipping
... skipping 12 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:151

      Driver csi-hostpath 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 [k8s.io] Docker Containers should use the image defaults if command and args are blank [NodeConformance] [Conformance]","total":-1,"completed":1,"skipped":6,"failed":0}
[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
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Jul 30 11:55:42.755: INFO: >>> kubeConfig: /root/.kube/config
... skipping 117 lines ...
Jul 30 11:57:24.612: INFO: ExecWithOptions {Command:[nsenter --mount=/rootfs/proc/1/ns/mnt -- sh -c rm -r /tmp/local-driver-98c53789-5eb3-4aac-812f-9307b6b8290c] Namespace:volume-6772 PodName:hostexec-ip-172-20-33-146.ap-southeast-2.compute.internal-9ngmf ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:true Quiet:false}
Jul 30 11:57:24.612: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:57:25.823: INFO: exec ip-172-20-33-146.ap-southeast-2.compute.internal: command:   rm -r /tmp/local-driver-98c53789-5eb3-4aac-812f-9307b6b8290c
Jul 30 11:57:25.823: INFO: exec ip-172-20-33-146.ap-southeast-2.compute.internal: stdout:    ""
Jul 30 11:57:25.823: INFO: exec ip-172-20-33-146.ap-southeast-2.compute.internal: stderr:    "rm: cannot remove '/tmp/local-driver-98c53789-5eb3-4aac-812f-9307b6b8290c': Device or resource busy\n"
Jul 30 11:57:25.823: INFO: exec ip-172-20-33-146.ap-southeast-2.compute.internal: exit code: 0
Jul 30 11:57:25.824: FAIL: Unexpected error:
    <exec.CodeExitError>: {
        Err: {
            s: "command terminated with exit code 1",
        },
        Code: 1,
    }
... skipping 40 lines ...
Jul 30 11:57:26.217: INFO: At 2021-07-30 11:55:53 +0000 UTC - event for local-injector: {default-scheduler } Scheduled: Successfully assigned volume-6772/local-injector to ip-172-20-33-146.ap-southeast-2.compute.internal
Jul 30 11:57:26.217: INFO: At 2021-07-30 11:55:54 +0000 UTC - event for local-injector: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} Pulling: Pulling image "docker.io/library/busybox:1.29"
Jul 30 11:57:26.217: INFO: At 2021-07-30 11:56:06 +0000 UTC - event for local-injector: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} Started: Started container local-injector
Jul 30 11:57:26.217: INFO: At 2021-07-30 11:56:06 +0000 UTC - event for local-injector: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} Created: Created container local-injector
Jul 30 11:57:26.217: INFO: At 2021-07-30 11:56:06 +0000 UTC - event for local-injector: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} Pulled: Successfully pulled image "docker.io/library/busybox:1.29" in 11.978516284s
Jul 30 11:57:26.217: INFO: At 2021-07-30 11:56:14 +0000 UTC - event for local-injector: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} Killing: Stopping container local-injector
Jul 30 11:57:26.217: INFO: At 2021-07-30 11:56:16 +0000 UTC - event for local-injector: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} FailedKillPod: error killing pod: failed to "KillPodSandbox" for "65a745f6-d4d7-477b-9916-dd7704ff869e" with KillPodSandboxError: "rpc error: code = Unknown desc = failed to remove network namespace for sandbox \"b091e8c0a86249ab0508f53a92b96f26e25b8e3488275a39e19a2ea5a1507c2c\": failed to remove netns: unlinkat /run/netns/cni-9d8d09c7-e0fd-18fd-be66-65c0957f0a75: device or resource busy"
Jul 30 11:57:26.217: INFO: At 2021-07-30 11:56:30 +0000 UTC - event for local-injector: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} FailedSync: error determining status: rpc error: code = Unknown desc = failed to get sandbox ip: check network namespace closed: remove netns: unlinkat /var/run/netns/cni-9d8d09c7-e0fd-18fd-be66-65c0957f0a75: device or resource busy
Jul 30 11:57:26.217: INFO: At 2021-07-30 11:56:43 +0000 UTC - event for local-client: {default-scheduler } Scheduled: Successfully assigned volume-6772/local-client to ip-172-20-33-146.ap-southeast-2.compute.internal
Jul 30 11:57:26.217: INFO: At 2021-07-30 11:56:44 +0000 UTC - event for local-client: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} Started: Started container local-client
Jul 30 11:57:26.217: INFO: At 2021-07-30 11:56:44 +0000 UTC - event for local-client: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} Created: Created container local-client
Jul 30 11:57:26.217: INFO: At 2021-07-30 11:56:44 +0000 UTC - event for local-client: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} Pulled: Container image "docker.io/library/busybox:1.29" already present on machine
Jul 30 11:57:26.217: INFO: At 2021-07-30 11:56:52 +0000 UTC - event for local-client: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} Killing: Stopping container local-client
Jul 30 11:57:26.217: INFO: At 2021-07-30 11:56:54 +0000 UTC - event for local-client: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} FailedKillPod: error killing pod: failed to "KillPodSandbox" for "6b0a440d-f5ba-48f8-b0ea-5f4d6ff32aec" with KillPodSandboxError: "rpc error: code = Unknown desc = failed to remove network namespace for sandbox \"39a051d3a9b18d43e9c06fe33863b8dec6abe62ebc276d4ab7538a00b4ab1040\": failed to remove netns: unlinkat /run/netns/cni-f6bef1e5-d3f5-8aa4-66d6-d47a7149b86a: device or resource busy"
Jul 30 11:57:26.217: INFO: At 2021-07-30 11:57:06 +0000 UTC - event for local-client: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} FailedSync: error determining status: rpc error: code = Unknown desc = failed to get sandbox ip: check network namespace closed: remove netns: unlinkat /var/run/netns/cni-f6bef1e5-d3f5-8aa4-66d6-d47a7149b86a: device or resource busy
Jul 30 11:57:26.217: INFO: At 2021-07-30 11:57:25 +0000 UTC - event for hostexec-ip-172-20-33-146.ap-southeast-2.compute.internal-9ngmf: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} Killing: Stopping container agnhost-container
Jul 30 11:57:26.408: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Jul 30 11:57:26.408: INFO: 
Jul 30 11:57:26.605: INFO: 
Logging node info for node ip-172-20-33-146.ap-southeast-2.compute.internal
Jul 30 11:57:26.794: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-33-146.ap-southeast-2.compute.internal    4d2de44e-bfe4-4abe-80e1-cf5dee13ece9 4349 0 2021-07-30 11:52:00 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:t3.medium beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:ap-southeast-2 failure-domain.beta.kubernetes.io/zone:ap-southeast-2a kops.k8s.io/instancegroup:nodes-ap-southeast-2a kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-33-146.ap-southeast-2.compute.internal kubernetes.io/os:linux kubernetes.io/role:node node-role.kubernetes.io/node: node.kubernetes.io/instance-type:t3.medium topology.kubernetes.io/region:ap-southeast-2 topology.kubernetes.io/zone:ap-southeast-2a] map[node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] []  [{kops-controller Update v1 2021-07-30 11:52:00 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kops.k8s.io/instancegroup":{},"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/node":{}}}}} {kube-controller-manager Update v1 2021-07-30 11:56:55 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.1.0/24\"":{}}}}} {kubelet Update v1 2021-07-30 11:57:10 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"ExternalDNS\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"ExternalIP\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalDNS\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:attachable-volumes-aws-ebs":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:attachable-volumes-aws-ebs":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}}]},Spec:NodeSpec{PodCIDR:100.96.1.0/24,DoNotUseExternalID:,ProviderID:aws:///ap-southeast-2a/i-04fff175d722b0fbd,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.1.0/24],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-aws-ebs: {{25 0} {<nil>} 25 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{51527004160 0} {<nil>} 50319340Ki BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3910443008 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-aws-ebs: {{25 0} {<nil>} 25 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{46374303668 0} {<nil>} 46374303668 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3805585408 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-07-30 11:57:10 +0000 UTC,LastTransitionTime:2021-07-30 11:52:00 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-07-30 11:57:10 +0000 UTC,LastTransitionTime:2021-07-30 11:52:00 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-07-30 11:57:10 +0000 UTC,LastTransitionTime:2021-07-30 11:52:00 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-07-30 11:57:10 +0000 UTC,LastTransitionTime:2021-07-30 11:52:01 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.33.146,},NodeAddress{Type:ExternalIP,Address:54.253.58.229,},NodeAddress{Type:Hostname,Address:ip-172-20-33-146.ap-southeast-2.compute.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-33-146.ap-southeast-2.compute.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-54-253-58-229.ap-southeast-2.compute.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec214589b3c37ae2e89f45d65f37c96a,SystemUUID:EC214589-B3C3-7AE2-E89F-45D65F37C96A,BootID:390e87f5-55fd-45b5-9a55-8f69ac17e9f2,KernelVersion:3.10.0-1160.el7.x86_64,OSImage:Red Hat Enterprise Linux Server 7.9 (Maipo),ContainerRuntimeVersion:containerd://1.4.6,KubeletVersion:v1.20.9,KubeProxyVersion:v1.20.9,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[k8s.gcr.io/kube-proxy-amd64:v1.20.9],SizeBytes:101477471,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/jessie-dnsutils@sha256:ad583e33cb284f7ef046673809b146ec4053cda19b54a85d2b180a86169715eb gcr.io/kubernetes-e2e-test-images/jessie-dnsutils:1.0],SizeBytes:85425365,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:ab055cd3d45f50b90732c14593a5bf50f210871bb4f91994c756fc22db6d922a k8s.gcr.io/e2e-test-images/agnhost:2.21],SizeBytes:46251468,},ContainerImage{Names:[docker.io/library/httpd@sha256:eb8ccf084cf3e80eece1add239effefd171eb39adbc154d33c14260d905d4060 docker.io/library/httpd:2.4.38-alpine],SizeBytes:40765017,},ContainerImage{Names:[docker.io/kopeio/networking-agent@sha256:2d16bdbc3257c42cdc59b05b8fad86653033f19cfafa709f263e93c8f7002932 docker.io/kopeio/networking-agent:1.0.20181028],SizeBytes:25781346,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler@sha256:67640771ad9fc56f109d5b01e020f0c858e7c890bb0eb15ba0ebd325df3285e7 k8s.gcr.io/cpa/cluster-proportional-autoscaler:1.8.3],SizeBytes:15191740,},ContainerImage{Names:[k8s.gcr.io/coredns@sha256:73ca82b4ce829766d4f1f10947c3a338888f876fbed0540dc849c89ff256e90c k8s.gcr.io/coredns:1.7.0],SizeBytes:13982350,},ContainerImage{Names:[docker.io/library/nginx@sha256:485b610fefec7ff6c463ced9623314a04ed67e3945b9c08d7e53a47f6d108dc7 docker.io/library/nginx:1.14-alpine],SizeBytes:6978806,},ContainerImage{Names:[docker.io/library/busybox@sha256:8ccbac733d19c0dd4d70b4f0c1e12245b5fa3ad24758a11035ee505c629c0796 docker.io/library/busybox:1.29],SizeBytes:732685,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:299513,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
... skipping 203 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 [It]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:151

      Jul 30 11:57:25.824: Unexpected error:
          <exec.CodeExitError>: {
              Err: {
                  s: "command terminated with exit code 1",
              },
              Code: 1,
          }
... skipping 86 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/framework.go:23
  With a server listening on 0.0.0.0
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/portforward.go:452
    should support forwarding over websockets
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/portforward.go:468
------------------------------
{"msg":"PASSED [sig-cli] Kubectl Port forwarding With a server listening on 0.0.0.0 should support forwarding over websockets","total":-1,"completed":2,"skipped":17,"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
Jul 30 11:57:34.924: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 53 lines ...
• [SLOW TEST:63.429 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 add, update, and delete watch notifications on configmaps [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 add, update, and delete watch notifications on configmaps [Conformance]","total":-1,"completed":3,"skipped":33,"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
Jul 30 11:57:39.782: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 148 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Dynamic 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: Dynamic PV (ext4)] volumes should store data","total":-1,"completed":2,"skipped":15,"failed":0}

SS
------------------------------
[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
Jul 30 11:57:40.058: INFO: Driver hostPathSymlink doesn't support PreprovisionedPV -- skipping
... skipping 65 lines ...
Jul 30 11:57:27.512: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename svcaccounts
STEP: Waiting for a default service account to be provisioned in namespace
[It] should set ownership and permission when RunAsUser or FsGroup is present [LinuxOnly] [NodeFeature:FSGroup]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/auth/service_accounts.go:488
STEP: Creating a pod to test service account token: 
Jul 30 11:57:28.648: INFO: Waiting up to 5m0s for pod "test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09" in namespace "svcaccounts-6410" to be "Succeeded or Failed"
Jul 30 11:57:28.837: INFO: Pod "test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09": Phase="Pending", Reason="", readiness=false. Elapsed: 188.520309ms
Jul 30 11:57:31.026: INFO: Pod "test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.377759562s
STEP: Saw pod success
Jul 30 11:57:31.026: INFO: Pod "test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09" satisfied condition "Succeeded or Failed"
Jul 30 11:57:31.215: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09 container agnhost-container: <nil>
STEP: delete the pod
Jul 30 11:57:31.600: INFO: Waiting for pod test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09 to disappear
Jul 30 11:57:31.788: INFO: Pod test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09 no longer exists
STEP: Creating a pod to test service account token: 
Jul 30 11:57:31.978: INFO: Waiting up to 5m0s for pod "test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09" in namespace "svcaccounts-6410" to be "Succeeded or Failed"
Jul 30 11:57:32.167: INFO: Pod "test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09": Phase="Pending", Reason="", readiness=false. Elapsed: 188.538574ms
Jul 30 11:57:34.356: INFO: Pod "test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.37767703s
STEP: Saw pod success
Jul 30 11:57:34.356: INFO: Pod "test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09" satisfied condition "Succeeded or Failed"
Jul 30 11:57:34.546: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09 container agnhost-container: <nil>
STEP: delete the pod
Jul 30 11:57:34.929: INFO: Waiting for pod test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09 to disappear
Jul 30 11:57:35.146: INFO: Pod test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09 no longer exists
STEP: Creating a pod to test service account token: 
Jul 30 11:57:35.336: INFO: Waiting up to 5m0s for pod "test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09" in namespace "svcaccounts-6410" to be "Succeeded or Failed"
Jul 30 11:57:35.532: INFO: Pod "test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09": Phase="Pending", Reason="", readiness=false. Elapsed: 195.986967ms
Jul 30 11:57:37.724: INFO: Pod "test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.387657798s
STEP: Saw pod success
Jul 30 11:57:37.724: INFO: Pod "test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09" satisfied condition "Succeeded or Failed"
Jul 30 11:57:37.915: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09 container agnhost-container: <nil>
STEP: delete the pod
Jul 30 11:57:38.323: INFO: Waiting for pod test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09 to disappear
Jul 30 11:57:38.512: INFO: Pod test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09 no longer exists
STEP: Creating a pod to test service account token: 
Jul 30 11:57:38.703: INFO: Waiting up to 5m0s for pod "test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09" in namespace "svcaccounts-6410" to be "Succeeded or Failed"
Jul 30 11:57:38.893: INFO: Pod "test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09": Phase="Pending", Reason="", readiness=false. Elapsed: 189.076767ms
Jul 30 11:57:41.082: INFO: Pod "test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09": Phase="Pending", Reason="", readiness=false. Elapsed: 2.378212157s
Jul 30 11:57:43.271: INFO: Pod "test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09": Phase="Pending", Reason="", readiness=false. Elapsed: 4.5673188s
Jul 30 11:57:45.460: INFO: Pod "test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.7569342s
STEP: Saw pod success
Jul 30 11:57:45.461: INFO: Pod "test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09" satisfied condition "Succeeded or Failed"
Jul 30 11:57:45.650: INFO: Trying to get logs from node ip-172-20-33-146.ap-southeast-2.compute.internal pod test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09 container agnhost-container: <nil>
STEP: delete the pod
Jul 30 11:57:46.039: INFO: Waiting for pod test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09 to disappear
Jul 30 11:57:46.228: INFO: Pod test-pod-9f06975e-04b3-4149-a498-8bfcb58abd09 no longer exists
[AfterEach] [sig-auth] ServiceAccounts
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 4 lines ...
• [SLOW TEST:19.096 seconds]
[sig-auth] ServiceAccounts
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/auth/framework.go:23
  should set ownership and permission when RunAsUser or FsGroup is present [LinuxOnly] [NodeFeature:FSGroup]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/auth/service_accounts.go:488
------------------------------
{"msg":"PASSED [sig-auth] ServiceAccounts should set ownership and permission when RunAsUser or FsGroup is present [LinuxOnly] [NodeFeature:FSGroup]","total":-1,"completed":5,"skipped":44,"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
Jul 30 11:57:46.623: INFO: Only supported for providers [gce gke] (not aws)
... skipping 22 lines ...
STEP: Building a namespace api object, basename configmap
STEP: Waiting for a default service account to be provisioned in namespace
[It] should be consumable from pods in volume as non-root with defaultMode and fsGroup set [LinuxOnly] [NodeFeature:FSGroup]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/configmap_volume.go:59
STEP: Creating configMap with name configmap-test-volume-5bd9e0df-6717-453c-9e78-359c6b894cce
STEP: Creating a pod to test consume configMaps
Jul 30 11:57:41.418: INFO: Waiting up to 5m0s for pod "pod-configmaps-cddee140-e091-4b2b-852b-4f2242ecdda3" in namespace "configmap-357" to be "Succeeded or Failed"
Jul 30 11:57:41.608: INFO: Pod "pod-configmaps-cddee140-e091-4b2b-852b-4f2242ecdda3": Phase="Pending", Reason="", readiness=false. Elapsed: 189.686861ms
Jul 30 11:57:43.798: INFO: Pod "pod-configmaps-cddee140-e091-4b2b-852b-4f2242ecdda3": Phase="Pending", Reason="", readiness=false. Elapsed: 2.379808534s
Jul 30 11:57:45.988: INFO: Pod "pod-configmaps-cddee140-e091-4b2b-852b-4f2242ecdda3": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.569881896s
STEP: Saw pod success
Jul 30 11:57:45.988: INFO: Pod "pod-configmaps-cddee140-e091-4b2b-852b-4f2242ecdda3" satisfied condition "Succeeded or Failed"
Jul 30 11:57:46.178: INFO: Trying to get logs from node ip-172-20-33-146.ap-southeast-2.compute.internal pod pod-configmaps-cddee140-e091-4b2b-852b-4f2242ecdda3 container agnhost-container: <nil>
STEP: delete the pod
Jul 30 11:57:46.565: INFO: Waiting for pod pod-configmaps-cddee140-e091-4b2b-852b-4f2242ecdda3 to disappear
Jul 30 11:57:46.755: INFO: Pod pod-configmaps-cddee140-e091-4b2b-852b-4f2242ecdda3 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
... skipping 4 lines ...
• [SLOW TEST:7.052 seconds]
[sig-storage] ConfigMap
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/configmap_volume.go:36
  should be consumable from pods in volume as non-root with defaultMode and fsGroup set [LinuxOnly] [NodeFeature:FSGroup]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/configmap_volume.go:59
------------------------------
{"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume as non-root with defaultMode and fsGroup set [LinuxOnly] [NodeFeature:FSGroup]","total":-1,"completed":3,"skipped":21,"failed":0}

SSS
------------------------------
[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
Jul 30 11:57:47.160: INFO: Driver local doesn't support InlineVolume -- skipping
... skipping 41 lines ...
Jul 30 11:57:34.886: INFO: PersistentVolumeClaim pvc-c4ldb found but phase is Pending instead of Bound.
Jul 30 11:57:37.075: INFO: PersistentVolumeClaim pvc-c4ldb found and phase=Bound (13.34287739s)
Jul 30 11:57:37.075: INFO: Waiting up to 3m0s for PersistentVolume local-mb795 to have phase Bound
Jul 30 11:57:37.263: INFO: PersistentVolume local-mb795 found and phase=Bound (187.879358ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-qbr5
STEP: Creating a pod to test subpath
Jul 30 11:57:37.829: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-qbr5" in namespace "provisioning-3618" to be "Succeeded or Failed"
Jul 30 11:57:38.017: INFO: Pod "pod-subpath-test-preprovisionedpv-qbr5": Phase="Pending", Reason="", readiness=false. Elapsed: 188.329827ms
Jul 30 11:57:40.206: INFO: Pod "pod-subpath-test-preprovisionedpv-qbr5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.377057074s
Jul 30 11:57:42.395: INFO: Pod "pod-subpath-test-preprovisionedpv-qbr5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.565798815s
STEP: Saw pod success
Jul 30 11:57:42.395: INFO: Pod "pod-subpath-test-preprovisionedpv-qbr5" satisfied condition "Succeeded or Failed"
Jul 30 11:57:42.583: INFO: Trying to get logs from node ip-172-20-35-124.ap-southeast-2.compute.internal pod pod-subpath-test-preprovisionedpv-qbr5 container test-container-subpath-preprovisionedpv-qbr5: <nil>
STEP: delete the pod
Jul 30 11:57:42.972: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-qbr5 to disappear
Jul 30 11:57:43.160: INFO: Pod pod-subpath-test-preprovisionedpv-qbr5 no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-qbr5
Jul 30 11:57:43.160: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-qbr5" in namespace "provisioning-3618"
STEP: Creating pod pod-subpath-test-preprovisionedpv-qbr5
STEP: Creating a pod to test subpath
Jul 30 11:57:43.538: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-qbr5" in namespace "provisioning-3618" to be "Succeeded or Failed"
Jul 30 11:57:43.727: INFO: Pod "pod-subpath-test-preprovisionedpv-qbr5": Phase="Pending", Reason="", readiness=false. Elapsed: 188.202925ms
Jul 30 11:57:45.916: INFO: Pod "pod-subpath-test-preprovisionedpv-qbr5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.377981262s
STEP: Saw pod success
Jul 30 11:57:45.916: INFO: Pod "pod-subpath-test-preprovisionedpv-qbr5" satisfied condition "Succeeded or Failed"
Jul 30 11:57:46.105: INFO: Trying to get logs from node ip-172-20-35-124.ap-southeast-2.compute.internal pod pod-subpath-test-preprovisionedpv-qbr5 container test-container-subpath-preprovisionedpv-qbr5: <nil>
STEP: delete the pod
Jul 30 11:57:46.487: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-qbr5 to disappear
Jul 30 11:57:46.675: INFO: Pod pod-subpath-test-preprovisionedpv-qbr5 no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-qbr5
Jul 30 11:57:46.676: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-qbr5" in namespace "provisioning-3618"
... 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":6,"skipped":41,"failed":0}

SSSSSSSS
------------------------------
[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 18 lines ...
Jul 30 11:57:33.963: INFO: PersistentVolumeClaim pvc-bc9dg found but phase is Pending instead of Bound.
Jul 30 11:57:36.164: INFO: PersistentVolumeClaim pvc-bc9dg found and phase=Bound (2.391118222s)
Jul 30 11:57:36.164: INFO: Waiting up to 3m0s for PersistentVolume local-s79d9 to have phase Bound
Jul 30 11:57:36.355: INFO: PersistentVolume local-s79d9 found and phase=Bound (190.763008ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-kttv
STEP: Creating a pod to test subpath
Jul 30 11:57:36.928: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-kttv" in namespace "provisioning-3853" to be "Succeeded or Failed"
Jul 30 11:57:37.119: INFO: Pod "pod-subpath-test-preprovisionedpv-kttv": Phase="Pending", Reason="", readiness=false. Elapsed: 190.822624ms
Jul 30 11:57:39.310: INFO: Pod "pod-subpath-test-preprovisionedpv-kttv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.381856473s
Jul 30 11:57:41.501: INFO: Pod "pod-subpath-test-preprovisionedpv-kttv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.572998974s
Jul 30 11:57:43.692: INFO: Pod "pod-subpath-test-preprovisionedpv-kttv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.764247094s
STEP: Saw pod success
Jul 30 11:57:43.692: INFO: Pod "pod-subpath-test-preprovisionedpv-kttv" satisfied condition "Succeeded or Failed"
Jul 30 11:57:43.883: INFO: Trying to get logs from node ip-172-20-33-146.ap-southeast-2.compute.internal pod pod-subpath-test-preprovisionedpv-kttv container test-container-subpath-preprovisionedpv-kttv: <nil>
STEP: delete the pod
Jul 30 11:57:44.273: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-kttv to disappear
Jul 30 11:57:44.464: INFO: Pod pod-subpath-test-preprovisionedpv-kttv no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-kttv
Jul 30 11:57:44.464: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-kttv" in namespace "provisioning-3853"
... 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 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: block] [Testpattern: Pre-provisioned PV (default fs)] subPath should support readOnly directory specified in the volumeMount","total":-1,"completed":5,"skipped":68,"failed":1,"failures":["[sig-storage] PersistentVolumes-local  [Volume type: dir-link-bindmounted] Two pods mounting a local volume at the same time should be able to write from pod1 and read from pod2"]}

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
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 21 lines ...
Jul 30 11:57:34.713: INFO: PersistentVolumeClaim pvc-d2xwd found but phase is Pending instead of Bound.
Jul 30 11:57:36.905: INFO: PersistentVolumeClaim pvc-d2xwd found and phase=Bound (15.541894901s)
Jul 30 11:57:36.905: INFO: Waiting up to 3m0s for PersistentVolume local-gq7rg to have phase Bound
Jul 30 11:57:37.097: INFO: PersistentVolume local-gq7rg found and phase=Bound (192.092402ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-pr5m
STEP: Creating a pod to test subpath
Jul 30 11:57:37.675: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-pr5m" in namespace "provisioning-8234" to be "Succeeded or Failed"
Jul 30 11:57:37.868: INFO: Pod "pod-subpath-test-preprovisionedpv-pr5m": Phase="Pending", Reason="", readiness=false. Elapsed: 192.360081ms
Jul 30 11:57:40.060: INFO: Pod "pod-subpath-test-preprovisionedpv-pr5m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.384954159s
Jul 30 11:57:42.254: INFO: Pod "pod-subpath-test-preprovisionedpv-pr5m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.578923468s
Jul 30 11:57:44.447: INFO: Pod "pod-subpath-test-preprovisionedpv-pr5m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.771582932s
Jul 30 11:57:46.641: INFO: Pod "pod-subpath-test-preprovisionedpv-pr5m": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.965482038s
STEP: Saw pod success
Jul 30 11:57:46.641: INFO: Pod "pod-subpath-test-preprovisionedpv-pr5m" satisfied condition "Succeeded or Failed"
Jul 30 11:57:46.835: INFO: Trying to get logs from node ip-172-20-33-146.ap-southeast-2.compute.internal pod pod-subpath-test-preprovisionedpv-pr5m container test-container-subpath-preprovisionedpv-pr5m: <nil>
STEP: delete the pod
Jul 30 11:57:47.226: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-pr5m to disappear
Jul 30 11:57:47.418: INFO: Pod pod-subpath-test-preprovisionedpv-pr5m no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-pr5m
Jul 30 11:57:47.418: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-pr5m" in namespace "provisioning-8234"
... 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":44,"failed":0}

SS
------------------------------
[BeforeEach] [sig-storage] ConfigMap
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 15 lines ...
• [SLOW TEST:70.711 seconds]
[sig-storage] ConfigMap
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/configmap_volume.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] ConfigMap updates should be reflected in volume [NodeConformance] [Conformance]","total":-1,"completed":2,"skipped":19,"failed":1,"failures":["[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]"]}

SS
------------------------------
[BeforeEach] [sig-scheduling] Multi-AZ Clusters
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 68 lines ...
• [SLOW TEST:139.531 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":1,"skipped":6,"failed":0}

SSSSSSS
------------------------------
[BeforeEach] [sig-auth] ServiceAccounts
  /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 ...
Jul 30 11:57:23.393: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-640-aws-scllcc4
STEP: creating a claim
Jul 30 11:57:23.583: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-wnrn
STEP: Creating a pod to test exec-volume-test
Jul 30 11:57:24.189: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-wnrn" in namespace "volume-640" to be "Succeeded or Failed"
Jul 30 11:57:24.387: INFO: Pod "exec-volume-test-dynamicpv-wnrn": Phase="Pending", Reason="", readiness=false. Elapsed: 197.275871ms
Jul 30 11:57:26.577: INFO: Pod "exec-volume-test-dynamicpv-wnrn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.38773292s
Jul 30 11:57:28.767: INFO: Pod "exec-volume-test-dynamicpv-wnrn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.578081944s
Jul 30 11:57:30.958: INFO: Pod "exec-volume-test-dynamicpv-wnrn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.768354174s
Jul 30 11:57:33.148: INFO: Pod "exec-volume-test-dynamicpv-wnrn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.958682478s
Jul 30 11:57:35.340: INFO: Pod "exec-volume-test-dynamicpv-wnrn": Phase="Pending", Reason="", readiness=false. Elapsed: 11.151040172s
Jul 30 11:57:37.533: INFO: Pod "exec-volume-test-dynamicpv-wnrn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.343244842s
STEP: Saw pod success
Jul 30 11:57:37.533: INFO: Pod "exec-volume-test-dynamicpv-wnrn" satisfied condition "Succeeded or Failed"
Jul 30 11:57:37.730: INFO: Trying to get logs from node ip-172-20-45-65.ap-southeast-2.compute.internal pod exec-volume-test-dynamicpv-wnrn container exec-container-dynamicpv-wnrn: <nil>
STEP: delete the pod
Jul 30 11:57:38.124: INFO: Waiting for pod exec-volume-test-dynamicpv-wnrn to disappear
Jul 30 11:57:38.322: INFO: Pod exec-volume-test-dynamicpv-wnrn no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-wnrn
Jul 30 11:57:38.322: INFO: Deleting pod "exec-volume-test-dynamicpv-wnrn" in namespace "volume-640"
... skipping 18 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/in_tree_volumes.go:57
    [Testpattern: Dynamic PV (ext4)] 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: Dynamic PV (ext4)] volumes should allow exec of files on the volume","total":-1,"completed":3,"skipped":18,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a validating webhook should work [Conformance]"]}

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
Jul 30 11:57:55.445: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
... 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
Jul 30 11:57:52.714: INFO: Waiting up to 5m0s for pod "downwardapi-volume-069bf186-cd73-458c-9383-48987271c514" in namespace "downward-api-9587" to be "Succeeded or Failed"
Jul 30 11:57:52.909: INFO: Pod "downwardapi-volume-069bf186-cd73-458c-9383-48987271c514": Phase="Pending", Reason="", readiness=false. Elapsed: 194.616999ms
Jul 30 11:57:55.102: INFO: Pod "downwardapi-volume-069bf186-cd73-458c-9383-48987271c514": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.387422059s
STEP: Saw pod success
Jul 30 11:57:55.102: INFO: Pod "downwardapi-volume-069bf186-cd73-458c-9383-48987271c514" satisfied condition "Succeeded or Failed"
Jul 30 11:57:55.294: INFO: Trying to get logs from node ip-172-20-35-124.ap-southeast-2.compute.internal pod downwardapi-volume-069bf186-cd73-458c-9383-48987271c514 container client-container: <nil>
STEP: delete the pod
Jul 30 11:57:55.700: INFO: Waiting for pod downwardapi-volume-069bf186-cd73-458c-9383-48987271c514 to disappear
Jul 30 11:57:55.893: INFO: Pod downwardapi-volume-069bf186-cd73-458c-9383-48987271c514 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
Jul 30 11:57:55.893: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "downward-api-9587" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] Downward API volume should set mode on item file [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":9,"skipped":47,"failed":0}

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
Jul 30 11:57:56.295: INFO: Driver csi-hostpath doesn't support PreprovisionedPV -- skipping
... skipping 125 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 11:57:57.643: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "pods-579" for this suite.

•
------------------------------
{"msg":"PASSED [k8s.io] Pods should delete a collection of pods [Conformance]","total":-1,"completed":4,"skipped":27,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a validating webhook should work [Conformance]"]}

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
Jul 30 11:57:58.040: INFO: Driver local doesn't support InlineVolume -- skipping
... skipping 37 lines ...
      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
------------------------------
S
------------------------------
{"msg":"PASSED [k8s.io] [sig-node] Security Context should support seccomp runtime/default [LinuxOnly]","total":-1,"completed":5,"skipped":46,"failed":0}
[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
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Jul 30 11:57:25.122: INFO: >>> kubeConfig: /root/.kube/config
... skipping 41 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)] 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: Dynamic PV (block volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]","total":-1,"completed":6,"skipped":46,"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
Jul 30 11:57:59.173: INFO: Driver supports dynamic provisioning, skipping InlineVolume pattern
... skipping 164 lines ...
Jul 30 11:58:06.874: INFO: AfterEach: Cleaning up test resources.
Jul 30 11:58:06.874: INFO: pvc is nil
Jul 30 11:58:06.874: INFO: Deleting PersistentVolume "hostpath-rdbn5"

•
------------------------------
{"msg":"PASSED [sig-storage] PV Protection Verify \"immediate\" deletion of a PV that is not bound to a PVC","total":-1,"completed":3,"skipped":28,"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 9 lines ...
Jul 30 11:57:40.785: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3484-aws-scv5t4w
STEP: creating a claim
Jul 30 11:57:40.977: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-4fxw
STEP: Creating a pod to test subpath
Jul 30 11:57:41.553: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-4fxw" in namespace "provisioning-3484" to be "Succeeded or Failed"
Jul 30 11:57:41.743: INFO: Pod "pod-subpath-test-dynamicpv-4fxw": Phase="Pending", Reason="", readiness=false. Elapsed: 189.932132ms
Jul 30 11:57:43.933: INFO: Pod "pod-subpath-test-dynamicpv-4fxw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.379994519s
Jul 30 11:57:46.123: INFO: Pod "pod-subpath-test-dynamicpv-4fxw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.570130735s
Jul 30 11:57:48.316: INFO: Pod "pod-subpath-test-dynamicpv-4fxw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.762971608s
Jul 30 11:57:50.509: INFO: Pod "pod-subpath-test-dynamicpv-4fxw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.956053284s
Jul 30 11:57:52.699: INFO: Pod "pod-subpath-test-dynamicpv-4fxw": Phase="Pending", Reason="", readiness=false. Elapsed: 11.145911252s
Jul 30 11:57:54.890: INFO: Pod "pod-subpath-test-dynamicpv-4fxw": Phase="Pending", Reason="", readiness=false. Elapsed: 13.337122668s
Jul 30 11:57:57.081: INFO: Pod "pod-subpath-test-dynamicpv-4fxw": Phase="Pending", Reason="", readiness=false. Elapsed: 15.52758825s
Jul 30 11:57:59.271: INFO: Pod "pod-subpath-test-dynamicpv-4fxw": Phase="Pending", Reason="", readiness=false. Elapsed: 17.717989214s
Jul 30 11:58:01.463: INFO: Pod "pod-subpath-test-dynamicpv-4fxw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.910325733s
STEP: Saw pod success
Jul 30 11:58:01.463: INFO: Pod "pod-subpath-test-dynamicpv-4fxw" satisfied condition "Succeeded or Failed"
Jul 30 11:58:01.654: INFO: Trying to get logs from node ip-172-20-33-146.ap-southeast-2.compute.internal pod pod-subpath-test-dynamicpv-4fxw container test-container-volume-dynamicpv-4fxw: <nil>
STEP: delete the pod
Jul 30 11:58:02.040: INFO: Waiting for pod pod-subpath-test-dynamicpv-4fxw to disappear
Jul 30 11:58:02.230: INFO: Pod pod-subpath-test-dynamicpv-4fxw no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-4fxw
Jul 30 11:58:02.230: INFO: Deleting pod "pod-subpath-test-dynamicpv-4fxw" in namespace "provisioning-3484"
... skipping 18 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":4,"skipped":45,"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
Jul 30 11:58:09.153: INFO: Only supported for providers [gce gke] (not aws)
... skipping 59 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":7,"skipped":49,"failed":0}

S
------------------------------
[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 58 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 DATA, and disconnects
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/portforward.go:479
------------------------------
{"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 DATA, and disconnects","total":-1,"completed":10,"skipped":106,"failed":0}
[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
Jul 30 11:58:10.823: INFO: Driver local doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (default fs)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 157 lines ...
Jul 30 11:58:05.864: INFO: PersistentVolumeClaim pvc-qdr78 found but phase is Pending instead of Bound.
Jul 30 11:58:08.055: INFO: PersistentVolumeClaim pvc-qdr78 found and phase=Bound (11.157142668s)
Jul 30 11:58:08.055: INFO: Waiting up to 3m0s for PersistentVolume local-gzkt5 to have phase Bound
Jul 30 11:58:08.245: INFO: PersistentVolume local-gzkt5 found and phase=Bound (190.546343ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-4zvq
STEP: Creating a pod to test subpath
Jul 30 11:58:08.821: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-4zvq" in namespace "provisioning-6263" to be "Succeeded or Failed"
Jul 30 11:58:09.012: INFO: Pod "pod-subpath-test-preprovisionedpv-4zvq": Phase="Pending", Reason="", readiness=false. Elapsed: 190.689295ms
Jul 30 11:58:11.203: INFO: Pod "pod-subpath-test-preprovisionedpv-4zvq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.381703011s
STEP: Saw pod success
Jul 30 11:58:11.203: INFO: Pod "pod-subpath-test-preprovisionedpv-4zvq" satisfied condition "Succeeded or Failed"
Jul 30 11:58:11.394: INFO: Trying to get logs from node ip-172-20-45-65.ap-southeast-2.compute.internal pod pod-subpath-test-preprovisionedpv-4zvq container test-container-subpath-preprovisionedpv-4zvq: <nil>
STEP: delete the pod
Jul 30 11:58:11.782: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-4zvq to disappear
Jul 30 11:58:11.972: INFO: Pod pod-subpath-test-preprovisionedpv-4zvq no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-4zvq
Jul 30 11:58:11.972: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-4zvq" in namespace "provisioning-6263"
... 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":6,"skipped":71,"failed":1,"failures":["[sig-storage] PersistentVolumes-local  [Volume type: dir-link-bindmounted] Two pods mounting a local volume at the same time should be able to write from pod1 and read from pod2"]}
[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
Jul 30 11:58:14.554: INFO: Only supported for providers [gce gke] (not aws)
[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 69 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/framework.go:23
  Simple pod
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:382
    should support exec through kubectl proxy
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:476
------------------------------
{"msg":"FAILED [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: blockfs] [Testpattern: Pre-provisioned PV (default fs)] volumes should store data","total":-1,"completed":1,"skipped":6,"failed":1,"failures":["[sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: blockfs] [Testpattern: Pre-provisioned PV (default fs)] volumes should store data"]}
[BeforeEach] [sig-storage] Mounted volume expand
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Jul 30 11:57:33.636: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename mounted-volume-expand
STEP: Waiting for a default service account to be provisioned in namespace
... skipping 44 lines ...
• [SLOW TEST:48.298 seconds]
[sig-storage] Mounted volume expand
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  Should verify mounted devices can be resized
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/mounted_volume_resize.go:116
------------------------------
{"msg":"PASSED [sig-storage] Mounted volume expand Should verify mounted devices can be resized","total":-1,"completed":2,"skipped":6,"failed":1,"failures":["[sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: blockfs] [Testpattern: Pre-provisioned PV (default fs)] volumes should store data"]}

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
Jul 30 11:58:14.572: 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 as non-root with defaultMode and fsGroup 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-f7648701-1fa6-48a0-b2eb-c4b28960cad0
STEP: Creating a pod to test consume secrets
Jul 30 11:58:15.915: INFO: Waiting up to 5m0s for pod "pod-secrets-584e3c31-9e04-4754-875d-606c694af033" in namespace "secrets-9445" to be "Succeeded or Failed"
Jul 30 11:58:16.106: INFO: Pod "pod-secrets-584e3c31-9e04-4754-875d-606c694af033": Phase="Pending", Reason="", readiness=false. Elapsed: 190.895973ms
Jul 30 11:58:18.297: INFO: Pod "pod-secrets-584e3c31-9e04-4754-875d-606c694af033": Phase="Pending", Reason="", readiness=false. Elapsed: 2.381605795s
Jul 30 11:58:20.488: INFO: Pod "pod-secrets-584e3c31-9e04-4754-875d-606c694af033": Phase="Running", Reason="", readiness=true. Elapsed: 4.572388959s
Jul 30 11:58:22.679: INFO: Pod "pod-secrets-584e3c31-9e04-4754-875d-606c694af033": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.763291403s
STEP: Saw pod success
Jul 30 11:58:22.679: INFO: Pod "pod-secrets-584e3c31-9e04-4754-875d-606c694af033" satisfied condition "Succeeded or Failed"
Jul 30 11:58:22.869: INFO: Trying to get logs from node ip-172-20-35-124.ap-southeast-2.compute.internal pod pod-secrets-584e3c31-9e04-4754-875d-606c694af033 container secret-volume-test: <nil>
STEP: delete the pod
Jul 30 11:58:23.256: INFO: Waiting for pod pod-secrets-584e3c31-9e04-4754-875d-606c694af033 to disappear
Jul 30 11:58:23.447: INFO: Pod pod-secrets-584e3c31-9e04-4754-875d-606c694af033 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:9.258 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 as non-root with defaultMode and fsGroup 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 as non-root with defaultMode and fsGroup set [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":7,"skipped":75,"failed":1,"failures":["[sig-storage] PersistentVolumes-local  [Volume type: dir-link-bindmounted] Two pods mounting a local volume at the same time should be able to write from pod1 and read from pod2"]}
[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
Jul 30 11:58:23.839: 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 270 lines ...
• [SLOW TEST:49.604 seconds]
[sig-apps] Deployment
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23
  iterative rollouts should eventually progress
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/deployment.go:129
------------------------------
{"msg":"PASSED [sig-apps] Deployment iterative rollouts should eventually progress","total":-1,"completed":4,"skipped":24,"failed":0}

S
------------------------------
[BeforeEach] [sig-storage] Downward API 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 2 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 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
Jul 30 11:58:23.087: INFO: Waiting up to 5m0s for pod "downwardapi-volume-5ec92a3c-a7e4-436d-8191-195b54389cd2" in namespace "downward-api-7056" to be "Succeeded or Failed"
Jul 30 11:58:23.276: INFO: Pod "downwardapi-volume-5ec92a3c-a7e4-436d-8191-195b54389cd2": Phase="Pending", Reason="", readiness=false. Elapsed: 189.713268ms
Jul 30 11:58:25.467: INFO: Pod "downwardapi-volume-5ec92a3c-a7e4-436d-8191-195b54389cd2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.380001922s
STEP: Saw pod success
Jul 30 11:58:25.467: INFO: Pod "downwardapi-volume-5ec92a3c-a7e4-436d-8191-195b54389cd2" satisfied condition "Succeeded or Failed"
Jul 30 11:58:25.667: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod downwardapi-volume-5ec92a3c-a7e4-436d-8191-195b54389cd2 container client-container: <nil>
STEP: delete the pod
Jul 30 11:58:26.055: INFO: Waiting for pod downwardapi-volume-5ec92a3c-a7e4-436d-8191-195b54389cd2 to disappear
Jul 30 11:58:26.244: INFO: Pod downwardapi-volume-5ec92a3c-a7e4-436d-8191-195b54389cd2 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 70 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":8,"skipped":50,"failed":0}

SS
------------------------------
[BeforeEach] [sig-apps] ReplicationController
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 11 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 11:58:28.097: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "replication-controller-3024" for this suite.

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

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
Jul 30 11:58:28.501: INFO: Driver hostPath doesn't support DynamicPV -- skipping
... skipping 110 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: blockfswithoutformat] Two pods mounting a local volume one after the other should be able to write from pod1 and read from pod2","total":-1,"completed":11,"skipped":107,"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
Jul 30 11:58:32.985: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 96 lines ...
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [k8s.io] Sysctls [LinuxOnly] [NodeFeature:Sysctls]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/sysctl.go:64
[It] should support sysctls
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/sysctl.go:68
STEP: Creating a pod with the kernel.shm_rmid_forced sysctl
STEP: Watching for error events or started pod
STEP: Waiting for pod completion
STEP: Checking that the pod succeeded
STEP: Getting logs from the pod
STEP: Checking that the sysctl is actually updated
[AfterEach] [k8s.io] Sysctls [LinuxOnly] [NodeFeature:Sysctls]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 4 lines ...
• [SLOW TEST:6.469 seconds]
[k8s.io] Sysctls [LinuxOnly] [NodeFeature:Sysctls]
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  should support sysctls
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/sysctl.go:68
------------------------------
{"msg":"PASSED [k8s.io] Sysctls [LinuxOnly] [NodeFeature:Sysctls] should support sysctls","total":-1,"completed":6,"skipped":34,"failed":0}

SSS
------------------------------
[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
Jul 30 11:58:35.022: INFO: Driver hostPathSymlink doesn't support DynamicPV -- skipping
... skipping 221 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: block] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]","total":-1,"completed":5,"skipped":34,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a validating webhook should work [Conformance]"]}

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
Jul 30 11:58:45.437: INFO: Driver aws doesn't support ext3 -- skipping
... skipping 73 lines ...
• [SLOW TEST:21.731 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 at the schema root [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 at the schema root [Conformance]","total":-1,"completed":8,"skipped":95,"failed":1,"failures":["[sig-storage] PersistentVolumes-local  [Volume type: dir-link-bindmounted] Two pods mounting a local volume at the same time should be able to write from pod1 and read from pod2"]}

S
------------------------------
[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
Jul 30 11:58:45.688: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 33 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 11:58:47.365: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "replication-controller-1163" for this suite.

•
------------------------------
{"msg":"PASSED [sig-apps] ReplicationController should release no longer matching pods [Conformance]","total":-1,"completed":6,"skipped":42,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a validating webhook should work [Conformance]"]}

S
------------------------------
{"msg":"PASSED [sig-storage] Downward API volume should set DefaultMode on files [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":3,"skipped":7,"failed":1,"failures":["[sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: blockfs] [Testpattern: Pre-provisioned PV (default fs)] volumes should store data"]}
[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
Jul 30 11:58:26.633: INFO: >>> kubeConfig: /root/.kube/config
... skipping 16 lines ...
Jul 30 11:58:35.614: INFO: PersistentVolumeClaim pvc-x5jtv found but phase is Pending instead of Bound.
Jul 30 11:58:37.804: INFO: PersistentVolumeClaim pvc-x5jtv found and phase=Bound (4.567699883s)
Jul 30 11:58:37.804: INFO: Waiting up to 3m0s for PersistentVolume local-4c8vr to have phase Bound
Jul 30 11:58:37.994: INFO: PersistentVolume local-4c8vr found and phase=Bound (190.099107ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-p864
STEP: Creating a pod to test subpath
Jul 30 11:58:38.561: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-p864" in namespace "provisioning-1829" to be "Succeeded or Failed"
Jul 30 11:58:38.750: INFO: Pod "pod-subpath-test-preprovisionedpv-p864": Phase="Pending", Reason="", readiness=false. Elapsed: 188.817693ms
Jul 30 11:58:40.940: INFO: Pod "pod-subpath-test-preprovisionedpv-p864": Phase="Pending", Reason="", readiness=false. Elapsed: 2.378360683s
Jul 30 11:58:43.130: INFO: Pod "pod-subpath-test-preprovisionedpv-p864": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.568797524s
STEP: Saw pod success
Jul 30 11:58:43.130: INFO: Pod "pod-subpath-test-preprovisionedpv-p864" satisfied condition "Succeeded or Failed"
Jul 30 11:58:43.319: INFO: Trying to get logs from node ip-172-20-45-65.ap-southeast-2.compute.internal pod pod-subpath-test-preprovisionedpv-p864 container test-container-subpath-preprovisionedpv-p864: <nil>
STEP: delete the pod
Jul 30 11:58:43.708: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-p864 to disappear
Jul 30 11:58:43.897: INFO: Pod pod-subpath-test-preprovisionedpv-p864 no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-p864
Jul 30 11:58:43.897: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-p864" in namespace "provisioning-1829"
... skipping 165 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":8,"skipped":75,"failed":0}
[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
Jul 30 11:58:51.102: INFO: Driver local doesn't support ext3 -- skipping
[AfterEach] [Testpattern: Pre-provisioned PV (ext3)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 45 lines ...
• [SLOW TEST:6.509 seconds]
[sig-apps] Deployment
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23
  deployment reaping should cascade to its replica sets and pods
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/deployment.go:91
------------------------------
{"msg":"PASSED [sig-apps] Deployment deployment reaping should cascade to its replica sets and pods","total":-1,"completed":7,"skipped":43,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a validating webhook should work [Conformance]"]}

SSSSSSSSSS
------------------------------
[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 27 lines ...
• [SLOW TEST:9.212 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 configmap [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 configmap [Conformance]","total":-1,"completed":9,"skipped":80,"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
Jul 30 11:59:00.345: INFO: Only supported for providers [gce gke] (not aws)
[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 53 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:151

      Driver hostPathSymlink doesn't support PreprovisionedPV -- 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 Simple pod should support exec through kubectl proxy","total":-1,"completed":10,"skipped":62,"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
Jul 30 11:58:15.205: 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:47.002 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
  removes definition from spec when one version gets changed to not be served [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] removes definition from spec when one version gets changed to not be served [Conformance]","total":-1,"completed":11,"skipped":62,"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
Jul 30 11:59:02.217: INFO: Driver csi-hostpath 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 151 lines ...
Jul 30 11:58:49.516: INFO: PersistentVolumeClaim pvc-5clxt found but phase is Pending instead of Bound.
Jul 30 11:58:51.705: INFO: PersistentVolumeClaim pvc-5clxt found and phase=Bound (13.322570765s)
Jul 30 11:58:51.705: INFO: Waiting up to 3m0s for PersistentVolume local-wdgfh to have phase Bound
Jul 30 11:58:51.893: INFO: PersistentVolume local-wdgfh found and phase=Bound (188.050579ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-gzhv
STEP: Creating a pod to test subpath
Jul 30 11:58:52.461: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-gzhv" in namespace "provisioning-7675" to be "Succeeded or Failed"
Jul 30 11:58:52.652: INFO: Pod "pod-subpath-test-preprovisionedpv-gzhv": Phase="Pending", Reason="", readiness=false. Elapsed: 190.203514ms
Jul 30 11:58:54.840: INFO: Pod "pod-subpath-test-preprovisionedpv-gzhv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.378819604s
Jul 30 11:58:57.030: INFO: Pod "pod-subpath-test-preprovisionedpv-gzhv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.568293945s
Jul 30 11:58:59.221: INFO: Pod "pod-subpath-test-preprovisionedpv-gzhv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.759475296s
Jul 30 11:59:01.410: INFO: Pod "pod-subpath-test-preprovisionedpv-gzhv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.948158805s
STEP: Saw pod success
Jul 30 11:59:01.410: INFO: Pod "pod-subpath-test-preprovisionedpv-gzhv" satisfied condition "Succeeded or Failed"
Jul 30 11:59:01.598: INFO: Trying to get logs from node ip-172-20-35-124.ap-southeast-2.compute.internal pod pod-subpath-test-preprovisionedpv-gzhv container test-container-volume-preprovisionedpv-gzhv: <nil>
STEP: delete the pod
Jul 30 11:59:01.987: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-gzhv to disappear
Jul 30 11:59:02.175: INFO: Pod pod-subpath-test-preprovisionedpv-gzhv no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-gzhv
Jul 30 11:59:02.175: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-gzhv" in namespace "provisioning-7675"
... 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":12,"skipped":127,"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
Jul 30 11:59:04.830: INFO: Driver csi-hostpath doesn't support ntfs -- skipping
[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 22 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
Jul 30 11:59:03.452: INFO: Waiting up to 5m0s for pod "pod-host-path-test" in namespace "hostpath-7071" to be "Succeeded or Failed"
Jul 30 11:59:03.641: INFO: Pod "pod-host-path-test": Phase="Pending", Reason="", readiness=false. Elapsed: 188.918935ms
Jul 30 11:59:05.831: INFO: Pod "pod-host-path-test": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.37895351s
STEP: Saw pod success
Jul 30 11:59:05.831: INFO: Pod "pod-host-path-test" satisfied condition "Succeeded or Failed"
Jul 30 11:59:06.021: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod pod-host-path-test container test-container-2: <nil>
STEP: delete the pod
Jul 30 11:59:06.406: INFO: Waiting for pod pod-host-path-test to disappear
Jul 30 11:59:06.595: 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
Jul 30 11:59:06.596: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "hostpath-7071" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] HostPath should support subPath [NodeConformance]","total":-1,"completed":12,"skipped":80,"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
Jul 30 11:59:06.990: INFO: Only supported for providers [azure] (not aws)
... skipping 44 lines ...
Jul 30 11:58:49.913: INFO: PersistentVolumeClaim pvc-mghnl found but phase is Pending instead of Bound.
Jul 30 11:58:52.103: INFO: PersistentVolumeClaim pvc-mghnl found and phase=Bound (8.948578989s)
Jul 30 11:58:52.103: INFO: Waiting up to 3m0s for PersistentVolume local-rm2gr to have phase Bound
Jul 30 11:58:52.292: INFO: PersistentVolume local-rm2gr found and phase=Bound (189.295581ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-m6hm
STEP: Creating a pod to test subpath
Jul 30 11:58:52.864: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-m6hm" in namespace "provisioning-7092" to be "Succeeded or Failed"
Jul 30 11:58:53.054: INFO: Pod "pod-subpath-test-preprovisionedpv-m6hm": Phase="Pending", Reason="", readiness=false. Elapsed: 190.543221ms
Jul 30 11:58:55.244: INFO: Pod "pod-subpath-test-preprovisionedpv-m6hm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.380117865s
Jul 30 11:58:57.434: INFO: Pod "pod-subpath-test-preprovisionedpv-m6hm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.569893435s
Jul 30 11:58:59.630: INFO: Pod "pod-subpath-test-preprovisionedpv-m6hm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.766259033s
Jul 30 11:59:01.820: INFO: Pod "pod-subpath-test-preprovisionedpv-m6hm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.956058671s
STEP: Saw pod success
Jul 30 11:59:01.820: INFO: Pod "pod-subpath-test-preprovisionedpv-m6hm" satisfied condition "Succeeded or Failed"
Jul 30 11:59:02.009: INFO: Trying to get logs from node ip-172-20-35-124.ap-southeast-2.compute.internal pod pod-subpath-test-preprovisionedpv-m6hm container test-container-volume-preprovisionedpv-m6hm: <nil>
STEP: delete the pod
Jul 30 11:59:02.395: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-m6hm to disappear
Jul 30 11:59:02.591: INFO: Pod pod-subpath-test-preprovisionedpv-m6hm no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-m6hm
Jul 30 11:59:02.591: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-m6hm" in namespace "provisioning-7092"
... 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-auth] ServiceAccounts should guarantee kube-root-ca.crt exist in any namespace","total":-1,"completed":3,"skipped":21,"failed":1,"failures":["[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]"]}
[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
Jul 30 11:57:53.383: 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 12 lines ...
STEP: Registering a validating webhook on ValidatingWebhookConfiguration and MutatingWebhookConfiguration objects, via the AdmissionRegistration API
Jul 30 11:58:10.830: INFO: Waiting for webhook configuration to be ready...
Jul 30 11:58:21.314: INFO: Waiting for webhook configuration to be ready...
Jul 30 11:58:31.714: INFO: Waiting for webhook configuration to be ready...
Jul 30 11:58:42.113: INFO: Waiting for webhook configuration to be ready...
Jul 30 11:58:52.495: INFO: Waiting for webhook configuration to be ready...
Jul 30 11:58:52.495: FAIL: waiting for webhook configuration to be ready
Unexpected error:
    <*errors.errorString | 0xc000284200>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred

... skipping 483 lines ...
[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] [It]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629

  Jul 30 11:58:52.495: waiting for webhook configuration to be ready
  Unexpected error:
      <*errors.errorString | 0xc000284200>: {
          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/apimachinery/webhook.go:1360
------------------------------
{"msg":"FAILED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should not be able to mutate or prevent deletion of webhook configuration objects [Conformance]","total":-1,"completed":3,"skipped":21,"failed":2,"failures":["[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]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should not be able to mutate or prevent deletion of webhook configuration objects [Conformance]"]}
[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
Jul 30 11:59:10.838: 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 35 lines ...
Jul 30 11:59:04.206: INFO: PersistentVolumeClaim pvc-dpnj5 found but phase is Pending instead of Bound.
Jul 30 11:59:06.396: INFO: PersistentVolumeClaim pvc-dpnj5 found and phase=Bound (6.760655789s)
Jul 30 11:59:06.396: INFO: Waiting up to 3m0s for PersistentVolume local-jzzjp to have phase Bound
Jul 30 11:59:06.586: INFO: PersistentVolume local-jzzjp found and phase=Bound (189.917238ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-4dz9
STEP: Creating a pod to test subpath
Jul 30 11:59:07.158: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-4dz9" in namespace "provisioning-3386" to be "Succeeded or Failed"
Jul 30 11:59:07.348: INFO: Pod "pod-subpath-test-preprovisionedpv-4dz9": Phase="Pending", Reason="", readiness=false. Elapsed: 190.369529ms
Jul 30 11:59:09.539: INFO: Pod "pod-subpath-test-preprovisionedpv-4dz9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.381299559s
Jul 30 11:59:11.751: INFO: Pod "pod-subpath-test-preprovisionedpv-4dz9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.593521797s
STEP: Saw pod success
Jul 30 11:59:11.752: INFO: Pod "pod-subpath-test-preprovisionedpv-4dz9" satisfied condition "Succeeded or Failed"
Jul 30 11:59:11.941: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod pod-subpath-test-preprovisionedpv-4dz9 container test-container-subpath-preprovisionedpv-4dz9: <nil>
STEP: delete the pod
Jul 30 11:59:12.334: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-4dz9 to disappear
Jul 30 11:59:12.524: INFO: Pod pod-subpath-test-preprovisionedpv-4dz9 no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-4dz9
Jul 30 11:59:12.524: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-4dz9" in namespace "provisioning-3386"
... 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-link-bindmounted] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing single file [LinuxOnly]","total":-1,"completed":8,"skipped":53,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a validating webhook should work [Conformance]"]}

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
Jul 30 11:59:15.134: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 31 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 11:59:16.476: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "kubelet-test-3742" for this suite.

•
------------------------------
{"msg":"PASSED [k8s.io] Kubelet when scheduling a busybox command that always fails in a pod should be possible to delete [NodeConformance] [Conformance]","total":-1,"completed":9,"skipped":56,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a validating webhook should work [Conformance]"]}

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
Jul 30 11:59:16.880: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 14 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
------------------------------
SSS
------------------------------
{"msg":"PASSED [sig-cli] Kubectl client Kubectl cluster-info should check if Kubernetes control plane services is included in cluster-info  [Conformance]","total":-1,"completed":4,"skipped":21,"failed":2,"failures":["[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]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should not be able to mutate or prevent deletion of webhook configuration objects [Conformance]"]}
[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
Jul 30 11:59:12.854: 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,tmpfs) [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 tmpfs
Jul 30 11:59:14.002: INFO: Waiting up to 5m0s for pod "pod-a00ec475-0446-48c4-bbc8-63c3e67b0e28" in namespace "emptydir-8228" to be "Succeeded or Failed"
Jul 30 11:59:14.192: INFO: Pod "pod-a00ec475-0446-48c4-bbc8-63c3e67b0e28": Phase="Pending", Reason="", readiness=false. Elapsed: 190.008553ms
Jul 30 11:59:16.383: INFO: Pod "pod-a00ec475-0446-48c4-bbc8-63c3e67b0e28": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.380376045s
STEP: Saw pod success
Jul 30 11:59:16.383: INFO: Pod "pod-a00ec475-0446-48c4-bbc8-63c3e67b0e28" satisfied condition "Succeeded or Failed"
Jul 30 11:59:16.573: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod pod-a00ec475-0446-48c4-bbc8-63c3e67b0e28 container test-container: <nil>
STEP: delete the pod
Jul 30 11:59:16.967: INFO: Waiting for pod pod-a00ec475-0446-48c4-bbc8-63c3e67b0e28 to disappear
Jul 30 11:59:17.157: INFO: Pod pod-a00ec475-0446-48c4-bbc8-63c3e67b0e28 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
Jul 30 11:59:17.157: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "emptydir-8228" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] EmptyDir volumes should support (non-root,0644,tmpfs) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":5,"skipped":21,"failed":2,"failures":["[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]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should not be able to mutate or prevent deletion of webhook configuration objects [Conformance]"]}

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
Jul 30 11:59:17.557: INFO: Driver local doesn't support InlineVolume -- skipping
... 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 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] One pod requesting one prebound PVC should be able to mount volume and read from pod1","total":-1,"completed":13,"skipped":132,"failed":0}

S
------------------------------
[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
... skipping 15 lines ...
• [SLOW TEST:75.010 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":5,"skipped":49,"failed":0}
[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
Jul 30 11:59:24.185: INFO: Driver hostPath doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (default fs)] volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175

... skipping 39 lines ...
• [SLOW TEST:24.480 seconds]
[k8s.io] [sig-node] PreStop
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  graceful pod terminated should wait until preStop hook completes the process
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/node/pre_stop.go:170
------------------------------
{"msg":"PASSED [k8s.io] [sig-node] PreStop graceful pod terminated should wait until preStop hook completes the process","total":-1,"completed":10,"skipped":84,"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
Jul 30 11:59:24.876: INFO: Driver local 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: local][LocalVolumeType: tmpfs]
  /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 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 25 lines ...
STEP: Creating a kubernetes client
Jul 30 11:59:16.899: 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
Jul 30 11:59:18.043: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jul 30 11:59:24.425: INFO: deleting claim "volume-provisioning-1677"/"pvc-h6x6g"
Jul 30 11:59:24.616: INFO: deleting storage class volume-provisioning-1677-invalid-aws
... skipping 5 lines ...

• [SLOW TEST:8.291 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":10,"skipped":63,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a validating webhook should work [Conformance]"]}

SSSSSS
------------------------------
[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
Jul 30 11:59:18.906: 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 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 projected-configmap-test-volume-map-873aaaa5-e9b2-40a7-b6ba-3e1a3f2e97ff
STEP: Creating a pod to test consume configMaps
Jul 30 11:59:20.230: INFO: Waiting up to 5m0s for pod "pod-projected-configmaps-0549b5fd-3e6c-4ab5-af35-691caac472cb" in namespace "projected-4824" to be "Succeeded or Failed"
Jul 30 11:59:20.418: INFO: Pod "pod-projected-configmaps-0549b5fd-3e6c-4ab5-af35-691caac472cb": Phase="Pending", Reason="", readiness=false. Elapsed: 188.414561ms
Jul 30 11:59:22.609: INFO: Pod "pod-projected-configmaps-0549b5fd-3e6c-4ab5-af35-691caac472cb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.379004811s
Jul 30 11:59:24.797: INFO: Pod "pod-projected-configmaps-0549b5fd-3e6c-4ab5-af35-691caac472cb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.567705364s
STEP: Saw pod success
Jul 30 11:59:24.797: INFO: Pod "pod-projected-configmaps-0549b5fd-3e6c-4ab5-af35-691caac472cb" satisfied condition "Succeeded or Failed"
Jul 30 11:59:24.986: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod pod-projected-configmaps-0549b5fd-3e6c-4ab5-af35-691caac472cb container agnhost-container: <nil>
STEP: delete the pod
Jul 30 11:59:25.368: INFO: Waiting for pod pod-projected-configmaps-0549b5fd-3e6c-4ab5-af35-691caac472cb to disappear
Jul 30 11:59:25.557: INFO: Pod pod-projected-configmaps-0549b5fd-3e6c-4ab5-af35-691caac472cb 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:7.029 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 [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 as non-root [NodeConformance] [Conformance]","total":-1,"completed":14,"skipped":133,"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
Jul 30 11:59:25.956: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 63 lines ...
STEP: Registering the mutating webhook for custom resource e2e-test-webhook-3632-crds.webhook.example.com via the AdmissionRegistration API
Jul 30 11:58:29.294: INFO: Waiting for webhook configuration to be ready...
Jul 30 11:58:39.777: INFO: Waiting for webhook configuration to be ready...
Jul 30 11:58:50.175: INFO: Waiting for webhook configuration to be ready...
Jul 30 11:59:00.585: INFO: Waiting for webhook configuration to be ready...
Jul 30 11:59:10.968: INFO: Waiting for webhook configuration to be ready...
Jul 30 11:59:10.969: FAIL: waiting for webhook configuration to be ready
Unexpected error:
    <*errors.errorString | 0xc000182200>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred

... skipping 474 lines ...
[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 pruning [Conformance] [It]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629

  Jul 30 11:59:10.969: waiting for webhook configuration to be ready
  Unexpected error:
      <*errors.errorString | 0xc000182200>: {
          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/apimachinery/webhook.go:1825
------------------------------
{"msg":"FAILED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource with pruning [Conformance]","total":-1,"completed":3,"skipped":29,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource with pruning [Conformance]"]}

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 2 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-7cabc4ef-3a5d-49e0-87a7-a53673351151
STEP: Creating secret with name secret-projected-all-test-volume-fd7dc6e5-5444-4627-a12d-8eb2d81da3e9
STEP: Creating a pod to test Check all projections for projected volume plugin
Jul 30 11:59:25.734: INFO: Waiting up to 5m0s for pod "projected-volume-5bb4cec8-ee13-4b10-8182-f0b0f6be9d0a" in namespace "projected-1276" to be "Succeeded or Failed"
Jul 30 11:59:25.924: INFO: Pod "projected-volume-5bb4cec8-ee13-4b10-8182-f0b0f6be9d0a": Phase="Pending", Reason="", readiness=false. Elapsed: 189.790157ms
Jul 30 11:59:28.115: INFO: Pod "projected-volume-5bb4cec8-ee13-4b10-8182-f0b0f6be9d0a": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.381133515s
STEP: Saw pod success
Jul 30 11:59:28.115: INFO: Pod "projected-volume-5bb4cec8-ee13-4b10-8182-f0b0f6be9d0a" satisfied condition "Succeeded or Failed"
Jul 30 11:59:28.305: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod projected-volume-5bb4cec8-ee13-4b10-8182-f0b0f6be9d0a container projected-all-volume-test: <nil>
STEP: delete the pod
Jul 30 11:59:28.690: INFO: Waiting for pod projected-volume-5bb4cec8-ee13-4b10-8182-f0b0f6be9d0a to disappear
Jul 30 11:59:28.880: INFO: Pod projected-volume-5bb4cec8-ee13-4b10-8182-f0b0f6be9d0a 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:5.052 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":6,"skipped":55,"failed":0}

S
------------------------------
[BeforeEach] [sig-storage] Downward API 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 2 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 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
Jul 30 11:59:27.120: INFO: Waiting up to 5m0s for pod "downwardapi-volume-ef187a9a-9b51-4590-a198-6f09ca5c849d" in namespace "downward-api-1335" to be "Succeeded or Failed"
Jul 30 11:59:27.308: INFO: Pod "downwardapi-volume-ef187a9a-9b51-4590-a198-6f09ca5c849d": Phase="Pending", Reason="", readiness=false. Elapsed: 188.355727ms
Jul 30 11:59:29.497: INFO: Pod "downwardapi-volume-ef187a9a-9b51-4590-a198-6f09ca5c849d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.376821468s
STEP: Saw pod success
Jul 30 11:59:29.497: INFO: Pod "downwardapi-volume-ef187a9a-9b51-4590-a198-6f09ca5c849d" satisfied condition "Succeeded or Failed"
Jul 30 11:59:29.688: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod downwardapi-volume-ef187a9a-9b51-4590-a198-6f09ca5c849d container client-container: <nil>
STEP: delete the pod
Jul 30 11:59:30.072: INFO: Waiting for pod downwardapi-volume-ef187a9a-9b51-4590-a198-6f09ca5c849d to disappear
Jul 30 11:59:30.260: INFO: Pod downwardapi-volume-ef187a9a-9b51-4590-a198-6f09ca5c849d 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
Jul 30 11:59:30.260: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "downward-api-1335" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] Downward API volume should provide container's cpu limit [NodeConformance] [Conformance]","total":-1,"completed":15,"skipped":140,"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
Jul 30 11:59:30.664: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 44 lines ...
Jul 30 11:59:28.550: 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,0644,tmpfs) [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 tmpfs
Jul 30 11:59:29.686: INFO: Waiting up to 5m0s for pod "pod-2eb981f9-636d-4c3d-8c32-7ee73d77ec99" in namespace "emptydir-7450" to be "Succeeded or Failed"
Jul 30 11:59:29.875: INFO: Pod "pod-2eb981f9-636d-4c3d-8c32-7ee73d77ec99": Phase="Pending", Reason="", readiness=false. Elapsed: 188.716756ms
Jul 30 11:59:32.064: INFO: Pod "pod-2eb981f9-636d-4c3d-8c32-7ee73d77ec99": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.377660786s
STEP: Saw pod success
Jul 30 11:59:32.064: INFO: Pod "pod-2eb981f9-636d-4c3d-8c32-7ee73d77ec99" satisfied condition "Succeeded or Failed"
Jul 30 11:59:32.253: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod pod-2eb981f9-636d-4c3d-8c32-7ee73d77ec99 container test-container: <nil>
STEP: delete the pod
Jul 30 11:59:32.637: INFO: Waiting for pod pod-2eb981f9-636d-4c3d-8c32-7ee73d77ec99 to disappear
Jul 30 11:59:32.826: INFO: Pod pod-2eb981f9-636d-4c3d-8c32-7ee73d77ec99 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 99 lines ...
Jul 30 11:56:10.305: INFO: The status of Pod netserver-3 is Running (Ready = true)
STEP: Creating test pods
Jul 30 11:56:13.819: INFO: Setting MaxTries for pod polling to 46 for networking test based on endpoint count 4
Jul 30 11:56:13.819: INFO: Going to poll 100.96.1.8 on port 8080 at least 0 times, with a maximum of 46 tries before failing
Jul 30 11:56:14.007: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:56:14.007: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:56:16.273: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:56:16.273: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:56:18.463: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:56:18.463: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:56:20.689: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:56:20.689: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:56:22.880: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:56:22.880: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:56:25.151: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:56:25.151: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:56:27.340: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:56:27.340: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:56:29.561: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:56:29.561: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:56:31.750: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:56:31.750: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:56:33.994: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:56:33.995: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:56:36.184: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:56:36.184: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:56:38.440: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:56:38.440: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:56:40.629: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:56:40.629: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:56:42.847: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:56:42.848: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:56:45.039: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:56:45.039: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:56:47.302: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:56:47.302: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:56:49.491: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:56:49.491: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:56:51.712: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:56:51.712: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:56:53.902: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:56:53.902: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:56:56.114: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:56:56.115: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:56:58.303: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:56:58.303: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:57:00.554: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:57:00.554: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:57:02.744: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:57:02.744: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:57:04.950: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:57:04.951: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:57:07.139: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:57:07.139: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:57:09.355: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:57:09.355: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:57:11.547: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:57:11.547: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:57:13.790: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:57:13.790: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:57:15.980: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:57:15.980: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:57:18.223: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:57:18.223: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:57:20.414: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:57:20.414: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:57:22.639: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:57:22.639: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:57:24.829: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:57:24.829: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:57:27.064: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:57:27.064: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:57:29.253: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:57:29.253: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:57:31.493: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:57:31.493: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:57:33.682: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:57:33.682: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:57:35.894: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:57:35.894: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:57:38.083: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:57:38.083: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:57:40.364: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:57:40.364: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:57:42.553: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:57:42.553: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:57:44.785: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:57:44.785: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:57:46.978: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:57:46.978: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:57:49.219: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:57:49.219: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:57:51.408: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:57:51.408: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:57:53.629: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:57:53.629: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:57:55.818: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:57:55.818: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:57:58.092: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:57:58.092: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:58:00.281: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:58:00.281: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:58:02.510: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:58:02.510: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:58:04.699: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:58:04.699: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:58:06.908: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:58:06.908: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:58:09.097: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:58:09.097: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:58:11.335: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:58:11.335: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:58:13.528: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:58:13.528: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:58:15.764: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:58:15.764: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:58:17.953: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:58:17.954: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:58:20.178: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:58:20.178: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:58:22.370: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:58:22.370: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:58:24.588: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:58:24.588: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:58:26.779: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:58:26.779: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:58:29.001: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:58:29.001: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:58:31.192: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:58:31.193: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:58:33.435: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:58:33.435: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:58:35.626: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:58:35.626: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:58:37.870: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:58:37.870: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:58:40.061: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:58:40.061: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:58:42.274: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:58:42.274: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:58:44.465: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:58:44.465: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:58:46.686: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:58:46.686: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:58:48.877: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:58:48.877: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:58:51.112: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:58:51.112: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:58:53.303: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:58:53.303: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:58:55.559: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:58:55.559: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:58:57.750: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:58:57.750: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:58:59.975: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:58:59.975: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:59:02.166: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:59:02.166: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:59:04.386: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:59:04.386: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:59:06.577: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:59:06.577: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:59:08.867: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:59:08.867: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:59:11.058: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:59:11.058: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:59:13.322: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:59:13.322: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:59:15.513: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:59:15.513: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:59:17.751: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:59:17.751: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:59:19.942: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:59:19.942: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:59:22.161: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:59:22.162: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:59:24.352: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:59:24.352: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:59:26.558: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:59:26.558: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:59:28.749: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:59:28.749: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:59:30.980: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:59:30.980: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:59:33.171: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\s*$'] Namespace:pod-network-test-2630 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 11:59:33.171: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 11:59:35.401: INFO: Failed to execute "curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 11:59:35.401: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 11:59:37.401: INFO: 
Output of kubectl describe pod pod-network-test-2630/netserver-0:

Jul 30 11:59:37.401: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=pod-network-test-2630 describe pod netserver-0 --namespace=pod-network-test-2630'
Jul 30 11:59:38.446: INFO: stderr: ""
... skipping 233 lines ...
  Normal  Scheduled  4m7s   default-scheduler  Successfully assigned pod-network-test-2630/netserver-3 to ip-172-20-60-194.ap-southeast-2.compute.internal
  Normal  Pulling    4m7s   kubelet            Pulling image "k8s.gcr.io/e2e-test-images/agnhost:2.21"
  Normal  Pulled     3m51s  kubelet            Successfully pulled image "k8s.gcr.io/e2e-test-images/agnhost:2.21" in 15.200718573s
  Normal  Created    3m51s  kubelet            Created container webserver
  Normal  Started    3m51s  kubelet            Started container webserver

Jul 30 11:59:41.588: FAIL: Error dialing HTTP node to pod failed to find expected endpoints, 
tries 46
Command curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName
retrieved map[]
expected map[netserver-0:{}]

Full Stack Trace
... skipping 282 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/networking.go:27
  Granular Checks: Pods
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/networking.go:30
    should function for node-pod communication: http [LinuxOnly] [NodeConformance] [Conformance] [It]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629

    Jul 30 11:59:41.588: Error dialing HTTP node to pod failed to find expected endpoints, 
    tries 46
    Command curl -g -q -s --max-time 15 --connect-timeout 1 http://100.96.1.8:8080/hostName
    retrieved map[]
    expected map[netserver-0:{}]

    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113
------------------------------
{"msg":"FAILED [sig-network] Networking Granular Checks: Pods should function for node-pod communication: http [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":0,"skipped":4,"failed":1,"failures":["[sig-network] Networking Granular Checks: Pods should function for node-pod communication: http [LinuxOnly] [NodeConformance] [Conformance]"]}

SSSSSSSS
------------------------------
[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
Jul 30 11:59:49.741: INFO: Only supported for providers [azure] (not aws)
... skipping 147 lines ...
STEP: creating a StorageClass volume-expand-6156-csi-hostpath-volume-expand-6156-scfs5zs
STEP: creating a claim
Jul 30 11:58:54.544: INFO: Waiting up to 5m0s for PersistentVolumeClaims [csi-hostpathxh5jz] to have phase Bound
Jul 30 11:58:54.737: INFO: PersistentVolumeClaim csi-hostpathxh5jz found and phase=Bound (192.24073ms)
STEP: Expanding non-expandable pvc
Jul 30 11:58:55.117: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jul 30 11:58:55.499: INFO: Error updating pvc csi-hostpathxh5jz: persistentvolumeclaims "csi-hostpathxh5jz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Jul 30 11:58:57.879: INFO: Error updating pvc csi-hostpathxh5jz: persistentvolumeclaims "csi-hostpathxh5jz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Jul 30 11:58:59.880: INFO: Error updating pvc csi-hostpathxh5jz: persistentvolumeclaims "csi-hostpathxh5jz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Jul 30 11:59:01.881: INFO: Error updating pvc csi-hostpathxh5jz: persistentvolumeclaims "csi-hostpathxh5jz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Jul 30 11:59:03.880: INFO: Error updating pvc csi-hostpathxh5jz: persistentvolumeclaims "csi-hostpathxh5jz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Jul 30 11:59:05.879: INFO: Error updating pvc csi-hostpathxh5jz: persistentvolumeclaims "csi-hostpathxh5jz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Jul 30 11:59:07.880: INFO: Error updating pvc csi-hostpathxh5jz: persistentvolumeclaims "csi-hostpathxh5jz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Jul 30 11:59:09.879: INFO: Error updating pvc csi-hostpathxh5jz: persistentvolumeclaims "csi-hostpathxh5jz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Jul 30 11:59:11.883: INFO: Error updating pvc csi-hostpathxh5jz: persistentvolumeclaims "csi-hostpathxh5jz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Jul 30 11:59:13.879: INFO: Error updating pvc csi-hostpathxh5jz: persistentvolumeclaims "csi-hostpathxh5jz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Jul 30 11:59:15.884: INFO: Error updating pvc csi-hostpathxh5jz: persistentvolumeclaims "csi-hostpathxh5jz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Jul 30 11:59:17.883: INFO: Error updating pvc csi-hostpathxh5jz: persistentvolumeclaims "csi-hostpathxh5jz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Jul 30 11:59:19.884: INFO: Error updating pvc csi-hostpathxh5jz: persistentvolumeclaims "csi-hostpathxh5jz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Jul 30 11:59:21.883: INFO: Error updating pvc csi-hostpathxh5jz: persistentvolumeclaims "csi-hostpathxh5jz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Jul 30 11:59:23.885: INFO: Error updating pvc csi-hostpathxh5jz: persistentvolumeclaims "csi-hostpathxh5jz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Jul 30 11:59:25.885: INFO: Error updating pvc csi-hostpathxh5jz: persistentvolumeclaims "csi-hostpathxh5jz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Jul 30 11:59:26.269: INFO: Error updating pvc csi-hostpathxh5jz: persistentvolumeclaims "csi-hostpathxh5jz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
STEP: Deleting pvc
Jul 30 11:59:26.269: INFO: Deleting PersistentVolumeClaim "csi-hostpathxh5jz"
Jul 30 11:59:26.462: INFO: Waiting up to 5m0s for PersistentVolume pvc-7ba2ae0f-c3d2-4284-ba86-2ea5e57ce2cc to get deleted
Jul 30 11:59:26.654: INFO: PersistentVolume pvc-7ba2ae0f-c3d2-4284-ba86-2ea5e57ce2cc was removed
STEP: Deleting sc
STEP: deleting the test namespace: volume-expand-6156
... skipping 45 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)] 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 (block volmode)] volume-expand should not allow expansion of pvcs without AllowVolumeExpansion property","total":-1,"completed":9,"skipped":97,"failed":1,"failures":["[sig-storage] PersistentVolumes-local  [Volume type: dir-link-bindmounted] Two pods mounting a local volume at the same time should be able to write from pod1 and read from pod2"]}

S
------------------------------
[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
Jul 30 11:59:56.121: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 144 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
------------------------------
SSSSSSS
------------------------------
{"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":13,"skipped":82,"failed":0}
[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
Jul 30 11:59:46.518: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename services
STEP: Waiting for a default service account to be provisioned in namespace
... skipping 27 lines ...
• [SLOW TEST:9.729 seconds]
[sig-network] Services
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
  should serve multiport endpoints from pods  [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 serve multiport endpoints from pods  [Conformance]","total":-1,"completed":14,"skipped":82,"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
Jul 30 11:59:56.254: 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 11 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 [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: blockfs] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing directory","total":-1,"completed":7,"skipped":52,"failed":0}
[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
Jul 30 11:59:08.998: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename container-probe
STEP: Waiting for a default service account to be provisioned in namespace
... skipping 50 lines ...
Jul 30 11:59:49.703: INFO: PersistentVolumeClaim pvc-j79r2 found but phase is Pending instead of Bound.
Jul 30 11:59:51.893: INFO: PersistentVolumeClaim pvc-j79r2 found and phase=Bound (13.323301715s)
Jul 30 11:59:51.893: INFO: Waiting up to 3m0s for PersistentVolume local-lrt5x to have phase Bound
Jul 30 11:59:52.082: INFO: PersistentVolume local-lrt5x found and phase=Bound (189.363774ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-6mwx
STEP: Creating a pod to test exec-volume-test
Jul 30 11:59:52.651: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-6mwx" in namespace "volume-3425" to be "Succeeded or Failed"
Jul 30 11:59:52.841: INFO: Pod "exec-volume-test-preprovisionedpv-6mwx": Phase="Pending", Reason="", readiness=false. Elapsed: 189.391153ms
Jul 30 11:59:55.030: INFO: Pod "exec-volume-test-preprovisionedpv-6mwx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.378885914s
STEP: Saw pod success
Jul 30 11:59:55.030: INFO: Pod "exec-volume-test-preprovisionedpv-6mwx" satisfied condition "Succeeded or Failed"
Jul 30 11:59:55.220: INFO: Trying to get logs from node ip-172-20-33-146.ap-southeast-2.compute.internal pod exec-volume-test-preprovisionedpv-6mwx container exec-container-preprovisionedpv-6mwx: <nil>
STEP: delete the pod
Jul 30 11:59:55.605: INFO: Waiting for pod exec-volume-test-preprovisionedpv-6mwx to disappear
Jul 30 11:59:55.795: INFO: Pod exec-volume-test-preprovisionedpv-6mwx no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-6mwx
Jul 30 11:59:55.795: INFO: Deleting pod "exec-volume-test-preprovisionedpv-6mwx" in namespace "volume-3425"
... 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)] 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: blockfs] [Testpattern: Pre-provisioned PV (default fs)] volumes should allow exec of files on the volume","total":-1,"completed":16,"skipped":148,"failed":0}

SSS
------------------------------
{"msg":"PASSED [k8s.io] Probing container should be restarted by liveness probe after startup probe enables it","total":-1,"completed":8,"skipped":52,"failed":0}
[BeforeEach] [sig-storage] GCP Volumes
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Jul 30 12:00:01.667: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename gcp-volume
STEP: Waiting for a default service account to be provisioned in namespace
... skipping 176 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
  [k8s.io] Pod Container Status
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
    should never report success for a pending container
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/node/pods.go:206
------------------------------
{"msg":"PASSED [k8s.io] [sig-node] Pods Extended [k8s.io] Pod Container Status should never report success for a pending container","total":-1,"completed":9,"skipped":52,"failed":0}

SSSSS
------------------------------
[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 9 lines ...
Jul 30 12:00:03.676: INFO: stderr: "Warning: v1 ComponentStatus is deprecated in v1.19+\n"
Jul 30 12:00:03.676: INFO: stdout: "scheduler controller-manager etcd-1 etcd-0"
STEP: getting details of componentstatuses
STEP: getting status of scheduler
Jul 30 12:00:03.676: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-3979 get componentstatuses scheduler'
Jul 30 12:00:04.331: INFO: stderr: "Warning: v1 ComponentStatus is deprecated in v1.19+\n"
Jul 30 12:00:04.331: INFO: stdout: "NAME        STATUS    MESSAGE   ERROR\nscheduler   Healthy   ok        \n"
STEP: getting status of controller-manager
Jul 30 12:00:04.331: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-3979 get componentstatuses controller-manager'
Jul 30 12:00:04.986: INFO: stderr: "Warning: v1 ComponentStatus is deprecated in v1.19+\n"
Jul 30 12:00:04.986: INFO: stdout: "NAME                 STATUS    MESSAGE   ERROR\ncontroller-manager   Healthy   ok        \n"
STEP: getting status of etcd-1
Jul 30 12:00:04.986: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-3979 get componentstatuses etcd-1'
Jul 30 12:00:05.655: INFO: stderr: "Warning: v1 ComponentStatus is deprecated in v1.19+\n"
Jul 30 12:00:05.655: INFO: stdout: "NAME     STATUS    MESSAGE             ERROR\netcd-1   Healthy   {\"health\":\"true\"}   \n"
STEP: getting status of etcd-0
Jul 30 12:00:05.655: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-3979 get componentstatuses etcd-0'
Jul 30 12:00:06.320: INFO: stderr: "Warning: v1 ComponentStatus is deprecated in v1.19+\n"
Jul 30 12:00:06.320: INFO: stdout: "NAME     STATUS    MESSAGE             ERROR\netcd-0   Healthy   {\"health\":\"true\"}   \n"
[AfterEach] [sig-cli] Kubectl client
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 12:00:06.320: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "kubectl-3979" for this suite.

•
------------------------------
{"msg":"PASSED [sig-cli] Kubectl client Kubectl get componentstatuses should get componentstatuses","total":-1,"completed":17,"skipped":151,"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
Jul 30 12:00:06.710: INFO: Only supported for providers [vsphere] (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 20 lines ...
Jul 30 12:00:06.733: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename svcaccounts
STEP: Waiting for a default service account to be provisioned in namespace
[It] should mount projected service account token [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 service account token: 
Jul 30 12:00:07.872: INFO: Waiting up to 5m0s for pod "test-pod-c1771999-41c8-4388-9615-127088dd910d" in namespace "svcaccounts-9399" to be "Succeeded or Failed"
Jul 30 12:00:08.061: INFO: Pod "test-pod-c1771999-41c8-4388-9615-127088dd910d": Phase="Pending", Reason="", readiness=false. Elapsed: 189.07546ms
Jul 30 12:00:10.251: INFO: Pod "test-pod-c1771999-41c8-4388-9615-127088dd910d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.378806884s
STEP: Saw pod success
Jul 30 12:00:10.251: INFO: Pod "test-pod-c1771999-41c8-4388-9615-127088dd910d" satisfied condition "Succeeded or Failed"
Jul 30 12:00:10.440: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod test-pod-c1771999-41c8-4388-9615-127088dd910d container agnhost-container: <nil>
STEP: delete the pod
Jul 30 12:00:10.830: INFO: Waiting for pod test-pod-c1771999-41c8-4388-9615-127088dd910d to disappear
Jul 30 12:00:11.019: INFO: Pod test-pod-c1771999-41c8-4388-9615-127088dd910d no longer exists
[AfterEach] [sig-auth] ServiceAccounts
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 12:00:11.020: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "svcaccounts-9399" for this suite.

•
------------------------------
{"msg":"PASSED [sig-auth] ServiceAccounts should mount projected service account token [Conformance]","total":-1,"completed":18,"skipped":156,"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
Jul 30 12:00:11.410: 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 39 lines ...
• [SLOW TEST:120.505 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":6,"skipped":58,"failed":0}

SSS
------------------------------
{"msg":"PASSED [sig-storage] EmptyDir volumes should support (root,0644,tmpfs) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":4,"skipped":30,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource with pruning [Conformance]"]}
[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
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Jul 30 11:59:33.214: INFO: >>> kubeConfig: /root/.kube/config
... skipping 12 lines ...
Jul 30 11:59:35.899: INFO: PersistentVolumeClaim pvc-6lxhf found but phase is Pending instead of Bound.
Jul 30 11:59:38.087: INFO: PersistentVolumeClaim pvc-6lxhf found and phase=Bound (2.377426118s)
Jul 30 11:59:38.088: INFO: Waiting up to 3m0s for PersistentVolume aws-rjrkb to have phase Bound
Jul 30 11:59:38.277: INFO: PersistentVolume aws-rjrkb found and phase=Bound (188.998513ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-5lrw
STEP: Creating a pod to test exec-volume-test
Jul 30 11:59:38.844: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-5lrw" in namespace "volume-2808" to be "Succeeded or Failed"
Jul 30 11:59:39.033: INFO: Pod "exec-volume-test-preprovisionedpv-5lrw": Phase="Pending", Reason="", readiness=false. Elapsed: 188.925879ms
Jul 30 11:59:41.223: INFO: Pod "exec-volume-test-preprovisionedpv-5lrw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.378028596s
Jul 30 11:59:43.412: INFO: Pod "exec-volume-test-preprovisionedpv-5lrw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.567038858s
Jul 30 11:59:45.627: INFO: Pod "exec-volume-test-preprovisionedpv-5lrw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.782455652s
Jul 30 11:59:47.816: INFO: Pod "exec-volume-test-preprovisionedpv-5lrw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.971945589s
Jul 30 11:59:50.005: INFO: Pod "exec-volume-test-preprovisionedpv-5lrw": Phase="Pending", Reason="", readiness=false. Elapsed: 11.160908167s
Jul 30 11:59:52.194: INFO: Pod "exec-volume-test-preprovisionedpv-5lrw": Phase="Pending", Reason="", readiness=false. Elapsed: 13.349849392s
Jul 30 11:59:54.384: INFO: Pod "exec-volume-test-preprovisionedpv-5lrw": Phase="Pending", Reason="", readiness=false. Elapsed: 15.539213345s
Jul 30 11:59:56.573: INFO: Pod "exec-volume-test-preprovisionedpv-5lrw": Phase="Pending", Reason="", readiness=false. Elapsed: 17.728553502s
Jul 30 11:59:58.762: INFO: Pod "exec-volume-test-preprovisionedpv-5lrw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.917933045s
STEP: Saw pod success
Jul 30 11:59:58.763: INFO: Pod "exec-volume-test-preprovisionedpv-5lrw" satisfied condition "Succeeded or Failed"
Jul 30 11:59:58.951: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod exec-volume-test-preprovisionedpv-5lrw container exec-container-preprovisionedpv-5lrw: <nil>
STEP: delete the pod
Jul 30 11:59:59.335: INFO: Waiting for pod exec-volume-test-preprovisionedpv-5lrw to disappear
Jul 30 11:59:59.524: INFO: Pod exec-volume-test-preprovisionedpv-5lrw no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-5lrw
Jul 30 11:59:59.524: INFO: Deleting pod "exec-volume-test-preprovisionedpv-5lrw" in namespace "volume-2808"
STEP: Deleting pv and pvc
Jul 30 11:59:59.713: INFO: Deleting PersistentVolumeClaim "pvc-6lxhf"
Jul 30 11:59:59.903: INFO: Deleting PersistentVolume "aws-rjrkb"
Jul 30 12:00:00.394: INFO: Couldn't delete PD "aws://ap-southeast-2a/vol-0f4ef35e4e53745ab", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f4ef35e4e53745ab is currently attached to i-059514bb34af11b09
	status code: 400, request id: c8e6df5c-56a8-4b9a-9234-f56a0767cb01
Jul 30 12:00:06.318: INFO: Couldn't delete PD "aws://ap-southeast-2a/vol-0f4ef35e4e53745ab", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f4ef35e4e53745ab is currently attached to i-059514bb34af11b09
	status code: 400, request id: f2719e6e-ded5-40cd-8861-8e68a7dd5e36
Jul 30 12:00:12.222: INFO: Couldn't delete PD "aws://ap-southeast-2a/vol-0f4ef35e4e53745ab", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f4ef35e4e53745ab is currently attached to i-059514bb34af11b09
	status code: 400, request id: 6d51e26d-32a8-44d3-9be6-084e1c13f1cf
Jul 30 12:00:18.189: INFO: Successfully deleted PD "aws://ap-southeast-2a/vol-0f4ef35e4e53745ab".
[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
Jul 30 12:00:18.189: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2808" 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 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 (ext4)] volumes should allow exec of files on the volume","total":-1,"completed":5,"skipped":30,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource with pruning [Conformance]"]}
[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
Jul 30 12:00:18.578: INFO: Driver emptydir 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 73 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/framework.go:23
  Kubectl diff
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:878
    should check if kubectl diff finds a difference for Deployments [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 diff should check if kubectl diff finds a difference for Deployments [Conformance]","total":-1,"completed":6,"skipped":33,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource with pruning [Conformance]"]}

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
Jul 30 12:00:24.004: INFO: Driver hostPath doesn't support DynamicPV -- skipping
... skipping 80979 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 12:20:44.629: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "emptydir-1033" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] EmptyDir volumes should support (non-root,0644,default) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":29,"skipped":225,"failed":1,"failures":["[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"]}

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
Jul 30 12:20:45.028: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 40 lines ...
Jul 30 12:20:34.930: INFO: PersistentVolumeClaim pvc-qdnf8 found but phase is Pending instead of Bound.
Jul 30 12:20:37.119: INFO: PersistentVolumeClaim pvc-qdnf8 found and phase=Bound (11.145770644s)
Jul 30 12:20:37.119: INFO: Waiting up to 3m0s for PersistentVolume local-xjk6g to have phase Bound
Jul 30 12:20:37.307: INFO: PersistentVolume local-xjk6g found and phase=Bound (188.346462ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-zdpn
STEP: Creating a pod to test subpath
Jul 30 12:20:37.874: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-zdpn" in namespace "provisioning-4418" to be "Succeeded or Failed"
Jul 30 12:20:38.063: INFO: Pod "pod-subpath-test-preprovisionedpv-zdpn": Phase="Pending", Reason="", readiness=false. Elapsed: 188.43621ms
Jul 30 12:20:40.252: INFO: Pod "pod-subpath-test-preprovisionedpv-zdpn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.377147114s
Jul 30 12:20:42.440: INFO: Pod "pod-subpath-test-preprovisionedpv-zdpn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.565831909s
STEP: Saw pod success
Jul 30 12:20:42.440: INFO: Pod "pod-subpath-test-preprovisionedpv-zdpn" satisfied condition "Succeeded or Failed"
Jul 30 12:20:42.629: INFO: Trying to get logs from node ip-172-20-35-124.ap-southeast-2.compute.internal pod pod-subpath-test-preprovisionedpv-zdpn container test-container-subpath-preprovisionedpv-zdpn: <nil>
STEP: delete the pod
Jul 30 12:20:43.012: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-zdpn to disappear
Jul 30 12:20:43.201: INFO: Pod pod-subpath-test-preprovisionedpv-zdpn no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-zdpn
Jul 30 12:20:43.201: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-zdpn" in namespace "provisioning-4418"
... 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-bindmounted] [Testpattern: Pre-provisioned PV (default fs)] subPath should support readOnly file specified in the volumeMount [LinuxOnly]","total":-1,"completed":29,"skipped":179,"failed":4,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a validating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource with different stored version [Conformance]","[sig-network] Services should create endpoints for unready pods","[sig-storage] PersistentVolumes NFS with Single PV - PVC pairs create a PV and a pre-bound PVC: test write access"]}
[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
Jul 30 12:20:45.748: 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 160 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 12:20:46.366: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "endpointslice-4052" for this suite.

•
------------------------------
{"msg":"PASSED [sig-network] EndpointSlice should have Endpoints and EndpointSlices pointing to API Server","total":-1,"completed":30,"skipped":228,"failed":1,"failures":["[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"]}
[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
Jul 30 12:20:46.757: INFO: Only supported for providers [gce gke] (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 107 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 12:20:47.676: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "container-runtime-7427" for this suite.

•
------------------------------
{"msg":"PASSED [k8s.io] Container Runtime blackbox test on terminated container should report termination message [LinuxOnly] as empty when pod succeeds and TerminationMessagePolicy FallbackToLogsOnError is set [NodeConformance] [Conformance]","total":-1,"completed":54,"skipped":459,"failed":2,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should deny crd creation [Conformance]","[sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]"]}

SSS
------------------------------
[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
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
... skipping 42 lines ...
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 12:20:47.907: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "secrets-3174" for this suite.

•
------------------------------
{"msg":"PASSED [sig-api-machinery] Secrets should patch a secret [Conformance]","total":-1,"completed":30,"skipped":192,"failed":4,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a validating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource with different stored version [Conformance]","[sig-network] Services should create endpoints for unready pods","[sig-storage] PersistentVolumes NFS with Single PV - PVC pairs create a PV and a pre-bound PVC: test write access"]}

S
------------------------------
{"msg":"PASSED [sig-storage] PersistentVolumes-local  [Volume type: dir] Two pods mounting a local volume at the same time should be able to write from pod1 and read from pod2","total":-1,"completed":19,"skipped":117,"failed":4,"failures":["[sig-network] DNS should provide DNS for pods for Subdomain [Conformance]","[sig-network] Services should be able to change the type from ExternalName to ClusterIP [Conformance]","[sig-network] Services should be able to switch session affinity for NodePort service [LinuxOnly] [Conformance]","[k8s.io] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart http hook properly [NodeConformance] [Conformance]"]}
[BeforeEach] [sig-scheduling] Multi-AZ Clusters
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Jul 30 12:20:47.410: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename multi-az
STEP: Waiting for a default service account to be provisioned in namespace
... skipping 49 lines ...
• [SLOW TEST:16.427 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 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] ResourceQuota should create a ResourceQuota and capture the life of a pod. [Conformance]","total":-1,"completed":16,"skipped":138,"failed":3,"failures":["[sig-network] Proxy version v1 should proxy through a service and a pod  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] listing mutating webhooks should work [Conformance]","[sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir-bindmounted] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing directories when readOnly specified in the volumeSource"]}

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
Jul 30 12:20:49.119: INFO: Driver local doesn't support InlineVolume -- skipping
... skipping 47 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-8473a5fd-a5fc-48ee-8375-3e69bb9d4c7b
STEP: Creating a pod to test consume configMaps
Jul 30 12:20:49.411: INFO: Waiting up to 5m0s for pod "pod-configmaps-7c469193-bf28-489a-8831-24fb65a349dc" in namespace "configmap-1103" to be "Succeeded or Failed"
Jul 30 12:20:49.601: INFO: Pod "pod-configmaps-7c469193-bf28-489a-8831-24fb65a349dc": Phase="Pending", Reason="", readiness=false. Elapsed: 189.470662ms
Jul 30 12:20:51.791: INFO: Pod "pod-configmaps-7c469193-bf28-489a-8831-24fb65a349dc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.379844391s
STEP: Saw pod success
Jul 30 12:20:51.791: INFO: Pod "pod-configmaps-7c469193-bf28-489a-8831-24fb65a349dc" satisfied condition "Succeeded or Failed"
Jul 30 12:20:51.981: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod pod-configmaps-7c469193-bf28-489a-8831-24fb65a349dc container agnhost-container: <nil>
STEP: delete the pod
Jul 30 12:20:52.368: INFO: Waiting for pod pod-configmaps-7c469193-bf28-489a-8831-24fb65a349dc to disappear
Jul 30 12:20:52.557: INFO: Pod pod-configmaps-7c469193-bf28-489a-8831-24fb65a349dc 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
Jul 30 12:20:52.557: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "configmap-1103" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume with mappings [NodeConformance] [Conformance]","total":-1,"completed":55,"skipped":462,"failed":2,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should deny crd creation [Conformance]","[sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]"]}

SSS
------------------------------
[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
Jul 30 12:20:52.962: INFO: Only supported for providers [gce gke] (not aws)
... skipping 201 lines ...
• [SLOW TEST:18.095 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":26,"skipped":205,"failed":3,"failures":["[sig-network] Services should implement service.kubernetes.io/service-proxy-name","[sig-storage] PersistentVolumes-local  [Volume type: dir-link-bindmounted] One pod requesting one prebound PVC should be able to mount volume and write from pod1","[sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]"]}

S
------------------------------
[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
... skipping 2 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] nonexistent volume subPath should have the correct mode and owner using FSGroup
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/empty_dir.go:63
STEP: Creating a pod to test emptydir subpath on tmpfs
Jul 30 12:20:50.101: INFO: Waiting up to 5m0s for pod "pod-79e7ca2e-c7f3-468b-b7ab-0059c9804bf1" in namespace "emptydir-3460" to be "Succeeded or Failed"
Jul 30 12:20:50.291: INFO: Pod "pod-79e7ca2e-c7f3-468b-b7ab-0059c9804bf1": Phase="Pending", Reason="", readiness=false. Elapsed: 190.002856ms
Jul 30 12:20:52.483: INFO: Pod "pod-79e7ca2e-c7f3-468b-b7ab-0059c9804bf1": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.381896323s
STEP: Saw pod success
Jul 30 12:20:52.483: INFO: Pod "pod-79e7ca2e-c7f3-468b-b7ab-0059c9804bf1" satisfied condition "Succeeded or Failed"
Jul 30 12:20:52.673: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod pod-79e7ca2e-c7f3-468b-b7ab-0059c9804bf1 container test-container: <nil>
STEP: delete the pod
Jul 30 12:20:53.063: INFO: Waiting for pod pod-79e7ca2e-c7f3-468b-b7ab-0059c9804bf1 to disappear
Jul 30 12:20:53.253: INFO: Pod pod-79e7ca2e-c7f3-468b-b7ab-0059c9804bf1 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
Jul 30 12:20:53.253: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "emptydir-3460" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] EmptyDir volumes when FSGroup is specified [LinuxOnly] [NodeFeature:FSGroup] nonexistent volume subPath should have the correct mode and owner using FSGroup","total":-1,"completed":20,"skipped":119,"failed":4,"failures":["[sig-network] DNS should provide DNS for pods for Subdomain [Conformance]","[sig-network] Services should be able to change the type from ExternalName to ClusterIP [Conformance]","[sig-network] Services should be able to switch session affinity for NodePort service [LinuxOnly] [Conformance]","[k8s.io] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart http hook properly [NodeConformance] [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 78 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/framework.go:23
  Simple pod
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:382
    should support exec
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:394
------------------------------
{"msg":"PASSED [sig-cli] Kubectl client Simple pod should support exec","total":-1,"completed":20,"skipped":149,"failed":1,"failures":["[sig-network] DNS should provide DNS for the cluster  [Conformance]"]}

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
Jul 30 12:20:55.782: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 107 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
      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 (block volmode)(allowExpansion)] volume-expand should resize volume when PVC is edited while pod is using it","total":-1,"completed":41,"skipped":229,"failed":2,"failures":["[sig-network] Conntrack should be able to preserve UDP traffic when server pod cycles for a ClusterIP service","[sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: blockfs] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]"]}

SSSSSSSSS
------------------------------
[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 193 lines ...
• [SLOW TEST:9.912 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":31,"skipped":232,"failed":1,"failures":["[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"]}
[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
Jul 30 12:20:58.038: INFO: Only supported for providers [gce gke] (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 48 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 64 lines ...
• [SLOW TEST:82.101 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":28,"skipped":210,"failed":3,"failures":["[sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: tmpfs] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing directory","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny pod and configmap creation [Conformance]","[sig-network] Services should be able to create a functioning NodePort service [Conformance]"]}

SSSSSSSSSSSS
------------------------------
[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 21 lines ...
Jul 30 12:17:22.824: INFO: The status of Pod netserver-3 is Running (Ready = true)
STEP: Creating test pods
Jul 30 12:17:26.343: INFO: Setting MaxTries for pod polling to 46 for networking test based on endpoint count 4
Jul 30 12:17:26.343: INFO: Going to poll 100.96.1.23 on port 8081 at least 0 times, with a maximum of 46 tries before failing
Jul 30 12:17:26.532: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:17:26.532: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:17:28.742: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:17:28.742: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:17:30.932: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:17:30.932: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:17:33.142: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:17:33.142: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:17:35.333: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:17:35.333: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:17:37.540: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:17:37.541: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:17:39.730: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:17:39.730: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:17:41.951: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:17:41.951: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:17:44.141: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:17:44.141: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:17:46.353: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:17:46.353: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:17:48.543: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:17:48.543: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:17:50.753: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:17:50.753: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:17:52.943: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:17:52.943: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:17:55.146: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:17:55.147: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:17:57.337: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:17:57.337: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:17:59.547: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:17:59.547: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:18:01.736: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:18:01.736: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:18:03.949: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:18:03.949: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:18:06.139: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:18:06.139: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:18:08.378: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:18:08.378: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:18:10.568: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:18:10.568: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:18:12.774: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:18:12.774: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:18:14.963: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:18:14.963: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:18:17.179: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:18:17.179: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:18:19.369: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:18:19.369: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:18:21.600: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:18:21.600: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:18:23.790: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:18:23.790: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:18:26.000: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:18:26.000: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:18:28.190: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:18:28.190: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:18:30.386: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:18:30.386: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:18:32.575: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:18:32.575: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:18:34.822: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:18:34.822: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:18:37.012: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:18:37.012: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:18:39.210: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:18:39.210: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:18:41.400: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:18:41.400: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:18:43.624: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:18:43.624: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:18:45.814: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:18:45.814: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:18:48.028: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:18:48.028: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:18:50.218: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:18:50.218: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:18:52.442: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:18:52.442: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:18:54.632: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:18:54.632: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:18:56.842: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:18:56.843: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:18:59.035: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:18:59.035: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:19:01.276: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:19:01.276: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:19:03.466: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:19:03.466: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:19:05.691: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:19:05.691: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:19:07.881: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:19:07.881: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:19:10.104: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:19:10.104: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:19:12.294: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:19:12.294: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:19:14.492: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:19:14.493: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:19:16.682: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:19:16.682: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:19:18.881: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:19:18.881: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:19:21.071: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:19:21.071: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:19:23.295: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:19:23.296: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:19:25.485: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:19:25.485: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:19:27.716: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:19:27.716: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:19:29.905: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:19:29.905: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:19:32.119: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:19:32.119: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:19:34.315: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:19:34.315: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:19:36.571: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:19:36.571: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:19:38.761: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:19:38.761: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:19:41.005: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:19:41.005: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:19:43.194: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:19:43.195: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:19:45.392: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:19:45.392: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:19:47.582: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:19:47.582: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:19:49.782: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:19:49.782: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:19:51.973: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:19:51.973: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:19:54.175: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:19:54.175: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:19:56.365: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:19:56.365: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:19:58.585: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:19:58.586: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:20:00.776: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:20:00.776: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:20:03.038: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:20:03.038: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:20:05.228: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:20:05.228: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:20:07.472: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:20:07.472: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:20:09.662: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:20:09.662: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:20:11.905: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:20:11.905: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:20:14.094: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:20:14.094: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:20:16.298: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:20:16.298: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:20:18.488: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:20:18.488: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:20:20.709: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:20:20.709: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:20:22.898: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:20:22.899: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:20:25.100: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:20:25.100: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:20:27.289: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:20:27.290: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:20:29.494: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:20:29.494: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:20:31.684: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:20:31.684: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:20:33.919: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:20:33.919: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:20:36.109: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:20:36.109: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:20:38.348: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:20:38.348: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:20:40.540: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:20:40.540: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:20:42.745: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:20:42.746: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:20:44.935: INFO: ExecWithOptions {Command:[/bin/sh -c echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\s*$'] Namespace:pod-network-test-2096 PodName:host-test-container-pod ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:20:44.935: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:20:47.145: INFO: Failed to execute "echo hostName | nc -w 1 -u 100.96.1.23 8081 | grep -v '^\\s*$'": command terminated with exit code 1, stdout: "", stderr: ""
Jul 30 12:20:47.145: INFO: Waiting for [netserver-0] endpoints (expected=[netserver-0], actual=[])
Jul 30 12:20:49.145: INFO: 
Output of kubectl describe pod pod-network-test-2096/netserver-0:

Jul 30 12:20:49.145: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=pod-network-test-2096 describe pod netserver-0 --namespace=pod-network-test-2096'
Jul 30 12:20:50.209: INFO: stderr: ""
... skipping 229 lines ...
  ----    ------     ----   ----               -------
  Normal  Scheduled  3m50s  default-scheduler  Successfully assigned pod-network-test-2096/netserver-3 to ip-172-20-60-194.ap-southeast-2.compute.internal
  Normal  Pulled     3m50s  kubelet            Container image "k8s.gcr.io/e2e-test-images/agnhost:2.21" already present on machine
  Normal  Created    3m50s  kubelet            Created container webserver
  Normal  Started    3m50s  kubelet            Started container webserver

Jul 30 12:20:53.344: FAIL: Error dialing UDP from node to pod: failed to find expected endpoints, 
tries 46
Command echo hostName | nc -w 1 -u 100.96.1.23 8081
retrieved map[]
expected map[netserver-0:{}]

Full Stack Trace
... skipping 274 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/networking.go:27
  Granular Checks: Pods
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/networking.go:30
    should function for node-pod communication: udp [LinuxOnly] [NodeConformance] [Conformance] [It]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629

    Jul 30 12:20:53.344: Error dialing UDP from node to pod: failed to find expected endpoints, 
    tries 46
    Command echo hostName | nc -w 1 -u 100.96.1.23 8081
    retrieved map[]
    expected map[netserver-0:{}]

    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113
------------------------------
{"msg":"FAILED [sig-network] Networking Granular Checks: Pods should function for node-pod communication: udp [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":21,"skipped":160,"failed":2,"failures":["[sig-network] Services should be able to up and down services","[sig-network] Networking Granular Checks: Pods should function for node-pod communication: udp [LinuxOnly] [NodeConformance] [Conformance]"]}
[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
Jul 30 12:21:01.305: INFO: Driver hostPath doesn't support PreprovisionedPV -- skipping
[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 236 lines ...
• [SLOW TEST:5.237 seconds]
[sig-apps] ReplicaSet
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23
  should adopt matching pods on creation and release no longer 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] ReplicaSet should adopt matching pods on creation and release no longer matching pods [Conformance]","total":-1,"completed":22,"skipped":178,"failed":2,"failures":["[sig-network] Services should be able to up and down services","[sig-network] Networking Granular Checks: Pods should function for node-pod communication: udp [LinuxOnly] [NodeConformance] [Conformance]"]}

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
Jul 30 12:21:06.692: INFO: Only supported for providers [openstack] (not aws)
... skipping 136 lines ...
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [k8s.io] Sysctls [LinuxOnly] [NodeFeature:Sysctls]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/sysctl.go:64
[It] should support unsafe sysctls which are actually whitelisted
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/sysctl.go:108
STEP: Creating a pod with the kernel.shm_rmid_forced sysctl
STEP: Watching for error events or started pod
STEP: Waiting for pod completion
STEP: Checking that the pod succeeded
STEP: Getting logs from the pod
STEP: Checking that the sysctl is actually updated
[AfterEach] [k8s.io] Sysctls [LinuxOnly] [NodeFeature:Sysctls]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
Jul 30 12:21:10.674: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "sysctl-7095" for this suite.

•
------------------------------
{"msg":"PASSED [k8s.io] Sysctls [LinuxOnly] [NodeFeature:Sysctls] should support unsafe sysctls which are actually whitelisted","total":-1,"completed":23,"skipped":193,"failed":2,"failures":["[sig-network] Services should be able to up and down services","[sig-network] Networking Granular Checks: Pods should function for node-pod communication: udp [LinuxOnly] [NodeConformance] [Conformance]"]}

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 ...
Jul 30 12:20:53.137: 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 directory specified in the volumeMount
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:361
Jul 30 12:20:54.079: INFO: In-tree plugin kubernetes.io/host-path is not migrated, not validating any metrics
Jul 30 12:20:54.463: INFO: Waiting up to 5m0s for pod "hostpath-symlink-prep-provisioning-8200" in namespace "provisioning-8200" to be "Succeeded or Failed"
Jul 30 12:20:54.651: INFO: Pod "hostpath-symlink-prep-provisioning-8200": Phase="Pending", Reason="", readiness=false. Elapsed: 187.843234ms
Jul 30 12:20:56.839: INFO: Pod "hostpath-symlink-prep-provisioning-8200": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.376018078s
STEP: Saw pod success
Jul 30 12:20:56.839: INFO: Pod "hostpath-symlink-prep-provisioning-8200" satisfied condition "Succeeded or Failed"
Jul 30 12:20:56.839: INFO: Deleting pod "hostpath-symlink-prep-provisioning-8200" in namespace "provisioning-8200"
Jul 30 12:20:57.031: INFO: Wait up to 5m0s for pod "hostpath-symlink-prep-provisioning-8200" to be fully deleted
Jul 30 12:20:57.219: INFO: Creating resource for inline volume
STEP: Creating pod pod-subpath-test-inlinevolume-pzvc
STEP: Creating a pod to test subpath
Jul 30 12:20:57.408: INFO: Waiting up to 5m0s for pod "pod-subpath-test-inlinevolume-pzvc" in namespace "provisioning-8200" to be "Succeeded or Failed"
Jul 30 12:20:57.597: INFO: Pod "pod-subpath-test-inlinevolume-pzvc": Phase="Pending", Reason="", readiness=false. Elapsed: 188.326958ms
Jul 30 12:20:59.785: INFO: Pod "pod-subpath-test-inlinevolume-pzvc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.376892874s
Jul 30 12:21:01.974: INFO: Pod "pod-subpath-test-inlinevolume-pzvc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.565485835s
STEP: Saw pod success
Jul 30 12:21:01.974: INFO: Pod "pod-subpath-test-inlinevolume-pzvc" satisfied condition "Succeeded or Failed"
Jul 30 12:21:02.162: INFO: Trying to get logs from node ip-172-20-35-124.ap-southeast-2.compute.internal pod pod-subpath-test-inlinevolume-pzvc container test-container-subpath-inlinevolume-pzvc: <nil>
STEP: delete the pod
Jul 30 12:21:02.546: INFO: Waiting for pod pod-subpath-test-inlinevolume-pzvc to disappear
Jul 30 12:21:02.734: INFO: Pod pod-subpath-test-inlinevolume-pzvc no longer exists
STEP: Deleting pod pod-subpath-test-inlinevolume-pzvc
Jul 30 12:21:02.735: INFO: Deleting pod "pod-subpath-test-inlinevolume-pzvc" in namespace "provisioning-8200"
STEP: Deleting pod
Jul 30 12:21:02.923: INFO: Deleting pod "pod-subpath-test-inlinevolume-pzvc" in namespace "provisioning-8200"
Jul 30 12:21:03.341: INFO: Waiting up to 5m0s for pod "hostpath-symlink-prep-provisioning-8200" in namespace "provisioning-8200" to be "Succeeded or Failed"
Jul 30 12:21:03.529: INFO: Pod "hostpath-symlink-prep-provisioning-8200": Phase="Pending", Reason="", readiness=false. Elapsed: 187.88038ms
Jul 30 12:21:05.733: INFO: Pod "hostpath-symlink-prep-provisioning-8200": Phase="Pending", Reason="", readiness=false. Elapsed: 2.391347711s
Jul 30 12:21:07.921: INFO: Pod "hostpath-symlink-prep-provisioning-8200": Phase="Pending", Reason="", readiness=false. Elapsed: 4.579665748s
Jul 30 12:21:10.109: INFO: Pod "hostpath-symlink-prep-provisioning-8200": Phase="Pending", Reason="", readiness=false. Elapsed: 6.767897272s
Jul 30 12:21:12.298: INFO: Pod "hostpath-symlink-prep-provisioning-8200": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.956546325s
STEP: Saw pod success
Jul 30 12:21:12.298: INFO: Pod "hostpath-symlink-prep-provisioning-8200" satisfied condition "Succeeded or Failed"
Jul 30 12:21:12.298: INFO: Deleting pod "hostpath-symlink-prep-provisioning-8200" in namespace "provisioning-8200"
Jul 30 12:21:12.492: INFO: Wait up to 5m0s for pod "hostpath-symlink-prep-provisioning-8200" 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
Jul 30 12:21:12.680: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "provisioning-8200" 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 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: hostPathSymlink] [Testpattern: Inline-volume (default fs)] subPath should support readOnly directory specified in the volumeMount","total":-1,"completed":27,"skipped":206,"failed":3,"failures":["[sig-network] Services should implement service.kubernetes.io/service-proxy-name","[sig-storage] PersistentVolumes-local  [Volume type: dir-link-bindmounted] One pod requesting one prebound PVC should be able to mount volume and write from pod1","[sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]"]}

S
------------------------------
[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
Jul 30 12:21:13.073: INFO: Driver hostPathSymlink doesn't support DynamicPV -- skipping
... skipping 210 lines ...
Jul 30 12:20:05.420: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jul 30 12:20:05.615: INFO: Waiting up to 5m0s for PersistentVolumeClaims [csi-hostpathx5kk4] to have phase Bound
Jul 30 12:20:05.808: INFO: PersistentVolumeClaim csi-hostpathx5kk4 found but phase is Pending instead of Bound.
Jul 30 12:20:08.001: INFO: PersistentVolumeClaim csi-hostpathx5kk4 found and phase=Bound (2.38572196s)
STEP: Creating pod pod-subpath-test-dynamicpv-thxd
STEP: Creating a pod to test subpath
Jul 30 12:20:08.581: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-thxd" in namespace "provisioning-4545" to be "Succeeded or Failed"
Jul 30 12:20:08.774: INFO: Pod "pod-subpath-test-dynamicpv-thxd": Phase="Pending", Reason="", readiness=false. Elapsed: 192.75991ms
Jul 30 12:20:10.968: INFO: Pod "pod-subpath-test-dynamicpv-thxd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.386150462s
Jul 30 12:20:13.161: INFO: Pod "pod-subpath-test-dynamicpv-thxd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.579391615s
Jul 30 12:20:15.354: INFO: Pod "pod-subpath-test-dynamicpv-thxd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.772730137s
Jul 30 12:20:17.547: INFO: Pod "pod-subpath-test-dynamicpv-thxd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.965794134s
Jul 30 12:20:19.740: INFO: Pod "pod-subpath-test-dynamicpv-thxd": Phase="Pending", Reason="", readiness=false. Elapsed: 11.158934266s
Jul 30 12:20:21.934: INFO: Pod "pod-subpath-test-dynamicpv-thxd": Phase="Pending", Reason="", readiness=false. Elapsed: 13.352270259s
Jul 30 12:20:24.127: INFO: Pod "pod-subpath-test-dynamicpv-thxd": Phase="Pending", Reason="", readiness=false. Elapsed: 15.545595361s
Jul 30 12:20:26.321: INFO: Pod "pod-subpath-test-dynamicpv-thxd": Phase="Pending", Reason="", readiness=false. Elapsed: 17.739139199s
Jul 30 12:20:28.514: INFO: Pod "pod-subpath-test-dynamicpv-thxd": Phase="Pending", Reason="", readiness=false. Elapsed: 19.932253183s
Jul 30 12:20:30.707: INFO: Pod "pod-subpath-test-dynamicpv-thxd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.125610869s
STEP: Saw pod success
Jul 30 12:20:30.707: INFO: Pod "pod-subpath-test-dynamicpv-thxd" satisfied condition "Succeeded or Failed"
Jul 30 12:20:30.900: INFO: Trying to get logs from node ip-172-20-33-146.ap-southeast-2.compute.internal pod pod-subpath-test-dynamicpv-thxd container test-container-subpath-dynamicpv-thxd: <nil>
STEP: delete the pod
Jul 30 12:20:31.292: INFO: Waiting for pod pod-subpath-test-dynamicpv-thxd to disappear
Jul 30 12:20:31.485: INFO: Pod pod-subpath-test-dynamicpv-thxd no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-thxd
Jul 30 12:20:31.485: INFO: Deleting pod "pod-subpath-test-dynamicpv-thxd" in namespace "provisioning-4545"
STEP: Creating pod pod-subpath-test-dynamicpv-thxd
STEP: Creating a pod to test subpath
Jul 30 12:20:31.873: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-thxd" in namespace "provisioning-4545" to be "Succeeded or Failed"
Jul 30 12:20:32.069: INFO: Pod "pod-subpath-test-dynamicpv-thxd": Phase="Pending", Reason="", readiness=false. Elapsed: 196.354856ms
Jul 30 12:20:34.267: INFO: Pod "pod-subpath-test-dynamicpv-thxd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.394188065s
Jul 30 12:20:36.460: INFO: Pod "pod-subpath-test-dynamicpv-thxd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.58760034s
Jul 30 12:20:38.654: INFO: Pod "pod-subpath-test-dynamicpv-thxd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.780743786s
Jul 30 12:20:40.848: INFO: Pod "pod-subpath-test-dynamicpv-thxd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.974952456s
Jul 30 12:20:43.041: INFO: Pod "pod-subpath-test-dynamicpv-thxd": Phase="Pending", Reason="", readiness=false. Elapsed: 11.16781259s
Jul 30 12:20:45.236: INFO: Pod "pod-subpath-test-dynamicpv-thxd": Phase="Pending", Reason="", readiness=false. Elapsed: 13.363396855s
Jul 30 12:20:47.430: INFO: Pod "pod-subpath-test-dynamicpv-thxd": Phase="Pending", Reason="", readiness=false. Elapsed: 15.556881115s
Jul 30 12:20:49.627: INFO: Pod "pod-subpath-test-dynamicpv-thxd": Phase="Pending", Reason="", readiness=false. Elapsed: 17.754298682s
Jul 30 12:20:51.821: INFO: Pod "pod-subpath-test-dynamicpv-thxd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.947743393s
STEP: Saw pod success
Jul 30 12:20:51.821: INFO: Pod "pod-subpath-test-dynamicpv-thxd" satisfied condition "Succeeded or Failed"
Jul 30 12:20:52.014: INFO: Trying to get logs from node ip-172-20-33-146.ap-southeast-2.compute.internal pod pod-subpath-test-dynamicpv-thxd container test-container-subpath-dynamicpv-thxd: <nil>
STEP: delete the pod
Jul 30 12:20:52.407: INFO: Waiting for pod pod-subpath-test-dynamicpv-thxd to disappear
Jul 30 12:20:52.599: INFO: Pod pod-subpath-test-dynamicpv-thxd no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-thxd
Jul 30 12:20:52.600: INFO: Deleting pod "pod-subpath-test-dynamicpv-thxd" in namespace "provisioning-4545"
... skipping 86 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 : secret
    /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 : secret","total":-1,"completed":42,"skipped":291,"failed":1,"failures":["[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]"]}
Jul 30 12:21:22.894: INFO: Running AfterSuite actions on all nodes


[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 11 lines ...
Jul 30 12:21:20.213: INFO: Creating a PV followed by a PVC
Jul 30 12:21:20.597: INFO: Waiting for PV local-pvv27cf to bind to PVC pvc-tvh2b
Jul 30 12:21:20.597: INFO: Waiting up to 3m0s for PersistentVolumeClaims [pvc-tvh2b] to have phase Bound
Jul 30 12:21:20.787: INFO: PersistentVolumeClaim pvc-tvh2b found and phase=Bound (189.458999ms)
Jul 30 12:21:20.787: INFO: Waiting up to 3m0s for PersistentVolume local-pvv27cf to have phase Bound
Jul 30 12:21:20.976: INFO: PersistentVolume local-pvv27cf found and phase=Bound (189.292799ms)
[It] should fail scheduling due to different NodeSelector
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:365
STEP: local-volume-type: dir
STEP: Initializing test volumes
Jul 30 12:21:21.355: INFO: ExecWithOptions {Command:[nsenter --mount=/rootfs/proc/1/ns/mnt -- sh -c mkdir -p /tmp/local-volume-test-c94ce052-04a0-4c6b-aa2a-57b17682fed9] Namespace:persistent-local-volumes-test-5489 PodName:hostexec-ip-172-20-33-146.ap-southeast-2.compute.internal-bd89k ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:true Quiet:false}
Jul 30 12:21:21.355: INFO: >>> kubeConfig: /root/.kube/config
STEP: Creating local PVCs and PVs
... skipping 22 lines ...

• [SLOW TEST:15.306 seconds]
[sig-storage] PersistentVolumes-local 
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  Pod with node different from PV's NodeAffinity
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:339
    should fail scheduling due to different NodeSelector
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:365
------------------------------
{"msg":"PASSED [sig-storage] PersistentVolumes-local  Pod with node different from PV's NodeAffinity should fail scheduling due to different NodeSelector","total":-1,"completed":24,"skipped":194,"failed":2,"failures":["[sig-network] Services should be able to up and down services","[sig-network] Networking Granular Checks: Pods should function for node-pod communication: udp [LinuxOnly] [NodeConformance] [Conformance]"]}
Jul 30 12:21:26.388: INFO: Running AfterSuite actions on all nodes


[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 104 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":24,"skipped":178,"failed":3,"failures":["[sig-network] Networking Granular Checks: Pods should function for node-pod communication: http [LinuxOnly] [NodeConformance] [Conformance]","[sig-storage] PersistentVolumes-local  [Volume type: dir-link-bindmounted] One pod requesting one prebound PVC should be able to mount volume and read from pod1","[sig-network] Services should preserve source pod IP for traffic thru service cluster IP [LinuxOnly]"]}
Jul 30 12:21:28.422: INFO: Running AfterSuite actions on all nodes


[BeforeEach] [sig-api-machinery] Aggregator
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 27 lines ...
• [SLOW TEST:33.237 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":21,"skipped":154,"failed":1,"failures":["[sig-network] DNS should provide DNS for the cluster  [Conformance]"]}
Jul 30 12:21:29.055: INFO: Running AfterSuite actions on all nodes


[BeforeEach] [sig-network] EndpointSlice
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 18 lines ...
• [SLOW TEST:35.644 seconds]
[sig-network] EndpointSlice
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
  should create Endpoints and EndpointSlices for Pods matching a Service
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/endpointslice.go:167
------------------------------
{"msg":"PASSED [sig-network] EndpointSlice should create Endpoints and EndpointSlices for Pods matching a Service","total":-1,"completed":21,"skipped":120,"failed":4,"failures":["[sig-network] DNS should provide DNS for pods for Subdomain [Conformance]","[sig-network] Services should be able to change the type from ExternalName to ClusterIP [Conformance]","[sig-network] Services should be able to switch session affinity for NodePort service [LinuxOnly] [Conformance]","[k8s.io] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart http hook properly [NodeConformance] [Conformance]"]}
Jul 30 12:21:29.299: INFO: Running AfterSuite actions on all nodes


[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
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
... skipping 51 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)] 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 (block volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]","total":-1,"completed":32,"skipped":246,"failed":1,"failures":["[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"]}
Jul 30 12:21:31.111: INFO: Running AfterSuite actions on all nodes


[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 52 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-link] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]","total":-1,"completed":29,"skipped":222,"failed":3,"failures":["[sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: tmpfs] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing directory","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny pod and configmap creation [Conformance]","[sig-network] Services should be able to create a functioning NodePort service [Conformance]"]}
Jul 30 12:21:34.313: INFO: Running AfterSuite actions on all nodes


[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 ...
Jul 30 12:21:05.594: INFO: PersistentVolumeClaim pvc-5tvpp found but phase is Pending instead of Bound.
Jul 30 12:21:07.785: INFO: PersistentVolumeClaim pvc-5tvpp found and phase=Bound (13.327488374s)
Jul 30 12:21:07.785: INFO: Waiting up to 3m0s for PersistentVolume local-bnrfl to have phase Bound
Jul 30 12:21:07.974: INFO: PersistentVolume local-bnrfl found and phase=Bound (188.670805ms)
STEP: Creating pod pod-subpath-test-preprovisionedpv-n69h
STEP: Creating a pod to test atomic-volume-subpath
Jul 30 12:21:08.542: INFO: Waiting up to 5m0s for pod "pod-subpath-test-preprovisionedpv-n69h" in namespace "provisioning-5526" to be "Succeeded or Failed"
Jul 30 12:21:08.731: INFO: Pod "pod-subpath-test-preprovisionedpv-n69h": Phase="Pending", Reason="", readiness=false. Elapsed: 188.80786ms
Jul 30 12:21:10.920: INFO: Pod "pod-subpath-test-preprovisionedpv-n69h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.377774933s
Jul 30 12:21:13.110: INFO: Pod "pod-subpath-test-preprovisionedpv-n69h": Phase="Running", Reason="", readiness=true. Elapsed: 4.567910458s
Jul 30 12:21:15.299: INFO: Pod "pod-subpath-test-preprovisionedpv-n69h": Phase="Running", Reason="", readiness=true. Elapsed: 6.757002836s
Jul 30 12:21:17.489: INFO: Pod "pod-subpath-test-preprovisionedpv-n69h": Phase="Running", Reason="", readiness=true. Elapsed: 8.946441657s
Jul 30 12:21:19.678: INFO: Pod "pod-subpath-test-preprovisionedpv-n69h": Phase="Running", Reason="", readiness=true. Elapsed: 11.136123606s
Jul 30 12:21:21.867: INFO: Pod "pod-subpath-test-preprovisionedpv-n69h": Phase="Running", Reason="", readiness=true. Elapsed: 13.325063541s
Jul 30 12:21:24.057: INFO: Pod "pod-subpath-test-preprovisionedpv-n69h": Phase="Running", Reason="", readiness=true. Elapsed: 15.514303261s
Jul 30 12:21:26.247: INFO: Pod "pod-subpath-test-preprovisionedpv-n69h": Phase="Running", Reason="", readiness=true. Elapsed: 17.704642524s
Jul 30 12:21:28.436: INFO: Pod "pod-subpath-test-preprovisionedpv-n69h": Phase="Running", Reason="", readiness=true. Elapsed: 19.893962746s
Jul 30 12:21:30.626: INFO: Pod "pod-subpath-test-preprovisionedpv-n69h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.083653889s
STEP: Saw pod success
Jul 30 12:21:30.626: INFO: Pod "pod-subpath-test-preprovisionedpv-n69h" satisfied condition "Succeeded or Failed"
Jul 30 12:21:30.816: INFO: Trying to get logs from node ip-172-20-60-194.ap-southeast-2.compute.internal pod pod-subpath-test-preprovisionedpv-n69h container test-container-subpath-preprovisionedpv-n69h: <nil>
STEP: delete the pod
Jul 30 12:21:31.203: INFO: Waiting for pod pod-subpath-test-preprovisionedpv-n69h to disappear
Jul 30 12:21:31.392: INFO: Pod pod-subpath-test-preprovisionedpv-n69h no longer exists
STEP: Deleting pod pod-subpath-test-preprovisionedpv-n69h
Jul 30 12:21:31.392: INFO: Deleting pod "pod-subpath-test-preprovisionedpv-n69h" in namespace "provisioning-5526"
... 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":17,"skipped":144,"failed":3,"failures":["[sig-network] Proxy version v1 should proxy through a service and a pod  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] listing mutating webhooks should work [Conformance]","[sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir-bindmounted] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing directories when readOnly specified in the volumeSource"]}
Jul 30 12:21:35.175: INFO: Running AfterSuite actions on all nodes


[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 101 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  CSI attach test using mock driver
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_mock_volume.go:310
    should require VolumeAttach for drivers with attachment
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_mock_volume.go:332
------------------------------
{"msg":"PASSED [sig-storage] CSI mock volume CSI attach test using mock driver should require VolumeAttach for drivers with attachment","total":-1,"completed":38,"skipped":351,"failed":3,"failures":["[sig-storage] PersistentVolumes-local  [Volume type: dir-link-bindmounted] Two pods mounting a local volume at the same time should be able to write from pod1 and read from pod2","[sig-storage] PersistentVolumes-local  [Volume type: blockfswithformat] Two pods mounting a local volume one after the other should be able to write from pod1 and read from pod2","[sig-network] DNS should resolve DNS of partial qualified names for the cluster [LinuxOnly]"]}
Jul 30 12:21:46.538: INFO: Running AfterSuite actions on all nodes


[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 49 lines ...
STEP: creating a claim
Jul 30 12:21:04.815: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jul 30 12:21:05.009: INFO: Waiting up to 5m0s for PersistentVolumeClaims [csi-hostpathrl9d7] to have phase Bound
Jul 30 12:21:05.198: INFO: PersistentVolumeClaim csi-hostpathrl9d7 found and phase=Bound (188.849167ms)
STEP: Creating pod pod-subpath-test-dynamicpv-jt56
STEP: Creating a pod to test subpath
Jul 30 12:21:05.766: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-jt56" in namespace "provisioning-4285" to be "Succeeded or Failed"
Jul 30 12:21:05.955: INFO: Pod "pod-subpath-test-dynamicpv-jt56": Phase="Pending", Reason="", readiness=false. Elapsed: 189.0829ms
Jul 30 12:21:08.145: INFO: Pod "pod-subpath-test-dynamicpv-jt56": Phase="Pending", Reason="", readiness=false. Elapsed: 2.378425131s
Jul 30 12:21:10.335: INFO: Pod "pod-subpath-test-dynamicpv-jt56": Phase="Pending", Reason="", readiness=false. Elapsed: 4.569109391s
Jul 30 12:21:12.525: INFO: Pod "pod-subpath-test-dynamicpv-jt56": Phase="Pending", Reason="", readiness=false. Elapsed: 6.758531133s
Jul 30 12:21:14.714: INFO: Pod "pod-subpath-test-dynamicpv-jt56": Phase="Pending", Reason="", readiness=false. Elapsed: 8.947765052s
Jul 30 12:21:16.904: INFO: Pod "pod-subpath-test-dynamicpv-jt56": Phase="Pending", Reason="", readiness=false. Elapsed: 11.137186584s
Jul 30 12:21:19.093: INFO: Pod "pod-subpath-test-dynamicpv-jt56": Phase="Pending", Reason="", readiness=false. Elapsed: 13.326524472s
Jul 30 12:21:21.282: INFO: Pod "pod-subpath-test-dynamicpv-jt56": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.516058302s
STEP: Saw pod success
Jul 30 12:21:21.282: INFO: Pod "pod-subpath-test-dynamicpv-jt56" satisfied condition "Succeeded or Failed"
Jul 30 12:21:21.472: INFO: Trying to get logs from node ip-172-20-35-124.ap-southeast-2.compute.internal pod pod-subpath-test-dynamicpv-jt56 container test-container-subpath-dynamicpv-jt56: <nil>
STEP: delete the pod
Jul 30 12:21:21.863: INFO: Waiting for pod pod-subpath-test-dynamicpv-jt56 to disappear
Jul 30 12:21:22.052: INFO: Pod pod-subpath-test-dynamicpv-jt56 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-jt56
Jul 30 12:21:22.052: INFO: Deleting pod "pod-subpath-test-dynamicpv-jt56" in namespace "provisioning-4285"
... 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 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] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support existing single file [LinuxOnly]","total":-1,"completed":42,"skipped":238,"failed":2,"failures":["[sig-network] Conntrack should be able to preserve UDP traffic when server pod cycles for a ClusterIP service","[sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: blockfs] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]"]}
Jul 30 12:21:48.144: INFO: Running AfterSuite actions on all nodes


[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 47 lines ...
Jul 30 12:21:07.785: INFO: Waiting up to 5m0s for PersistentVolumeClaims [pvc-bjjw6] to have phase Bound
Jul 30 12:21:07.974: INFO: PersistentVolumeClaim pvc-bjjw6 found and phase=Bound (189.405367ms)
STEP: Deleting the previously created pod
Jul 30 12:21:16.924: INFO: Deleting pod "pvc-volume-tester-cxvkr" in namespace "csi-mock-volumes-3345"
Jul 30 12:21:17.137: INFO: Wait up to 5m0s for pod "pvc-volume-tester-cxvkr" to be fully deleted
STEP: Checking CSI driver logs
Jul 30 12:21:31.708: INFO: Found NodeUnpublishVolume: {json: {"Method":"/csi.v1.Node/NodeUnpublishVolume","Request":{"volume_id":"4","target_path":"/var/lib/kubelet/pods/8070c08a-51a0-4504-926b-641fbbb11b93/volumes/kubernetes.io~csi/pvc-a1858059-1e9b-49af-896b-378ee2530b01/mount"},"Response":{},"Error":"","FullError":null} Method:NodeUnpublishVolume Request:{VolumeContext:map[]} FullError:{Code:OK Message:} Error:}
STEP: Deleting pod pvc-volume-tester-cxvkr
Jul 30 12:21:31.708: INFO: Deleting pod "pvc-volume-tester-cxvkr" in namespace "csi-mock-volumes-3345"
STEP: Deleting claim pvc-bjjw6
Jul 30 12:21:32.276: INFO: Waiting up to 2m0s for PersistentVolume pvc-a1858059-1e9b-49af-896b-378ee2530b01 to get deleted
Jul 30 12:21:32.465: INFO: PersistentVolume pvc-a1858059-1e9b-49af-896b-378ee2530b01 was removed
STEP: Deleting storageclass csi-mock-volumes-3345-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":56,"skipped":484,"failed":2,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should deny crd creation [Conformance]","[sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]"]}
Jul 30 12:21:51.946: INFO: Running AfterSuite actions on all nodes


[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 124 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
      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 (block volmode)(allowExpansion)] volume-expand should resize volume when PVC is edited while pod is using it","total":-1,"completed":21,"skipped":152,"failed":1,"failures":["[sig-network] DNS should provide DNS for ExternalName services [Conformance]"]}
Jul 30 12:22:17.009: INFO: Running AfterSuite actions on all nodes


[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 38 lines ...
Jul 30 12:17:08.255: INFO: stderr: ""
Jul 30 12:17:08.255: INFO: stdout: "true"
Jul 30 12:17:08.255: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-5443 get pods update-demo-nautilus-x6hhr -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}'
Jul 30 12:17:08.940: INFO: stderr: ""
Jul 30 12:17:08.940: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0"
Jul 30 12:17:08.940: INFO: validating pod update-demo-nautilus-x6hhr
Jul 30 12:17:39.131: INFO: update-demo-nautilus-x6hhr is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-x6hhr)
Jul 30 12:17:44.131: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-5443 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo'
Jul 30 12:17:45.004: INFO: stderr: ""
Jul 30 12:17:45.004: INFO: stdout: "update-demo-nautilus-jfmqf update-demo-nautilus-x6hhr "
Jul 30 12:17:45.004: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-5443 get pods update-demo-nautilus-jfmqf -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}'
Jul 30 12:17:45.679: INFO: stderr: ""
Jul 30 12:17:45.679: INFO: stdout: "true"
... skipping 11 lines ...
Jul 30 12:17:47.191: INFO: stderr: ""
Jul 30 12:17:47.191: INFO: stdout: "true"
Jul 30 12:17:47.191: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-5443 get pods update-demo-nautilus-x6hhr -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}'
Jul 30 12:17:47.861: INFO: stderr: ""
Jul 30 12:17:47.861: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0"
Jul 30 12:17:47.861: INFO: validating pod update-demo-nautilus-x6hhr
Jul 30 12:18:18.052: INFO: update-demo-nautilus-x6hhr is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-x6hhr)
Jul 30 12:18:23.052: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-5443 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo'
Jul 30 12:18:23.904: INFO: stderr: ""
Jul 30 12:18:23.904: INFO: stdout: "update-demo-nautilus-jfmqf update-demo-nautilus-x6hhr "
Jul 30 12:18:23.904: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-5443 get pods update-demo-nautilus-jfmqf -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}'
Jul 30 12:18:24.659: INFO: stderr: ""
Jul 30 12:18:24.659: INFO: stdout: "true"
... skipping 11 lines ...
Jul 30 12:18:26.163: INFO: stderr: ""
Jul 30 12:18:26.163: INFO: stdout: "true"
Jul 30 12:18:26.163: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-5443 get pods update-demo-nautilus-x6hhr -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}'
Jul 30 12:18:26.824: INFO: stderr: ""
Jul 30 12:18:26.824: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0"
Jul 30 12:18:26.824: INFO: validating pod update-demo-nautilus-x6hhr
Jul 30 12:18:57.015: INFO: update-demo-nautilus-x6hhr is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-x6hhr)
Jul 30 12:19:02.015: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-5443 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo'
Jul 30 12:19:02.870: INFO: stderr: ""
Jul 30 12:19:02.870: INFO: stdout: "update-demo-nautilus-jfmqf update-demo-nautilus-x6hhr "
Jul 30 12:19:02.871: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-5443 get pods update-demo-nautilus-jfmqf -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}'
Jul 30 12:19:03.525: INFO: stderr: ""
Jul 30 12:19:03.525: INFO: stdout: "true"
... skipping 11 lines ...
Jul 30 12:19:05.035: INFO: stderr: ""
Jul 30 12:19:05.035: INFO: stdout: "true"
Jul 30 12:19:05.035: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-5443 get pods update-demo-nautilus-x6hhr -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}'
Jul 30 12:19:05.692: INFO: stderr: ""
Jul 30 12:19:05.692: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0"
Jul 30 12:19:05.692: INFO: validating pod update-demo-nautilus-x6hhr
Jul 30 12:19:35.884: INFO: update-demo-nautilus-x6hhr is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-x6hhr)
Jul 30 12:19:40.884: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-5443 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo'
Jul 30 12:19:41.725: INFO: stderr: ""
Jul 30 12:19:41.725: INFO: stdout: "update-demo-nautilus-jfmqf update-demo-nautilus-x6hhr "
Jul 30 12:19:41.725: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-5443 get pods update-demo-nautilus-jfmqf -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}'
Jul 30 12:19:42.381: INFO: stderr: ""
Jul 30 12:19:42.381: INFO: stdout: "true"
... skipping 11 lines ...
Jul 30 12:19:43.886: INFO: stderr: ""
Jul 30 12:19:43.886: INFO: stdout: "true"
Jul 30 12:19:43.886: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-5443 get pods update-demo-nautilus-x6hhr -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}'
Jul 30 12:19:44.550: INFO: stderr: ""
Jul 30 12:19:44.550: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0"
Jul 30 12:19:44.550: INFO: validating pod update-demo-nautilus-x6hhr
Jul 30 12:20:14.741: INFO: update-demo-nautilus-x6hhr is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-x6hhr)
Jul 30 12:20:19.742: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-5443 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo'
Jul 30 12:20:20.580: INFO: stderr: ""
Jul 30 12:20:20.580: INFO: stdout: "update-demo-nautilus-jfmqf update-demo-nautilus-x6hhr "
Jul 30 12:20:20.581: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-5443 get pods update-demo-nautilus-jfmqf -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}'
Jul 30 12:20:21.229: INFO: stderr: ""
Jul 30 12:20:21.230: INFO: stdout: "true"
... skipping 11 lines ...
Jul 30 12:20:22.733: INFO: stderr: ""
Jul 30 12:20:22.733: INFO: stdout: "true"
Jul 30 12:20:22.733: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-5443 get pods update-demo-nautilus-x6hhr -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}'
Jul 30 12:20:23.392: INFO: stderr: ""
Jul 30 12:20:23.392: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0"
Jul 30 12:20:23.392: INFO: validating pod update-demo-nautilus-x6hhr
Jul 30 12:20:53.583: INFO: update-demo-nautilus-x6hhr is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-x6hhr)
Jul 30 12:20:58.583: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-5443 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo'
Jul 30 12:20:59.422: INFO: stderr: ""
Jul 30 12:20:59.423: INFO: stdout: "update-demo-nautilus-jfmqf update-demo-nautilus-x6hhr "
Jul 30 12:20:59.423: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-5443 get pods update-demo-nautilus-jfmqf -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}'
Jul 30 12:21:00.079: INFO: stderr: ""
Jul 30 12:21:00.079: INFO: stdout: "true"
... skipping 11 lines ...
Jul 30 12:21:01.603: INFO: stderr: ""
Jul 30 12:21:01.603: INFO: stdout: "true"
Jul 30 12:21:01.603: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-5443 get pods update-demo-nautilus-x6hhr -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}'
Jul 30 12:21:02.259: INFO: stderr: ""
Jul 30 12:21:02.259: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0"
Jul 30 12:21:02.259: INFO: validating pod update-demo-nautilus-x6hhr
Jul 30 12:21:32.450: INFO: update-demo-nautilus-x6hhr is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-x6hhr)
Jul 30 12:21:37.450: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-5443 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo'
Jul 30 12:21:38.304: INFO: stderr: ""
Jul 30 12:21:38.304: INFO: stdout: "update-demo-nautilus-jfmqf update-demo-nautilus-x6hhr "
Jul 30 12:21:38.304: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-5443 get pods update-demo-nautilus-jfmqf -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}'
Jul 30 12:21:38.966: INFO: stderr: ""
Jul 30 12:21:38.966: INFO: stdout: "true"
... skipping 11 lines ...
Jul 30 12:21:40.485: INFO: stderr: ""
Jul 30 12:21:40.485: INFO: stdout: "true"
Jul 30 12:21:40.485: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-5443 get pods update-demo-nautilus-x6hhr -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}'
Jul 30 12:21:41.141: INFO: stderr: ""
Jul 30 12:21:41.141: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0"
Jul 30 12:21:41.141: INFO: validating pod update-demo-nautilus-x6hhr
Jul 30 12:22:11.332: INFO: update-demo-nautilus-x6hhr is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-x6hhr)
Jul 30 12:22:16.333: FAIL: Timed out after 300 seconds waiting for name=update-demo pods to reach valid state

Full Stack Trace
k8s.io/kubernetes/test/e2e/kubectl.glob..func1.6.3()
	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:330 +0x2ad
k8s.io/kubernetes/test/e2e.RunE2ETests(0xc0012d0900)
	_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c
... skipping 211 lines ...
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629

    Jul 30 12:22:16.333: Timed out after 300 seconds waiting for name=update-demo pods to reach valid state

    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:330
------------------------------
{"msg":"FAILED [sig-cli] Kubectl client Update Demo should scale a replication controller  [Conformance]","total":-1,"completed":25,"skipped":161,"failed":3,"failures":["[sig-storage] PersistentVolumes NFS with Single PV - PVC pairs create a PVC and non-pre-bound PV: test write access","[sig-storage] PersistentVolumes-local  [Volume type: dir-bindmounted] One pod requesting one prebound PVC should be able to mount volume and write from pod1","[sig-cli] Kubectl client Update Demo should scale a replication controller  [Conformance]"]}
Jul 30 12:22:26.369: INFO: Running AfterSuite actions on all nodes


[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 38 lines ...
Jul 30 12:17:13.938: INFO: stderr: ""
Jul 30 12:17:13.938: INFO: stdout: "true"
Jul 30 12:17:13.938: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7426 get pods update-demo-nautilus-fxdrn -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}'
Jul 30 12:17:14.599: INFO: stderr: ""
Jul 30 12:17:14.599: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0"
Jul 30 12:17:14.599: INFO: validating pod update-demo-nautilus-fxdrn
Jul 30 12:17:44.788: INFO: update-demo-nautilus-fxdrn is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-fxdrn)
Jul 30 12:17:49.788: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7426 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo'
Jul 30 12:17:50.652: INFO: stderr: ""
Jul 30 12:17:50.652: INFO: stdout: "update-demo-nautilus-75jjn update-demo-nautilus-fxdrn "
Jul 30 12:17:50.652: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7426 get pods update-demo-nautilus-75jjn -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}'
Jul 30 12:17:51.315: INFO: stderr: ""
Jul 30 12:17:51.316: INFO: stdout: "true"
... skipping 11 lines ...
Jul 30 12:17:52.822: INFO: stderr: ""
Jul 30 12:17:52.822: INFO: stdout: "true"
Jul 30 12:17:52.822: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7426 get pods update-demo-nautilus-fxdrn -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}'
Jul 30 12:17:53.482: INFO: stderr: ""
Jul 30 12:17:53.482: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0"
Jul 30 12:17:53.482: INFO: validating pod update-demo-nautilus-fxdrn
Jul 30 12:18:23.671: INFO: update-demo-nautilus-fxdrn is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-fxdrn)
Jul 30 12:18:28.671: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7426 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo'
Jul 30 12:18:29.512: INFO: stderr: ""
Jul 30 12:18:29.512: INFO: stdout: "update-demo-nautilus-75jjn update-demo-nautilus-fxdrn "
Jul 30 12:18:29.512: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7426 get pods update-demo-nautilus-75jjn -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}'
Jul 30 12:18:30.165: INFO: stderr: ""
Jul 30 12:18:30.165: INFO: stdout: "true"
... skipping 11 lines ...
Jul 30 12:18:31.702: INFO: stderr: ""
Jul 30 12:18:31.702: INFO: stdout: "true"
Jul 30 12:18:31.702: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7426 get pods update-demo-nautilus-fxdrn -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}'
Jul 30 12:18:32.346: INFO: stderr: ""
Jul 30 12:18:32.347: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0"
Jul 30 12:18:32.347: INFO: validating pod update-demo-nautilus-fxdrn
Jul 30 12:19:02.537: INFO: update-demo-nautilus-fxdrn is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-fxdrn)
Jul 30 12:19:07.537: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7426 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo'
Jul 30 12:19:08.378: INFO: stderr: ""
Jul 30 12:19:08.378: INFO: stdout: "update-demo-nautilus-75jjn update-demo-nautilus-fxdrn "
Jul 30 12:19:08.379: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7426 get pods update-demo-nautilus-75jjn -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}'
Jul 30 12:19:09.033: INFO: stderr: ""
Jul 30 12:19:09.033: INFO: stdout: "true"
... skipping 11 lines ...
Jul 30 12:19:10.544: INFO: stderr: ""
Jul 30 12:19:10.544: INFO: stdout: "true"
Jul 30 12:19:10.544: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7426 get pods update-demo-nautilus-fxdrn -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}'
Jul 30 12:19:11.199: INFO: stderr: ""
Jul 30 12:19:11.200: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0"
Jul 30 12:19:11.200: INFO: validating pod update-demo-nautilus-fxdrn
Jul 30 12:19:41.388: INFO: update-demo-nautilus-fxdrn is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-fxdrn)
Jul 30 12:19:46.388: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7426 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo'
Jul 30 12:19:47.255: INFO: stderr: ""
Jul 30 12:19:47.255: INFO: stdout: "update-demo-nautilus-75jjn update-demo-nautilus-fxdrn "
Jul 30 12:19:47.255: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7426 get pods update-demo-nautilus-75jjn -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}'
Jul 30 12:19:47.936: INFO: stderr: ""
Jul 30 12:19:47.936: INFO: stdout: "true"
... skipping 11 lines ...
Jul 30 12:19:49.445: INFO: stderr: ""
Jul 30 12:19:49.445: INFO: stdout: "true"
Jul 30 12:19:49.445: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7426 get pods update-demo-nautilus-fxdrn -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}'
Jul 30 12:19:50.099: INFO: stderr: ""
Jul 30 12:19:50.099: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0"
Jul 30 12:19:50.099: INFO: validating pod update-demo-nautilus-fxdrn
Jul 30 12:20:20.288: INFO: update-demo-nautilus-fxdrn is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-fxdrn)
Jul 30 12:20:25.288: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7426 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo'
Jul 30 12:20:26.129: INFO: stderr: ""
Jul 30 12:20:26.129: INFO: stdout: "update-demo-nautilus-75jjn update-demo-nautilus-fxdrn "
Jul 30 12:20:26.129: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7426 get pods update-demo-nautilus-75jjn -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}'
Jul 30 12:20:26.791: INFO: stderr: ""
Jul 30 12:20:26.791: INFO: stdout: "true"
... skipping 11 lines ...
Jul 30 12:20:28.296: INFO: stderr: ""
Jul 30 12:20:28.296: INFO: stdout: "true"
Jul 30 12:20:28.296: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7426 get pods update-demo-nautilus-fxdrn -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}'
Jul 30 12:20:28.945: INFO: stderr: ""
Jul 30 12:20:28.945: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0"
Jul 30 12:20:28.946: INFO: validating pod update-demo-nautilus-fxdrn
Jul 30 12:20:59.134: INFO: update-demo-nautilus-fxdrn is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-fxdrn)
Jul 30 12:21:04.134: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7426 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo'
Jul 30 12:21:04.988: INFO: stderr: ""
Jul 30 12:21:04.988: INFO: stdout: "update-demo-nautilus-75jjn update-demo-nautilus-fxdrn "
Jul 30 12:21:04.988: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7426 get pods update-demo-nautilus-75jjn -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}'
Jul 30 12:21:05.653: INFO: stderr: ""
Jul 30 12:21:05.653: INFO: stdout: "true"
... skipping 11 lines ...
Jul 30 12:21:07.151: INFO: stderr: ""
Jul 30 12:21:07.151: INFO: stdout: "true"
Jul 30 12:21:07.151: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7426 get pods update-demo-nautilus-fxdrn -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}'
Jul 30 12:21:07.802: INFO: stderr: ""
Jul 30 12:21:07.802: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0"
Jul 30 12:21:07.802: INFO: validating pod update-demo-nautilus-fxdrn
Jul 30 12:21:37.990: INFO: update-demo-nautilus-fxdrn is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-fxdrn)
Jul 30 12:21:42.990: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7426 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo'
Jul 30 12:21:43.848: INFO: stderr: ""
Jul 30 12:21:43.848: INFO: stdout: "update-demo-nautilus-75jjn update-demo-nautilus-fxdrn "
Jul 30 12:21:43.848: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7426 get pods update-demo-nautilus-75jjn -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}'
Jul 30 12:21:44.501: INFO: stderr: ""
Jul 30 12:21:44.501: INFO: stdout: "true"
... skipping 11 lines ...
Jul 30 12:21:46.003: INFO: stderr: ""
Jul 30 12:21:46.003: INFO: stdout: "true"
Jul 30 12:21:46.003: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7426 get pods update-demo-nautilus-fxdrn -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}'
Jul 30 12:21:46.694: INFO: stderr: ""
Jul 30 12:21:46.694: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0"
Jul 30 12:21:46.694: INFO: validating pod update-demo-nautilus-fxdrn
Jul 30 12:22:16.882: INFO: update-demo-nautilus-fxdrn is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-fxdrn)
Jul 30 12:22:21.883: FAIL: Timed out after 300 seconds waiting for name=update-demo pods to reach valid state

Full Stack Trace
k8s.io/kubernetes/test/e2e/kubectl.glob..func1.6.2()
	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:317 +0x29b
k8s.io/kubernetes/test/e2e.RunE2ETests(0xc003220f00)
	_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c
... skipping 202 lines ...
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629

    Jul 30 12:22:21.883: Timed out after 300 seconds waiting for name=update-demo pods to reach valid state

    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:317
------------------------------
{"msg":"FAILED [sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","total":-1,"completed":20,"skipped":115,"failed":3,"failures":["[sig-network] Services should be able to switch session affinity for service with type clusterIP [LinuxOnly] [Conformance]","[sig-storage] PersistentVolumes-local  [Volume type: blockfswithformat] One pod requesting one prebound PVC should be able to mount volume and write from pod1","[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}
Jul 30 12:22:32.304: INFO: Running AfterSuite actions on all nodes


[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 15 lines ...
STEP: creating replication controller affinity-nodeport-timeout in namespace services-4510
I0730 12:18:20.064793    4658 runners.go:190] Created replication controller with name: affinity-nodeport-timeout, namespace: services-4510, replica count: 3
I0730 12:18:23.265298    4658 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 
Jul 30 12:18:23.831: INFO: Creating new exec pod
Jul 30 12:18:27.777: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Jul 30 12:18:34.660: INFO: rc: 1
Jul 30 12:18:34.660: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /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...
Jul 30 12:18:35.661: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Jul 30 12:18:39.548: INFO: rc: 1
Jul 30 12:18:39.548: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /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...
Jul 30 12:18:39.661: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Jul 30 12:18:43.546: INFO: rc: 1
Jul 30 12:18:43.546: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /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...
Jul 30 12:18:43.661: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Jul 30 12:18:50.607: INFO: rc: 1
Jul 30 12:18:50.607: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /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...
Jul 30 12:18:50.661: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Jul 30 12:18:54.570: INFO: rc: 1
Jul 30 12:18:54.570: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /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...
Jul 30 12:18:54.661: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Jul 30 12:19:01.538: INFO: rc: 1
Jul 30 12:19:01.538: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /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...
Jul 30 12:19:01.661: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Jul 30 12:19:05.564: INFO: rc: 1
Jul 30 12:19:05.564: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /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...
Jul 30 12:19:05.661: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Jul 30 12:19:09.536: INFO: rc: 1
Jul 30 12:19:09.536: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /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...
Jul 30 12:19:09.661: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Jul 30 12:19:16.546: INFO: rc: 1
Jul 30 12:19:16.546: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /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...
Jul 30 12:19:16.661: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Jul 30 12:19:20.570: INFO: rc: 1
Jul 30 12:19:20.570: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /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...
Jul 30 12:19:20.661: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Jul 30 12:19:27.553: INFO: rc: 1
Jul 30 12:19:27.553: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /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...
Jul 30 12:19:27.661: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Jul 30 12:19:34.599: INFO: rc: 1
Jul 30 12:19:34.599: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /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...
Jul 30 12:19:34.661: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Jul 30 12:19:41.563: INFO: rc: 1
Jul 30 12:19:41.563: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /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...
Jul 30 12:19:41.661: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Jul 30 12:19:45.534: INFO: rc: 1
Jul 30 12:19:45.534: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /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...
Jul 30 12:19:45.661: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Jul 30 12:19:49.563: INFO: rc: 1
Jul 30 12:19:49.564: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /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...
Jul 30 12:19:49.661: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Jul 30 12:19:56.532: INFO: rc: 1
Jul 30 12:19:56.532: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /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...
Jul 30 12:19:56.661: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Jul 30 12:20:03.525: INFO: rc: 1
Jul 30 12:20:03.525: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /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...
Jul 30 12:20:03.661: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
Jul 30 12:20:05.545: INFO: stderr: "+ nc -zv -t -w 2 affinity-nodeport-timeout 80\nConnection to affinity-nodeport-timeout 80 port [tcp/http] succeeded!\n"
Jul 30 12:20:05.545: INFO: stdout: ""
Jul 30 12:20:05.545: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 100.71.186.90 80'
Jul 30 12:20:07.436: INFO: stderr: "+ nc -zv -t -w 2 100.71.186.90 80\nConnection to 100.71.186.90 80 port [tcp/http] succeeded!\n"
Jul 30 12:20:07.436: INFO: stdout: ""
Jul 30 12:20:07.436: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.35.124 32656'
Jul 30 12:20:09.302: INFO: stderr: "+ nc -zv -t -w 2 172.20.35.124 32656\nConnection to 172.20.35.124 32656 port [tcp/32656] succeeded!\n"
Jul 30 12:20:09.302: INFO: stdout: ""
Jul 30 12:20:09.302: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:20:13.179: INFO: rc: 1
Jul 30 12:20:13.179: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:20:14.180: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:20:18.051: INFO: rc: 1
Jul 30 12:20:18.051: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:20:18.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:20:22.058: INFO: rc: 1
Jul 30 12:20:22.059: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:20:22.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:20:26.064: INFO: rc: 1
Jul 30 12:20:26.064: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:20:26.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:20:30.067: INFO: rc: 1
Jul 30 12:20:30.067: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:20:30.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:20:34.069: INFO: rc: 1
Jul 30 12:20:34.069: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:20:34.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:20:38.078: INFO: rc: 1
Jul 30 12:20:38.078: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:20:38.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:20:42.055: INFO: rc: 1
Jul 30 12:20:42.055: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:20:42.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:20:46.067: INFO: rc: 1
Jul 30 12:20:46.067: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:20:46.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:20:50.072: INFO: rc: 1
Jul 30 12:20:50.072: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:20:50.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:20:54.045: INFO: rc: 1
Jul 30 12:20:54.045: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:20:54.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:20:58.062: INFO: rc: 1
Jul 30 12:20:58.062: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:20:58.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:21:02.080: INFO: rc: 1
Jul 30 12:21:02.080: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:02.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:21:06.126: INFO: rc: 1
Jul 30 12:21:06.126: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:06.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:21:10.080: INFO: rc: 1
Jul 30 12:21:10.080: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:10.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:21:14.038: INFO: rc: 1
Jul 30 12:21:14.039: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:14.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:21:18.137: INFO: rc: 1
Jul 30 12:21:18.137: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:18.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:21:22.663: INFO: rc: 1
Jul 30 12:21:22.663: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:23.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:21:27.048: INFO: rc: 1
Jul 30 12:21:27.048: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:27.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:21:31.045: INFO: rc: 1
Jul 30 12:21:31.045: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:31.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:21:35.070: INFO: rc: 1
Jul 30 12:21:35.070: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:35.180: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:21:39.076: INFO: rc: 1
Jul 30 12:21:39.077: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:39.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:21:43.119: INFO: rc: 1
Jul 30 12:21:43.119: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:43.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:21:47.059: INFO: rc: 1
Jul 30 12:21:47.059: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:47.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:21:51.076: INFO: rc: 1
Jul 30 12:21:51.077: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:51.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:21:55.058: INFO: rc: 1
Jul 30 12:21:55.058: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:55.180: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:21:59.099: INFO: rc: 1
Jul 30 12:21:59.099: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:59.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:22:03.056: INFO: rc: 1
Jul 30 12:22:03.056: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:22:03.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:22:07.036: INFO: rc: 1
Jul 30 12:22:07.037: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:22:07.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:22:11.064: INFO: rc: 1
Jul 30 12:22:11.064: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:22:11.179: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:22:15.041: INFO: rc: 1
Jul 30 12:22:15.041: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:22:15.041: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656'
Jul 30 12:22:18.940: INFO: rc: 1
Jul 30 12:22:18.940: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-4510 exec execpod-affinityvxv7g -- /bin/sh -x -c nc -zv -t -w 2 172.20.60.194 32656:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:22:18.940: FAIL: Unexpected error:
    <*errors.errorString | 0xc00483e030>: {
        s: "service is not reachable within 2m0s timeout on endpoint 172.20.60.194:32656 over TCP protocol",
    }
    service is not reachable within 2m0s timeout on endpoint 172.20.60.194:32656 over TCP protocol
occurred

... skipping 39 lines ...
Jul 30 12:22:28.711: INFO: At 2021-07-30 12:18:20 +0000 UTC - event for affinity-nodeport-timeout-r6j2h: {kubelet ip-172-20-60-194.ap-southeast-2.compute.internal} Created: Created container affinity-nodeport-timeout
Jul 30 12:22:28.711: INFO: At 2021-07-30 12:18:20 +0000 UTC - event for affinity-nodeport-timeout-r6j2h: {kubelet ip-172-20-60-194.ap-southeast-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/agnhost:2.21" already present on machine
Jul 30 12:22:28.711: INFO: At 2021-07-30 12:18:23 +0000 UTC - event for execpod-affinityvxv7g: {default-scheduler } Scheduled: Successfully assigned services-4510/execpod-affinityvxv7g to ip-172-20-35-124.ap-southeast-2.compute.internal
Jul 30 12:22:28.711: INFO: At 2021-07-30 12:18:24 +0000 UTC - event for execpod-affinityvxv7g: {kubelet ip-172-20-35-124.ap-southeast-2.compute.internal} Created: Created container agnhost-container
Jul 30 12:22:28.711: INFO: At 2021-07-30 12:18:24 +0000 UTC - event for execpod-affinityvxv7g: {kubelet ip-172-20-35-124.ap-southeast-2.compute.internal} Started: Started container agnhost-container
Jul 30 12:22:28.711: INFO: At 2021-07-30 12:18:24 +0000 UTC - event for execpod-affinityvxv7g: {kubelet ip-172-20-35-124.ap-southeast-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/agnhost:2.21" already present on machine
Jul 30 12:22:28.711: INFO: At 2021-07-30 12:22:19 +0000 UTC - event for affinity-nodeport-timeout: {endpoint-controller } FailedToUpdateEndpoint: Failed to update endpoint services-4510/affinity-nodeport-timeout: Operation cannot be fulfilled on endpoints "affinity-nodeport-timeout": the object has been modified; please apply your changes to the latest version and try again
Jul 30 12:22:28.711: INFO: At 2021-07-30 12:22:19 +0000 UTC - event for affinity-nodeport-timeout-8drss: {kubelet ip-172-20-35-124.ap-southeast-2.compute.internal} Killing: Stopping container affinity-nodeport-timeout
Jul 30 12:22:28.711: INFO: At 2021-07-30 12:22:19 +0000 UTC - event for affinity-nodeport-timeout-bzsm9: {kubelet ip-172-20-45-65.ap-southeast-2.compute.internal} Killing: Stopping container affinity-nodeport-timeout
Jul 30 12:22:28.711: INFO: At 2021-07-30 12:22:19 +0000 UTC - event for affinity-nodeport-timeout-r6j2h: {kubelet ip-172-20-60-194.ap-southeast-2.compute.internal} Killing: Stopping container affinity-nodeport-timeout
Jul 30 12:22:28.711: INFO: At 2021-07-30 12:22:19 +0000 UTC - event for execpod-affinityvxv7g: {kubelet ip-172-20-35-124.ap-southeast-2.compute.internal} Killing: Stopping container agnhost-container
Jul 30 12:22:28.899: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Jul 30 12:22:28.899: INFO: 
... skipping 159 lines ...
• Failure [263.107 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 timeout work for NodePort service [LinuxOnly] [Conformance] [It]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629

  Jul 30 12:22:18.941: Unexpected error:
      <*errors.errorString | 0xc00483e030>: {
          s: "service is not reachable within 2m0s timeout on endpoint 172.20.60.194:32656 over TCP protocol",
      }
      service is not reachable within 2m0s timeout on endpoint 172.20.60.194:32656 over TCP protocol
  occurred

  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:3365
------------------------------
{"msg":"FAILED [sig-network] Services should have session affinity timeout work for NodePort service [LinuxOnly] [Conformance]","total":-1,"completed":26,"skipped":160,"failed":2,"failures":["[sig-network] Services should be able to change the type from ClusterIP to ExternalName [Conformance]","[sig-network] Services should have session affinity timeout work for NodePort service [LinuxOnly] [Conformance]"]}
Jul 30 12:22:36.848: INFO: Running AfterSuite actions on all nodes


[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 10 lines ...
STEP: creating replication controller nodeport-update-service in namespace services-7361
I0730 12:18:45.099693    4791 runners.go:190] Created replication controller with name: nodeport-update-service, namespace: services-7361, replica count: 2
I0730 12:18:48.300281    4791 runners.go:190] nodeport-update-service Pods: 2 out of 2 created, 2 running, 0 pending, 0 waiting, 0 inactive, 0 terminating, 0 unknown, 0 runningButNotReady 
Jul 30 12:18:48.300: INFO: Creating new exec pod
Jul 30 12:18:52.249: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80'
Jul 30 12:18:56.133: INFO: rc: 1
Jul 30 12:18:56.133: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /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...
Jul 30 12:18:57.134: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80'
Jul 30 12:19:01.056: INFO: rc: 1
Jul 30 12:19:01.056: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /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...
Jul 30 12:19:01.134: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80'
Jul 30 12:19:08.046: INFO: rc: 1
Jul 30 12:19:08.046: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /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: getaddrinfo: Try again
command terminated with exit code 1

error:
exit status 1
Retrying...
Jul 30 12:19:08.134: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80'
Jul 30 12:19:15.026: INFO: rc: 1
Jul 30 12:19:15.026: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /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: getaddrinfo: Try again
command terminated with exit code 1

error:
exit status 1
Retrying...
Jul 30 12:19:15.134: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80'
Jul 30 12:19:17.006: INFO: stderr: "+ nc -zv -t -w 2 nodeport-update-service 80\nConnection to nodeport-update-service 80 port [tcp/http] succeeded!\n"
Jul 30 12:19:17.006: INFO: stdout: ""
Jul 30 12:19:17.006: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 100.67.218.240 80'
Jul 30 12:19:20.898: INFO: rc: 1
Jul 30 12:19:20.898: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 100.67.218.240 80:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:19:21.898: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 100.67.218.240 80'
Jul 30 12:19:25.776: INFO: rc: 1
Jul 30 12:19:25.776: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 100.67.218.240 80:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:19:25.898: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 100.67.218.240 80'
Jul 30 12:19:27.987: INFO: stderr: "+ nc -zv -t -w 2 100.67.218.240 80\nConnection to 100.67.218.240 80 port [tcp/http] succeeded!\n"
Jul 30 12:19:27.987: INFO: stdout: ""
Jul 30 12:19:27.987: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.35.124 31388'
Jul 30 12:19:29.878: INFO: stderr: "+ nc -zv -t -w 2 172.20.35.124 31388\nConnection to 172.20.35.124 31388 port [tcp/31388] succeeded!\n"
Jul 30 12:19:29.878: INFO: stdout: ""
Jul 30 12:19:29.878: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.33.146 31388'
Jul 30 12:19:33.807: INFO: rc: 1
Jul 30 12:19:33.807: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.33.146 31388:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:19:34.807: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.33.146 31388'
Jul 30 12:19:38.690: INFO: rc: 1
Jul 30 12:19:38.690: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.33.146 31388:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:19:38.807: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.33.146 31388'
Jul 30 12:19:40.693: INFO: stderr: "+ nc -zv -t -w 2 172.20.33.146 31388\nConnection to 172.20.33.146 31388 port [tcp/31388] succeeded!\n"
Jul 30 12:19:40.693: INFO: stdout: ""
Jul 30 12:19:40.693: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 3.25.197.55 31388'
Jul 30 12:19:42.618: INFO: stderr: "+ nc -zv -t -w 2 3.25.197.55 31388\nConnection to 3.25.197.55 31388 port [tcp/31388] succeeded!\n"
Jul 30 12:19:42.618: INFO: stdout: ""
Jul 30 12:19:42.618: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 54.253.58.229 31388'
Jul 30 12:19:46.482: INFO: rc: 1
Jul 30 12:19:46.482: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 54.253.58.229 31388:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:19:47.482: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 54.253.58.229 31388'
Jul 30 12:19:49.356: INFO: stderr: "+ nc -zv -t -w 2 54.253.58.229 31388\nConnection to 54.253.58.229 31388 port [tcp/31388] succeeded!\n"
Jul 30 12:19:49.356: INFO: stdout: ""
STEP: Updating NodePort service to listen TCP and UDP based requests over same Port
Jul 30 12:19:51.129: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80'
Jul 30 12:19:58.004: INFO: rc: 1
Jul 30 12:19:58.004: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /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: getaddrinfo: Try again
command terminated with exit code 1

error:
exit status 1
Retrying...
Jul 30 12:19:59.005: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80'
Jul 30 12:20:05.906: INFO: rc: 1
Jul 30 12:20:05.906: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /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: getaddrinfo: Try again
command terminated with exit code 1

error:
exit status 1
Retrying...
Jul 30 12:20:06.005: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80'
Jul 30 12:20:09.907: INFO: rc: 1
Jul 30 12:20:09.907: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /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...
Jul 30 12:20:10.005: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80'
Jul 30 12:20:13.919: INFO: rc: 1
Jul 30 12:20:13.919: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /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...
Jul 30 12:20:14.005: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80'
Jul 30 12:20:17.876: INFO: rc: 1
Jul 30 12:20:17.876: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /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...
Jul 30 12:20:18.005: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80'
Jul 30 12:20:24.874: INFO: rc: 1
Jul 30 12:20:24.874: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /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: getaddrinfo: Try again
command terminated with exit code 1

error:
exit status 1
Retrying...
Jul 30 12:20:25.005: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80'
Jul 30 12:20:31.880: INFO: rc: 1
Jul 30 12:20:31.880: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /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: getaddrinfo: Try again
command terminated with exit code 1

error:
exit status 1
Retrying...
Jul 30 12:20:32.005: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80'
Jul 30 12:20:38.916: INFO: rc: 1
Jul 30 12:20:38.916: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /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: getaddrinfo: Try again
command terminated with exit code 1

error:
exit status 1
Retrying...
Jul 30 12:20:39.005: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 nodeport-update-service 80'
Jul 30 12:20:40.920: INFO: stderr: "+ nc -zv -t -w 2 nodeport-update-service 80\nConnection to nodeport-update-service 80 port [tcp/http] succeeded!\n"
Jul 30 12:20:40.920: INFO: stdout: ""
Jul 30 12:20:40.921: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 100.67.218.240 80'
Jul 30 12:20:44.813: INFO: rc: 1
Jul 30 12:20:44.813: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 100.67.218.240 80:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:20:45.813: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 100.67.218.240 80'
Jul 30 12:20:47.674: INFO: stderr: "+ nc -zv -t -w 2 100.67.218.240 80\nConnection to 100.67.218.240 80 port [tcp/http] succeeded!\n"
Jul 30 12:20:47.674: INFO: stdout: ""
Jul 30 12:20:47.674: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:20:51.561: INFO: rc: 1
Jul 30 12:20:51.561: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:20:52.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:20:56.443: INFO: rc: 1
Jul 30 12:20:56.443: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:20:56.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:21:00.459: INFO: rc: 1
Jul 30 12:21:00.459: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:00.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:21:04.473: INFO: rc: 1
Jul 30 12:21:04.473: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:04.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:21:08.476: INFO: rc: 1
Jul 30 12:21:08.476: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:08.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:21:12.497: INFO: rc: 1
Jul 30 12:21:12.497: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:12.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:21:16.442: INFO: rc: 1
Jul 30 12:21:16.442: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:16.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:21:20.868: INFO: rc: 1
Jul 30 12:21:20.868: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:21.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:21:25.518: INFO: rc: 1
Jul 30 12:21:25.518: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:25.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:21:29.447: INFO: rc: 1
Jul 30 12:21:29.447: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:29.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:21:33.446: INFO: rc: 1
Jul 30 12:21:33.446: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:33.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:21:37.471: INFO: rc: 1
Jul 30 12:21:37.471: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:37.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:21:41.432: INFO: rc: 1
Jul 30 12:21:41.433: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:41.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:21:45.486: INFO: rc: 1
Jul 30 12:21:45.486: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:45.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:21:49.447: INFO: rc: 1
Jul 30 12:21:49.447: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:49.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:21:53.432: INFO: rc: 1
Jul 30 12:21:53.432: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:53.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:21:57.487: INFO: rc: 1
Jul 30 12:21:57.488: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:21:57.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:22:01.446: INFO: rc: 1
Jul 30 12:22:01.446: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:22:01.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:22:05.440: INFO: rc: 1
Jul 30 12:22:05.440: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:22:05.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:22:09.447: INFO: rc: 1
Jul 30 12:22:09.447: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:22:09.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:22:13.433: INFO: rc: 1
Jul 30 12:22:13.433: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:22:13.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:22:17.539: INFO: rc: 1
Jul 30 12:22:17.539: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:22:17.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:22:21.436: INFO: rc: 1
Jul 30 12:22:21.436: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:22:21.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:22:25.441: INFO: rc: 1
Jul 30 12:22:25.441: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:22:25.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:22:29.431: INFO: rc: 1
Jul 30 12:22:29.431: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:22:29.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:22:33.482: INFO: rc: 1
Jul 30 12:22:33.482: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:22:33.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:22:37.450: INFO: rc: 1
Jul 30 12:22:37.450: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:22:37.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:22:41.462: INFO: rc: 1
Jul 30 12:22:41.462: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:22:41.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:22:45.483: INFO: rc: 1
Jul 30 12:22:45.483: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:22:45.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:22:49.464: INFO: rc: 1
Jul 30 12:22:49.464: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:22:49.561: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:22:53.458: INFO: rc: 1
Jul 30 12:22:53.458: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:22:53.458: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540'
Jul 30 12:22:57.353: INFO: rc: 1
Jul 30 12:22:57.353: INFO: Service reachability failing with error: error running /tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=services-7361 exec execpodzgf6t -- /bin/sh -x -c nc -zv -t -w 2 172.20.45.65 30540:
Command stdout:

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

error:
exit status 1
Retrying...
Jul 30 12:22:57.353: FAIL: Unexpected error:
    <*errors.errorString | 0xc000b9e370>: {
        s: "service is not reachable within 2m0s timeout on endpoint 172.20.45.65:30540 over TCP protocol",
    }
    service is not reachable within 2m0s timeout on endpoint 172.20.45.65:30540 over TCP protocol
occurred

... skipping 192 lines ...
• Failure [261.451 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 [It]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:1562

  Jul 30 12:22:57.353: Unexpected error:
      <*errors.errorString | 0xc000b9e370>: {
          s: "service is not reachable within 2m0s timeout on endpoint 172.20.45.65:30540 over TCP protocol",
      }
      service is not reachable within 2m0s timeout on endpoint 172.20.45.65:30540 over TCP protocol
  occurred

  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:1617
------------------------------
{"msg":"FAILED [sig-network] Services should be able to update service type to NodePort listening on same port number but different protocols","total":-1,"completed":29,"skipped":224,"failed":4,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource with pruning [Conformance]","[sig-network] Services should implement service.kubernetes.io/headless","[sig-network] Services should be rejected when no endpoints exist","[sig-network] Services should be able to update service type to NodePort listening on same port number but different protocols"]}
Jul 30 12:23:04.840: INFO: Running AfterSuite actions on all nodes


[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
[BeforeEach] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
... skipping 116 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":31,"skipped":211,"failed":4,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a validating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource with different stored version [Conformance]","[sig-network] Services should create endpoints for unready pods","[sig-storage] PersistentVolumes NFS with Single PV - PVC pairs create a PV and a pre-bound PVC: test write access"]}
Jul 30 12:23:06.501: INFO: Running AfterSuite actions on all nodes


[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 158 lines ...
Jul 30 12:12:11.704: INFO: Running '/tmp/kubectl3379812399/kubectl --server=https://api.e2e-5b174bf702-4fc32.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-8247 create -f -'
Jul 30 12:12:12.658: INFO: stderr: ""
Jul 30 12:12:12.658: INFO: stdout: "deployment.apps/agnhost-replica created\n"
STEP: validating guestbook app
Jul 30 12:12:12.658: INFO: Waiting for all frontend pods to be Running.
Jul 30 12:12:17.858: INFO: Waiting for frontend to serve content.
Jul 30 12:13:08.055: INFO: Failed to get response from guestbook. err: the server rejected our request for an unknown reason (get services frontend), response: 
Jul 30 12:13:43.245: INFO: Failed to get response from guestbook. err: an error on the server ("unknown") has prevented the request from succeeding (get services frontend), response: k8s

v1Status\

FailureDerror trying to reach service: dial tcp 100.96.3.224:80: i/o timeout"0�"
Jul 30 12:14:38.441: INFO: Failed to get response from guestbook. err: the server rejected our request for an unknown reason (get services frontend), response: 
Jul 30 12:15:13.655: INFO: Failed to get response from guestbook. err: an error on the server ("unknown") has prevented the request from succeeding (get services frontend), response: k8s

v1Status\

FailureDerror trying to reach service: dial tcp 100.96.3.224:80: i/o timeout"0�"
Jul 30 12:15:48.845: INFO: Failed to get response from guestbook. err: an error on the server ("unknown") has prevented the request from succeeding (get services frontend), response: k8s

v1Status\

FailureDerror trying to reach service: dial tcp 100.96.1.218:80: i/o timeout"0�"
Jul 30 12:16:24.034: INFO: Failed to get response from guestbook. err: an error on the server ("unknown") has prevented the request from succeeding (get services frontend), response: k8s

v1Status\

FailureDerror trying to reach service: dial tcp 100.96.1.218:80: i/o timeout"0�"
Jul 30 12:16:59.223: INFO: Failed to get response from guestbook. err: an error on the server ("unknown") has prevented the request from succeeding (get services frontend), response: k8s

v1Status\

FailureDerror trying to reach service: dial tcp 100.96.3.224:80: i/o timeout"0�"
Jul 30 12:17:54.428: INFO: Failed to get response from guestbook. err: the server rejected our request for an unknown reason (get services frontend), response: 
Jul 30 12:18:29.619: INFO: Failed to get response from guestbook. err: an error on the server ("unknown") has prevented the request from succeeding (get services frontend), response: k8s

v1Status\

FailureDerror trying to reach service: dial tcp 100.96.1.218:80: i/o timeout"0�"
Jul 30 12:19:04.808: INFO: Failed to get response from guestbook. err: an error on the server ("unknown") has prevented the request from succeeding (get services frontend), response: k8s

v1Status\

FailureDerror trying to reach service: dial tcp 100.96.3.224:80: i/o timeout"0�"
Jul 30 12:20:00.001: INFO: Failed to get response from guestbook. err: the server rejected our request for an unknown reason (get services frontend), response: 
Jul 30 12:20:55.197: INFO: Failed to get response from guestbook. err: the server rejected our request for an unknown reason (get services frontend), response: 
Jul 30 12:21:30.386: INFO: Failed to get response from guestbook. err: an error on the server ("unknown") has prevented the request from succeeding (get services frontend), response: k8s

v1Status\

FailureDerror trying to reach service: dial tcp 100.96.1.218:80: i/o timeout"0�"
Jul 30 12:22:05.575: INFO: Failed to get response from guestbook. err: an error on the server ("unknown") has prevented the request from succeeding (get services frontend), response: k8s

v1Status\

FailureDerror trying to reach service: dial tcp 100.96.1.218:80: i/o timeout"0�"
Jul 30 12:23:00.773: INFO: Failed to get response from guestbook. err: the server rejected our request for an unknown reason (get services frontend), response: 
Jul 30 12:23:05.774: FAIL: Frontend service did not start serving content in 600 seconds.

Full Stack Trace
k8s.io/kubernetes/test/e2e/kubectl.glob..func1.7.2()
	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:378 +0x159
k8s.io/kubernetes/test/e2e.RunE2ETests(0xc00309c000)
	_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c
... skipping 44 lines ...
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:12:11 +0000 UTC - event for frontend-7659f66489-8xx4s: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/agnhost:2.21" already present on machine
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:12:11 +0000 UTC - event for frontend-7659f66489-8xx4s: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} Started: Started container guestbook-frontend
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:12:11 +0000 UTC - event for frontend-7659f66489-8xx4s: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} Created: Created container guestbook-frontend
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:12:11 +0000 UTC - event for frontend-7659f66489-msnh6: {kubelet ip-172-20-35-124.ap-southeast-2.compute.internal} Started: Started container guestbook-frontend
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:12:11 +0000 UTC - event for frontend-7659f66489-msnh6: {kubelet ip-172-20-35-124.ap-southeast-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/agnhost:2.21" already present on machine
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:12:11 +0000 UTC - event for frontend-7659f66489-msnh6: {kubelet ip-172-20-35-124.ap-southeast-2.compute.internal} Created: Created container guestbook-frontend
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:12:11 +0000 UTC - event for frontend-7659f66489-rhjwm: {kubelet ip-172-20-45-65.ap-southeast-2.compute.internal} FailedMount: MountVolume.SetUp failed for volume "default-token-dg92v" : failed to sync secret cache: timed out waiting for the condition
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:12:12 +0000 UTC - event for agnhost-primary-56857545d9-hhcvz: {kubelet ip-172-20-45-65.ap-southeast-2.compute.internal} Started: Started container primary
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:12:12 +0000 UTC - event for agnhost-primary-56857545d9-hhcvz: {kubelet ip-172-20-45-65.ap-southeast-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/agnhost:2.21" already present on machine
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:12:12 +0000 UTC - event for agnhost-primary-56857545d9-hhcvz: {kubelet ip-172-20-45-65.ap-southeast-2.compute.internal} Created: Created container primary
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:12:12 +0000 UTC - event for agnhost-replica: {deployment-controller } ScalingReplicaSet: Scaled up replica set agnhost-replica-55fd9c5577 to 2
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:12:12 +0000 UTC - event for agnhost-replica-55fd9c5577: {replicaset-controller } SuccessfulCreate: Created pod: agnhost-replica-55fd9c5577-r7j2p
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:12:12 +0000 UTC - event for agnhost-replica-55fd9c5577: {replicaset-controller } SuccessfulCreate: Created pod: agnhost-replica-55fd9c5577-wbwtv
... skipping 5 lines ...
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:12:13 +0000 UTC - event for agnhost-replica-55fd9c5577-r7j2p: {kubelet ip-172-20-35-124.ap-southeast-2.compute.internal} Created: Created container replica
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:12:13 +0000 UTC - event for agnhost-replica-55fd9c5577-r7j2p: {kubelet ip-172-20-35-124.ap-southeast-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/agnhost:2.21" already present on machine
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:12:13 +0000 UTC - event for agnhost-replica-55fd9c5577-r7j2p: {kubelet ip-172-20-35-124.ap-southeast-2.compute.internal} Started: Started container replica
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:12:13 +0000 UTC - event for agnhost-replica-55fd9c5577-wbwtv: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} Created: Created container replica
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:12:13 +0000 UTC - event for agnhost-replica-55fd9c5577-wbwtv: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/agnhost:2.21" already present on machine
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:12:13 +0000 UTC - event for agnhost-replica-55fd9c5577-wbwtv: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} Started: Started container replica
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:12:58 +0000 UTC - event for agnhost-replica-55fd9c5577-wbwtv: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} BackOff: Back-off restarting failed container
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:13:17 +0000 UTC - event for agnhost-replica-55fd9c5577-r7j2p: {kubelet ip-172-20-35-124.ap-southeast-2.compute.internal} BackOff: Back-off restarting failed container
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:23:09 +0000 UTC - event for frontend-7659f66489-8xx4s: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} Killing: Stopping container guestbook-frontend
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:23:09 +0000 UTC - event for frontend-7659f66489-msnh6: {kubelet ip-172-20-35-124.ap-southeast-2.compute.internal} Killing: Stopping container guestbook-frontend
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:23:09 +0000 UTC - event for frontend-7659f66489-rhjwm: {kubelet ip-172-20-45-65.ap-southeast-2.compute.internal} Killing: Stopping container guestbook-frontend
Jul 30 12:23:11.555: INFO: At 2021-07-30 12:23:10 +0000 UTC - event for agnhost-primary-56857545d9-hhcvz: {kubelet ip-172-20-45-65.ap-southeast-2.compute.internal} Killing: Stopping container primary
Jul 30 12:23:11.744: INFO: POD                               NODE                                              PHASE    GRACE  CONDITIONS
Jul 30 12:23:11.744: INFO: agnhost-primary-56857545d9-hhcvz  ip-172-20-45-65.ap-southeast-2.compute.internal   Running  30s    [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2021-07-30 12:12:11 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2021-07-30 12:23:10 +0000 UTC ContainersNotReady containers with unready status: [primary]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2021-07-30 12:23:10 +0000 UTC ContainersNotReady containers with unready status: [primary]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2021-07-30 12:12:11 +0000 UTC  }]
... skipping 146 lines ...
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629

    Jul 30 12:23:05.774: Frontend service did not start serving content in 600 seconds.

    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:378
------------------------------
{"msg":"FAILED [sig-cli] Kubectl client Guestbook application should create and stop a working application  [Conformance]","total":-1,"completed":7,"skipped":80,"failed":2,"failures":["[sig-network] DNS should provide /etc/hosts entries for the cluster [LinuxOnly] [Conformance]","[sig-cli] Kubectl client Guestbook application should create and stop a working application  [Conformance]"]}
Jul 30 12:23:18.580: INFO: Running AfterSuite actions on all nodes


[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 22 lines ...
Jul 30 12:18:04.259: INFO: PersistentVolume nfs-dwcrd found and phase=Bound (187.889118ms)
Jul 30 12:18:04.447: INFO: Waiting up to 3m0s for PersistentVolumeClaims [pvc-4lwjf] to have phase Bound
Jul 30 12:18:04.635: INFO: PersistentVolumeClaim pvc-4lwjf found and phase=Bound (188.10989ms)
STEP: Checking pod has write access to PersistentVolumes
Jul 30 12:18:04.823: INFO: Creating nfs test pod
Jul 30 12:18:05.012: INFO: Pod should terminate with exitcode 0 (success)
Jul 30 12:18:05.012: INFO: Waiting up to 5m0s for pod "pvc-tester-v4sdw" in namespace "pv-108" to be "Succeeded or Failed"
Jul 30 12:18:05.200: INFO: Pod "pvc-tester-v4sdw": Phase="Pending", Reason="", readiness=false. Elapsed: 187.610951ms
Jul 30 12:18:07.389: INFO: Pod "pvc-tester-v4sdw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.37615118s
Jul 30 12:18:09.577: INFO: Pod "pvc-tester-v4sdw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.564550069s
Jul 30 12:18:11.765: INFO: Pod "pvc-tester-v4sdw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.752502852s
Jul 30 12:18:13.954: INFO: Pod "pvc-tester-v4sdw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.94185808s
Jul 30 12:18:16.142: INFO: Pod "pvc-tester-v4sdw": Phase="Pending", Reason="", readiness=false. Elapsed: 11.129830464s
... skipping 128 lines ...
Jul 30 12:22:58.471: INFO: Pod "pvc-tester-v4sdw": Phase="Pending", Reason="", readiness=false. Elapsed: 4m53.458722878s
Jul 30 12:23:00.660: INFO: Pod "pvc-tester-v4sdw": Phase="Pending", Reason="", readiness=false. Elapsed: 4m55.647154752s
Jul 30 12:23:02.848: INFO: Pod "pvc-tester-v4sdw": Phase="Pending", Reason="", readiness=false. Elapsed: 4m57.835987259s
Jul 30 12:23:05.037: INFO: Pod "pvc-tester-v4sdw": Phase="Pending", Reason="", readiness=false. Elapsed: 5m0.024204486s
Jul 30 12:23:07.037: INFO: Deleting pod "pvc-tester-v4sdw" in namespace "pv-108"
Jul 30 12:23:07.228: INFO: Wait up to 5m0s for pod "pvc-tester-v4sdw" to be fully deleted
Jul 30 12:23:11.605: FAIL: Unexpected error:
    <*errors.errorString | 0xc000b14aa0>: {
        s: "pod \"pvc-tester-v4sdw\" did not exit with Success: pod \"pvc-tester-v4sdw\" failed to reach Success: Gave up after waiting 5m0s for pod \"pvc-tester-v4sdw\" to be \"Succeeded or Failed\"",
    }
    pod "pvc-tester-v4sdw" did not exit with Success: pod "pvc-tester-v4sdw" failed to reach Success: Gave up after waiting 5m0s for pod "pvc-tester-v4sdw" to be "Succeeded or Failed"
occurred

Full Stack Trace
k8s.io/kubernetes/test/e2e/storage.glob..func21.2.4.2()
	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes.go:238 +0x365
k8s.io/kubernetes/test/e2e.RunE2ETests(0xc0025a1e00)
... skipping 26 lines ...
Jul 30 12:23:17.495: INFO: At 2021-07-30 12:17:59 +0000 UTC - event for nfs-server: {kubelet ip-172-20-60-194.ap-southeast-2.compute.internal} Created: Created container nfs-server
Jul 30 12:23:17.495: INFO: At 2021-07-30 12:17:59 +0000 UTC - event for nfs-server: {kubelet ip-172-20-60-194.ap-southeast-2.compute.internal} Started: Started container nfs-server
Jul 30 12:23:17.495: INFO: At 2021-07-30 12:18:03 +0000 UTC - event for pvc-kxgw8: {persistentvolume-controller } FailedBinding: no persistent volumes available for this claim and no storage class is set
Jul 30 12:23:17.495: INFO: At 2021-07-30 12:18:03 +0000 UTC - event for pvc-x6fx8: {persistentvolume-controller } FailedBinding: no persistent volumes available for this claim and no storage class is set
Jul 30 12:23:17.495: INFO: At 2021-07-30 12:18:04 +0000 UTC - event for pvc-tester-v4sdw: {default-scheduler } Scheduled: Successfully assigned pv-108/pvc-tester-v4sdw to ip-172-20-33-146.ap-southeast-2.compute.internal
Jul 30 12:23:17.495: INFO: At 2021-07-30 12:20:07 +0000 UTC - event for pvc-tester-v4sdw: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume1], unattached volumes=[volume1 default-token-nm9gz]: timed out waiting for the condition
Jul 30 12:23:17.495: INFO: At 2021-07-30 12:22:22 +0000 UTC - event for pvc-tester-v4sdw: {kubelet ip-172-20-33-146.ap-southeast-2.compute.internal} FailedMount: MountVolume.SetUp failed for volume "nfs-fxwfs" : mount failed: exit status 32
Mounting command: mount
Mounting arguments: -t nfs 100.96.4.98:/exports /var/lib/kubelet/pods/66a1c35a-4b81-4052-89ee-2659c39f6620/volumes/kubernetes.io~nfs/nfs-fxwfs
Output: mount.nfs: Connection timed out

Jul 30 12:23:17.495: INFO: At 2021-07-30 12:23:12 +0000 UTC - event for nfs-server: {kubelet ip-172-20-60-194.ap-southeast-2.compute.internal} Killing: Stopping container nfs-server
Jul 30 12:23:17.683: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
... skipping 134 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 [It]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes.go:233

      Jul 30 12:23:11.605: Unexpected error:
          <*errors.errorString | 0xc000b14aa0>: {
              s: "pod \"pvc-tester-v4sdw\" did not exit with Success: pod \"pvc-tester-v4sdw\" failed to reach Success: Gave up after waiting 5m0s for pod \"pvc-tester-v4sdw\" to be \"Succeeded or Failed\"",
          }
          pod "pvc-tester-v4sdw" did not exit with Success: pod "pvc-tester-v4sdw" failed to reach Success: Gave up after waiting 5m0s for pod "pvc-tester-v4sdw" to be "Succeeded or Failed"
      occurred

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes.go:238
------------------------------
{"msg":"FAILED [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":28,"skipped":220,"failed":3,"failures":["[sig-cli] Kubectl client Simple pod should handle in-cluster config","[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","[sig-storage] PersistentVolumes NFS with multiple PVs and PVCs all in same ns should create 2 PVs and 4 PVCs: test write access"]}
Jul 30 12:23:24.469: INFO: Running AfterSuite actions on all nodes


[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 18 lines ...
• [SLOW TEST:245.308 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 exec "cat /tmp/health" 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 exec \"cat /tmp/health\" liveness probe [NodeConformance] [Conformance]","total":-1,"completed":25,"skipped":253,"failed":3,"failures":["[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]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should not be able to mutate or prevent deletion of webhook configuration objects [Conformance]","[sig-storage] PersistentVolumes NFS when invoking the Recycle reclaim policy should test that a PV becomes Available and is clean after the PVC is deleted."]}
Jul 30 12:24:02.786: INFO: Running AfterSuite actions on all nodes


[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 262 lines ...
  ----    ------     ----  ----               -------
  Normal  Scheduled  36s   default-scheduler  Successfully assigned pod-network-test-2786/netserver-3 to ip-172-20-60-194.ap-southeast-2.compute.internal
  Normal  Pulled     35s   kubelet            Container image "k8s.gcr.io/e2e-test-images/agnhost:2.21" already present on machine
  Normal  Created    35s   kubelet            Created container webserver
  Normal  Started    35s   kubelet            Started container webserver

Jul 30 12:04:31.130: INFO: encountered error during dial (did not find expected responses... 
Tries 1
Command curl -g -q -s 'http://100.96.3.146:9080/dial?request=hostname&protocol=udp&host=100.96.1.130&port=8081&tries=1'
retrieved map[]
expected map[netserver-0:{}])
Jul 30 12:04:31.130: INFO: ...failed...will try again in next pass
Jul 30 12:04:31.130: INFO: Breadth first check of 100.96.3.139 on host 172.20.35.124...
Jul 30 12:04:31.321: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s 'http://100.96.3.146:9080/dial?request=hostname&protocol=udp&host=100.96.3.139&port=8081&tries=1'] Namespace:pod-network-test-2786 PodName:test-container-pod ContainerName:webserver Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:04:31.321: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:04:32.563: INFO: Waiting for responses: map[]
Jul 30 12:04:32.563: INFO: reached 100.96.3.139 after 0/1 tries
Jul 30 12:04:32.563: INFO: Breadth first check of 100.96.2.102 on host 172.20.45.65...
... skipping 237 lines ...
  ----    ------     ----  ----               -------
  Normal  Scheduled  50s   default-scheduler  Successfully assigned pod-network-test-2786/netserver-3 to ip-172-20-60-194.ap-southeast-2.compute.internal
  Normal  Pulled     49s   kubelet            Container image "k8s.gcr.io/e2e-test-images/agnhost:2.21" already present on machine
  Normal  Created    49s   kubelet            Created container webserver
  Normal  Started    49s   kubelet            Started container webserver

Jul 30 12:04:45.167: INFO: encountered error during dial (did not find expected responses... 
Tries 1
Command curl -g -q -s 'http://100.96.3.146:9080/dial?request=hostname&protocol=udp&host=100.96.2.102&port=8081&tries=1'
retrieved map[]
expected map[netserver-2:{}])
Jul 30 12:04:45.167: INFO: ...failed...will try again in next pass
Jul 30 12:04:45.167: INFO: Breadth first check of 100.96.4.168 on host 172.20.60.194...
Jul 30 12:04:45.358: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s 'http://100.96.3.146:9080/dial?request=hostname&protocol=udp&host=100.96.4.168&port=8081&tries=1'] Namespace:pod-network-test-2786 PodName:test-container-pod ContainerName:webserver Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:04:45.358: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:04:51.568: INFO: Waiting for responses: map[netserver-3:{}]
Jul 30 12:04:53.568: INFO: 
Output of kubectl describe pod pod-network-test-2786/netserver-0:
... skipping 232 lines ...
  ----    ------     ----  ----               -------
  Normal  Scheduled  62s   default-scheduler  Successfully assigned pod-network-test-2786/netserver-3 to ip-172-20-60-194.ap-southeast-2.compute.internal
  Normal  Pulled     61s   kubelet            Container image "k8s.gcr.io/e2e-test-images/agnhost:2.21" already present on machine
  Normal  Created    61s   kubelet            Created container webserver
  Normal  Started    61s   kubelet            Started container webserver

Jul 30 12:04:57.775: INFO: encountered error during dial (did not find expected responses... 
Tries 1
Command curl -g -q -s 'http://100.96.3.146:9080/dial?request=hostname&protocol=udp&host=100.96.4.168&port=8081&tries=1'
retrieved map[]
expected map[netserver-3:{}])
Jul 30 12:04:57.775: INFO: ...failed...will try again in next pass
Jul 30 12:04:57.775: INFO: Going to retry 3 out of 4 pods....
Jul 30 12:04:57.775: INFO: Doublechecking 1 pods in host 172.20.33.146 which werent seen the first time.
Jul 30 12:04:57.775: INFO: Now attempting to probe pod [[[ 100.96.1.130 ]]]
Jul 30 12:04:57.967: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s 'http://100.96.3.146:9080/dial?request=hostname&protocol=udp&host=100.96.1.130&port=8081&tries=1'] Namespace:pod-network-test-2786 PodName:test-container-pod ContainerName:webserver Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:04:57.967: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:05:04.174: INFO: Waiting for responses: map[netserver-0:{}]
... skipping 369 lines ...
  ----    ------     ----   ----               -------
  Normal  Scheduled  7m34s  default-scheduler  Successfully assigned pod-network-test-2786/netserver-3 to ip-172-20-60-194.ap-southeast-2.compute.internal
  Normal  Pulled     7m33s  kubelet            Container image "k8s.gcr.io/e2e-test-images/agnhost:2.21" already present on machine
  Normal  Created    7m33s  kubelet            Created container webserver
  Normal  Started    7m33s  kubelet            Started container webserver

Jul 30 12:11:29.185: INFO: encountered error during dial (did not find expected responses... 
Tries 46
Command curl -g -q -s 'http://100.96.3.146:9080/dial?request=hostname&protocol=udp&host=100.96.1.130&port=8081&tries=1'
retrieved map[]
expected map[netserver-0:{}])
Jul 30 12:11:29.185: INFO: ... Done probing pod [[[ 100.96.1.130 ]]]
Jul 30 12:11:29.185: INFO: succeeded at polling 3 out of 4 connections
... skipping 374 lines ...
  ----    ------     ----  ----               -------
  Normal  Scheduled  14m   default-scheduler  Successfully assigned pod-network-test-2786/netserver-3 to ip-172-20-60-194.ap-southeast-2.compute.internal
  Normal  Pulled     14m   kubelet            Container image "k8s.gcr.io/e2e-test-images/agnhost:2.21" already present on machine
  Normal  Created    14m   kubelet            Created container webserver
  Normal  Started    14m   kubelet            Started container webserver

Jul 30 12:18:00.785: INFO: encountered error during dial (did not find expected responses... 
Tries 46
Command curl -g -q -s 'http://100.96.3.146:9080/dial?request=hostname&protocol=udp&host=100.96.2.102&port=8081&tries=1'
retrieved map[]
expected map[netserver-2:{}])
Jul 30 12:18:00.785: INFO: ... Done probing pod [[[ 100.96.2.102 ]]]
Jul 30 12:18:00.785: INFO: succeeded at polling 2 out of 4 connections
... skipping 374 lines ...
  ----    ------     ----  ----               -------
  Normal  Scheduled  20m   default-scheduler  Successfully assigned pod-network-test-2786/netserver-3 to ip-172-20-60-194.ap-southeast-2.compute.internal
  Normal  Pulled     20m   kubelet            Container image "k8s.gcr.io/e2e-test-images/agnhost:2.21" already present on machine
  Normal  Created    20m   kubelet            Created container webserver
  Normal  Started    20m   kubelet            Started container webserver

Jul 30 12:24:32.329: INFO: encountered error during dial (did not find expected responses... 
Tries 46
Command curl -g -q -s 'http://100.96.3.146:9080/dial?request=hostname&protocol=udp&host=100.96.4.168&port=8081&tries=1'
retrieved map[]
expected map[netserver-3:{}])
Jul 30 12:24:32.329: INFO: ... Done probing pod [[[ 100.96.4.168 ]]]
Jul 30 12:24:32.329: INFO: succeeded at polling 1 out of 4 connections
Jul 30 12:24:32.329: INFO: pod polling failure summary:
Jul 30 12:24:32.329: INFO: Collected error: did not find expected responses... 
Tries 46
Command curl -g -q -s 'http://100.96.3.146:9080/dial?request=hostname&protocol=udp&host=100.96.1.130&port=8081&tries=1'
retrieved map[]
expected map[netserver-0:{}]
Jul 30 12:24:32.329: INFO: Collected error: did not find expected responses... 
Tries 46
Command curl -g -q -s 'http://100.96.3.146:9080/dial?request=hostname&protocol=udp&host=100.96.2.102&port=8081&tries=1'
retrieved map[]
expected map[netserver-2:{}]
Jul 30 12:24:32.329: INFO: Collected error: did not find expected responses... 
Tries 46
Command curl -g -q -s 'http://100.96.3.146:9080/dial?request=hostname&protocol=udp&host=100.96.4.168&port=8081&tries=1'
retrieved map[]
expected map[netserver-3:{}]
Jul 30 12:24:32.329: FAIL: failed,  3 out of 4 connections failed

Full Stack Trace
k8s.io/kubernetes/test/e2e/common.glob..func16.1.3()
	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/networking.go:93 +0x69
k8s.io/kubernetes/test/e2e.RunE2ETests(0xc003858480)
	_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c
... skipping 158 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/networking.go:27
  Granular Checks: Pods
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/networking.go:30
    should function for intra-pod communication: udp [NodeConformance] [Conformance] [It]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629

    Jul 30 12:24:32.330: failed,  3 out of 4 connections failed

    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/networking.go:93
------------------------------
{"msg":"FAILED [sig-network] Networking Granular Checks: Pods should function for intra-pod communication: udp [NodeConformance] [Conformance]","total":-1,"completed":9,"skipped":82,"failed":2,"failures":["[sig-network] Services should allow pods to hairpin back to themselves through services","[sig-network] Networking Granular Checks: Pods should function for intra-pod communication: udp [NodeConformance] [Conformance]"]}
Jul 30 12:24:39.427: INFO: Running AfterSuite actions on all nodes


[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 263 lines ...
  ----    ------     ----  ----               -------
  Normal  Scheduled  38s   default-scheduler  Successfully assigned pod-network-test-9222/netserver-3 to ip-172-20-60-194.ap-southeast-2.compute.internal
  Normal  Pulled     37s   kubelet            Container image "k8s.gcr.io/e2e-test-images/agnhost:2.21" already present on machine
  Normal  Created    37s   kubelet            Created container webserver
  Normal  Started    37s   kubelet            Started container webserver

Jul 30 12:13:54.266: INFO: encountered error during dial (did not find expected responses... 
Tries 1
Command curl -g -q -s 'http://100.96.2.246:9080/dial?request=hostname&protocol=http&host=100.96.1.235&port=8080&tries=1'
retrieved map[]
expected map[netserver-0:{}])
Jul 30 12:13:54.266: INFO: ...failed...will try again in next pass
Jul 30 12:13:54.266: INFO: Breadth first check of 100.96.3.246 on host 172.20.35.124...
Jul 30 12:13:54.454: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s 'http://100.96.2.246:9080/dial?request=hostname&protocol=http&host=100.96.3.246&port=8080&tries=1'] Namespace:pod-network-test-9222 PodName:test-container-pod ContainerName:webserver Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:13:54.454: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:14:00.683: INFO: Waiting for responses: map[netserver-1:{}]
Jul 30 12:14:02.683: INFO: 
Output of kubectl describe pod pod-network-test-9222/netserver-0:
... skipping 232 lines ...
  ----    ------     ----  ----               -------
  Normal  Scheduled  50s   default-scheduler  Successfully assigned pod-network-test-9222/netserver-3 to ip-172-20-60-194.ap-southeast-2.compute.internal
  Normal  Pulled     49s   kubelet            Container image "k8s.gcr.io/e2e-test-images/agnhost:2.21" already present on machine
  Normal  Created    49s   kubelet            Created container webserver
  Normal  Started    49s   kubelet            Started container webserver

Jul 30 12:14:06.870: INFO: encountered error during dial (did not find expected responses... 
Tries 1
Command curl -g -q -s 'http://100.96.2.246:9080/dial?request=hostname&protocol=http&host=100.96.3.246&port=8080&tries=1'
retrieved map[]
expected map[netserver-1:{}])
Jul 30 12:14:06.870: INFO: ...failed...will try again in next pass
Jul 30 12:14:06.870: INFO: Breadth first check of 100.96.2.243 on host 172.20.45.65...
Jul 30 12:14:07.058: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s 'http://100.96.2.246:9080/dial?request=hostname&protocol=http&host=100.96.2.243&port=8080&tries=1'] Namespace:pod-network-test-9222 PodName:test-container-pod ContainerName:webserver Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Jul 30 12:14:07.058: INFO: >>> kubeConfig: /root/.kube/config
Jul 30 12:14:08.266: INFO: Waiting for responses: map[]
Jul 30 12:14:08.266: INFO: reached 100.96.2.243 after 0/1 tries
Jul 30 12:14:08.266: INFO: Breadth first check of 100.96.4.34 on host 172.20.60.194...
... skipping 379 lines ...
  ----    ------     ----   ----               -------
  Normal  Scheduled  7m25s  default-scheduler  Successfully assigned pod-network-test-9222/netserver-3 to ip-172-20-60-194.ap-southeast-2.compute.internal
  Normal  Pulled     7m24s  kubelet            Container image "k8s.gcr.io/e2e-test-images/agnhost:2.21" already present on machine
  Normal  Created    7m24s  kubelet            Created container webserver
  Normal  Started    7m24s  kubelet            Started container webserver

Jul 30 12:20:41.371: INFO: encountered error during dial (did not find expected responses... 
Tries 46
Command curl -g -q -s 'http://100.96.2.246:9080/dial?request=hostname&protocol=http&host=100.96.1.235&port=8080&tries=1'
retrieved map[]
expected map[netserver-0:{}])
Jul 30 12:20:41.371: INFO: ... Done probing pod [[[ 100.96.1.235 ]]]
Jul 30 12:20:41.371: INFO: succeeded at polling 3 out of 4 connections
... skipping 374 lines ...
  ----    ------     ----  ----               -------
  Normal  Scheduled  13m   default-scheduler  Successfully assigned pod-network-test-9222/netserver-3 to ip-172-20-60-194.ap-southeast-2.compute.internal
  Normal  Pulled     13m   kubelet            Container image "k8s.gcr.io/e2e-test-images/agnhost:2.21" already present on machine
  Normal  Created    13m   kubelet            Created container webserver
  Normal  Started    13m   kubelet            Started container webserver

Jul 30 12:27:13.708: INFO: encountered error during dial (did not find expected responses... 
Tries 46
Command curl -g -q -s 'http://100.96.2.246:9080/dial?request=hostname&protocol=http&host=100.96.3.246&port=8080&tries=1'
retrieved map[]
expected map[netserver-1:{}])
Jul 30 12:27:13.708: INFO: ... Done probing pod [[[ 100.96.3.246 ]]]
Jul 30 12:27:13.708: INFO: succeeded at polling 2 out of 4 connections
Jul 30 12:27:13.708: INFO: pod polling failure summary:
Jul 30 12:27:13.708: INFO: Collected error: did not find expected responses... 
Tries 46
Command curl -g -q -s 'http://100.96.2.246:9080/dial?request=hostname&protocol=http&host=100.96.1.235&port=8080&tries=1'
retrieved map[]
expected map[netserver-0:{}]
Jul 30 12:27:13.708: INFO: Collected error: did not find expected responses... 
Tries 46
Command curl -g -q -s 'http://100.96.2.246:9080/dial?request=hostname&protocol=http&host=100.96.3.246&port=8080&tries=1'
retrieved map[]
expected map[netserver-1:{}]
Jul 30 12:27:13.708: FAIL: failed,  2 out of 4 connections failed

Full Stack Trace
k8s.io/kubernetes/test/e2e/common.glob..func16.1.2()
	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/networking.go:82 +0x69
k8s.io/kubernetes/test/e2e.RunE2ETests(0xc001bb4300)
	_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c
... skipping 148 lines ...
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/networking.go:27
  Granular Checks: Pods
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/networking.go:30
    should function for intra-pod communication: http [NodeConformance] [Conformance] [It]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629

    Jul 30 12:27:13.708: failed,  2 out of 4 connections failed

    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/networking.go:82
------------------------------
{"msg":"FAILED [sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]","total":-1,"completed":13,"skipped":84,"failed":3,"failures":["[sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: blockfs] [Testpattern: Pre-provisioned PV (default fs)] volumes should store data","[sig-network] DNS should provide DNS for pods for Hostname [LinuxOnly] [Conformance]","[sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]"]}
Jul 30 12:27:23.328: INFO: Running AfterSuite actions on all nodes


[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
... skipping 28 lines ...
Jul 30 12:17:38.723: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:38.914: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:39.104: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:39.295: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:39.485: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:39.675: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:39.675: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:17:44.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:45.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:45.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:45.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:45.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:17:47.564: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:47.797: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:47.988: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:48.178: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:48.369: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:48.560: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:48.560: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:17:49.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:50.056: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:50.247: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:50.437: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:50.628: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:17:52.539: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:52.730: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:52.922: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:53.113: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:53.304: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:53.495: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:53.495: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:17:54.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:55.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:55.247: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:55.438: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:55.628: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:17:57.534: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:57.725: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:57.915: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:58.106: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:58.300: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:58.491: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:17:58.491: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:17:59.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:00.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:00.251: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:00.445: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:00.636: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:18:02.550: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:02.742: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:02.934: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:03.125: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:03.316: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:03.512: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:03.512: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:18:04.869: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:05.061: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:05.252: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:05.444: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:05.635: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:18:07.552: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:07.743: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:07.934: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:08.124: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:08.315: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:08.505: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:08.505: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:18:09.867: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:10.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:10.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:10.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:10.630: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:18:12.535: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:12.725: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:12.916: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:13.107: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:13.297: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:13.488: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:13.488: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:18:14.869: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:15.059: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:15.250: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:15.441: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:15.631: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:18:17.538: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:17.729: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:17.919: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:18.109: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:18.303: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:18.493: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:18.493: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:18:19.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:20.056: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:20.247: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:20.442: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:20.633: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:18:22.543: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:22.733: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:22.923: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:23.114: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:23.305: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:23.495: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:23.495: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:18:24.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:25.056: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:25.249: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:25.440: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:25.631: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:18:27.537: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:27.728: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:27.919: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:28.109: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:28.300: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:28.491: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:28.491: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:18:29.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:30.056: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:30.247: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:30.438: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:30.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:18:32.543: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:32.733: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:32.923: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:33.114: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:33.304: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:33.494: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:33.495: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:18:34.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:35.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:35.247: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:35.438: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:35.628: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:18:37.535: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:37.726: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:37.916: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:38.108: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:38.298: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:38.489: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:38.489: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:18:39.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:40.056: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:40.249: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:40.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:40.630: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:18:42.536: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:42.726: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:42.917: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:43.113: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:43.304: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:43.494: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:43.494: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:18:44.867: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:45.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:45.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:45.449: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:45.640: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:18:47.546: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:47.737: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:47.928: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:48.119: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:48.309: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:48.503: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:48.503: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:18:49.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:50.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:50.247: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:50.438: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:50.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:18:52.541: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:52.731: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:52.928: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:53.119: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:53.311: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:53.501: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:53.502: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:18:54.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:55.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:55.247: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:55.438: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:55.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:18:57.534: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:57.724: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:57.915: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:58.105: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:58.296: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:58.487: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:18:58.487: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:18:59.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:00.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:00.247: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:00.438: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:00.628: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:19:02.545: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:02.737: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:02.928: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:03.118: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:03.311: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:03.501: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:03.501: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:19:04.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:05.058: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:05.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:05.440: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:05.630: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:19:07.537: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:07.727: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:07.918: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:08.109: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:08.299: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:08.491: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:08.491: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:19:09.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:10.056: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:10.247: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:10.438: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:10.628: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:19:12.534: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:12.724: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:12.915: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:13.108: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:13.298: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:13.488: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:13.488: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:19:14.867: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:15.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:15.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:15.461: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:15.652: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:19:17.559: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:17.750: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:17.940: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:18.131: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:18.322: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:18.512: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:18.512: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:19:19.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:20.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:20.247: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:20.438: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:20.628: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:19:22.540: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:22.731: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:22.923: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:23.118: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:23.310: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:23.500: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:23.500: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:19:24.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:25.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:25.247: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:25.438: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:25.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:19:27.600: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:27.792: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:27.983: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:28.176: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:28.391: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:28.583: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:28.583: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:19:29.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:30.056: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:30.247: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:30.437: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:30.628: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:19:32.533: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:32.730: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:32.920: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:33.115: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:33.306: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:33.496: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:33.496: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:19:34.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:35.059: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:35.269: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:35.476: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:35.668: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:19:37.580: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:37.771: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:37.961: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:38.152: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:38.342: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:38.533: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:38.533: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:19:39.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:40.059: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:40.249: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:40.440: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:40.638: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:19:42.547: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:42.742: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:42.932: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:43.125: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:43.315: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:43.505: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:43.505: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:19:44.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:45.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:45.247: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:45.437: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:45.631: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:19:47.537: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:47.727: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:47.918: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:48.109: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:48.299: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:48.490: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:48.490: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:19:49.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:50.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:50.250: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:50.440: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:50.630: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:19:52.556: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:52.747: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:52.939: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:53.130: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:53.320: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:53.510: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:53.510: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:19:54.867: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:55.059: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:55.249: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:55.440: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:55.631: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:19:57.540: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:57.731: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:57.923: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:58.113: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:58.304: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:58.494: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:19:58.494: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:19:59.867: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:00.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:00.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:00.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:00.631: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:20:02.591: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:02.781: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:02.971: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:03.162: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:03.353: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:03.548: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:03.548: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:20:04.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:05.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:05.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:05.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:05.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:20:07.537: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:07.728: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:07.921: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:08.113: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:08.303: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:08.494: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:08.494: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:20:09.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:10.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:10.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:10.438: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:10.628: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:20:12.532: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:12.723: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:12.913: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:13.104: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:13.296: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:13.486: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:13.486: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:20:14.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:15.058: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:15.249: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:15.440: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:15.630: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:20:17.543: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:17.733: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:17.924: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:18.115: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:18.305: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:18.496: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:18.496: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:20:19.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:20.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:20.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:20.438: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:20.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:20:22.541: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:22.731: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:22.922: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:23.113: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:23.304: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:23.494: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:23.494: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:20:24.868: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:25.058: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:25.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:25.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:25.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:20:27.535: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:27.726: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:27.916: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:28.107: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:28.300: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:28.490: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:28.490: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:20:29.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:30.056: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:30.247: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:30.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:30.630: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:20:32.536: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:32.727: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:32.918: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:33.108: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:33.299: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:33.490: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:33.490: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:20:34.871: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:35.066: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:35.267: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:35.467: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:35.660: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:20:37.571: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:37.762: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:37.953: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:38.144: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:38.334: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:38.530: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:38.530: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:20:39.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:40.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:40.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:40.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:40.630: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:20:42.541: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:42.731: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:42.922: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:43.112: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:43.303: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:43.493: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:43.493: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:20:44.867: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:45.058: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:45.249: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:45.440: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:45.630: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:20:47.539: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:47.730: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:47.921: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:48.111: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:48.302: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:48.493: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:48.493: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:20:49.870: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:50.061: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:50.252: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:50.457: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:50.647: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:20:52.557: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:52.748: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:52.940: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:53.131: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:53.322: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:53.512: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:53.512: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:20:54.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:55.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:55.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:55.438: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:55.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:20:57.539: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:57.729: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:57.920: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:58.111: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:58.301: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:58.497: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:20:58.498: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:20:59.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:00.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:00.247: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:00.438: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:00.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:21:02.542: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:02.733: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:02.924: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:03.144: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:03.335: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:03.526: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:03.526: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:21:04.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:05.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:05.247: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:05.438: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:05.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:21:07.539: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:07.729: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:07.920: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:08.112: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:08.302: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:08.493: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:08.493: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:21:09.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:10.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:10.247: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:10.438: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:10.628: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:21:12.537: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:12.728: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:12.918: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:13.109: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:13.299: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:13.489: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:13.489: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:21:14.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:15.058: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:15.249: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:15.440: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:15.630: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:21:17.553: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:17.744: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:17.935: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:18.126: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:18.318: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:18.509: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:18.509: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:21:19.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:20.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:20.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:20.442: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:20.632: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:21:22.542: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:22.733: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:22.928: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:23.120: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:23.314: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:23.551: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:23.551: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:21:24.868: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:25.058: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:25.249: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:25.440: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:25.631: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:21:27.569: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:27.760: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:27.952: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:28.142: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:28.334: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:28.525: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:28.525: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:21:29.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:30.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:30.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:30.438: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:30.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:21:32.538: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:32.728: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:32.919: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:33.109: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:33.299: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:33.491: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:33.491: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:21:34.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:35.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:35.249: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:35.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:35.630: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:21:37.542: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:37.733: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:37.924: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:38.115: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:38.305: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:38.496: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:38.496: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:21:39.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:40.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:40.247: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:40.438: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:40.628: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:21:42.535: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:42.725: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:42.916: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:43.106: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:43.297: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:43.487: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:43.488: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:21:44.867: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:45.058: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:45.251: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:45.442: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:45.632: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:21:47.539: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:47.730: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:47.921: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:48.112: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:48.302: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:48.493: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:48.493: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:21:49.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:50.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:50.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:50.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:50.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:21:52.544: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:52.735: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:52.926: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:53.117: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:53.308: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:53.499: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:53.499: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:21:54.867: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:55.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:55.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:55.440: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:55.631: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:21:57.538: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:57.729: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:57.919: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:58.110: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:58.300: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:58.490: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:21:58.490: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:21:59.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:00.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:00.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:00.438: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:00.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:22:02.540: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:02.731: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:02.921: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:03.112: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:03.303: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:03.493: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:03.493: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:22:04.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:05.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:05.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:05.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:05.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:22:07.542: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:07.733: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:07.924: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:08.114: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:08.305: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:08.496: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:08.496: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:22:09.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:10.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:10.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:10.438: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:10.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:22:12.537: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:12.728: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:12.919: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:13.109: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:13.300: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:13.491: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:13.491: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:22:14.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:15.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:15.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:15.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:15.630: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:22:17.537: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:17.728: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:17.919: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:18.109: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:18.300: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:18.490: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:18.490: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:22:19.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:20.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:20.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:20.438: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:20.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:22:22.537: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:22.727: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:22.918: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:23.109: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:23.299: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:23.490: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:23.490: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:22:24.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:25.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:25.247: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:25.438: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:25.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:22:27.540: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:27.731: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:27.921: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:28.113: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:28.304: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:28.494: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:28.495: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:22:29.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:30.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:30.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:30.438: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:30.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:22:32.538: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:32.728: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:32.919: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:33.110: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:33.300: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:33.496: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:33.497: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:22:34.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:35.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:35.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:35.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:35.630: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:22:37.538: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:37.729: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:37.920: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:38.110: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:38.301: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:38.492: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:38.492: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:22:39.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:40.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:40.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:40.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:40.630: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:22:42.538: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:42.729: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:42.920: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:43.111: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:43.302: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:43.493: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:43.493: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:22:44.867: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:45.058: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:45.249: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:45.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:45.630: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:22:47.539: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:47.730: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:47.921: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:48.111: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:48.302: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:48.493: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:48.493: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:22:49.867: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:50.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:50.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:50.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:50.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:22:52.540: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:52.731: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:52.922: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:53.113: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:53.304: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:53.494: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:53.495: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:22:54.867: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:55.058: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:55.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:55.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:55.630: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:22:57.537: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:57.728: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:57.919: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:58.110: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:58.301: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:58.492: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:22:58.492: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:22:59.867: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:00.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:00.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:00.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:00.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:23:02.539: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:02.729: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:02.921: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:03.112: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:03.303: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:03.494: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:03.494: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:23:04.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:05.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:05.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:05.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:05.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:23:07.540: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:07.732: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:07.924: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:08.115: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:08.306: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:08.497: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:08.497: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:23:09.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:10.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:10.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:10.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:10.630: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:23:12.536: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:12.726: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:12.917: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:13.108: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:13.298: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:13.489: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:13.489: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:23:14.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:15.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:15.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:15.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:15.631: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:23:17.538: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:17.729: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:17.920: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:18.110: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:18.301: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:18.492: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:18.492: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:23:19.867: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:20.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:20.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:20.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:20.630: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:23:22.538: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:22.729: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:22.919: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:23.111: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:23.302: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:23.494: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:23.494: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:23:24.867: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:25.058: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:25.249: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:25.440: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:25.631: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:23:27.540: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:27.731: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:27.922: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:28.113: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:28.304: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:28.494: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:28.494: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:23:29.867: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:30.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:30.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:30.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:30.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:23:32.538: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:32.729: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:32.920: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:33.110: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:33.301: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:33.492: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:33.492: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:23:34.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:35.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:35.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:35.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:35.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:23:37.539: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:37.730: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:37.921: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:38.112: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:38.302: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:38.493: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:38.493: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:23:39.867: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:40.058: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:40.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:40.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:40.630: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:23:42.538: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:42.728: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:42.919: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:43.110: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:43.301: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:43.492: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:43.493: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:23:44.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:45.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:45.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:45.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:45.629: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:23:47.537: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:47.737: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:47.927: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:48.118: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:48.309: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:48.500: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:48.500: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:23:49.867: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:50.057: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:50.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:50.440: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:50.630: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:23:52.538: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:52.729: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:52.920: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:53.110: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:53.301: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:53.492: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:53.492: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:23:54.867: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:55.058: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:55.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:55.439: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:55.630: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:23:57.542: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:57.732: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:57.923: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:58.114: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:58.305: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:58.495: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:23:58.496: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:23:59.865: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:00.055: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:00.251: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:00.441: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:00.630: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:24:02.527: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:02.717: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:02.906: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:03.096: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:03.286: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:03.475: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:03.475: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:24:04.865: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:05.055: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:05.245: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:05.434: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:05.624: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:24:07.522: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:07.711: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:07.900: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:08.090: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:08.280: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:08.471: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:08.471: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:24:09.865: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:10.055: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:10.245: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:10.435: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:10.625: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:24:12.521: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:12.711: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:12.900: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:13.090: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:13.280: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:13.470: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:13.470: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:24:14.868: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:15.058: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:15.248: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:15.437: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:15.627: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:24:17.525: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:17.714: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:17.904: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:18.094: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:18.283: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:18.473: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:18.473: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:24:19.865: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:20.055: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:20.245: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:20.434: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:20.624: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
... skipping 9 lines ...
Jul 30 12:24:22.520: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:22.710: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:22.900: INFO: Unable to read jessie_udp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:23.089: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:23.279: INFO: Unable to read 100.66.202.45_udp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:23.469: INFO: Unable to read 100.66.202.45_tcp@PTR from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:23.469: INFO: Lookups using dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e failed for: [wheezy_udp@dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local wheezy_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR jessie_udp@dns-test-service.dns-3814.svc.cluster.local jessie_tcp@dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local jessie_udp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_tcp@_http._tcp.test-service-2.dns-3814.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord 100.66.202.45_udp@PTR 100.66.202.45_tcp@PTR]

Jul 30 12:24:24.866: INFO: Unable to read wheezy_udp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:25.055: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:25.245: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3814.svc.cluster.local from pod dns-3814/dns-test-95bb413f-a970-445f-b988-93ae8863411e: the server could not find the requested resource (get pods dns-test-95bb413f-a970-445f-b988-93ae8863411e)
Jul 30 12:24:25.435: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3814.svc.