This job view page is being replaced by Spyglass soon. Check out the new job view.
PRdims: Bump dependencies and go version (in go.mod)
ResultABORTED
Tests 0 failed / 0 succeeded
Started2023-01-21 17:09
Elapsed17m43s
Revision0d93b6b47628bbeabdf521a9f517fa165f7a5b14
Refs 547

No Test Failures!


Error lines from build-log.txt

... skipping 401 lines ...
	go build \
	-o=/home/prow/go/src/github.com/kubernetes-sigs/aws-iam-authenticator/_output/bin/aws-iam-authenticator \
	-ldflags="-w -s -X sigs.k8s.io/aws-iam-authenticator/pkg.Version= -X sigs.k8s.io/aws-iam-authenticator/pkg.BuildDate=2023-01-21T17:15:00Z -X sigs.k8s.io/aws-iam-authenticator/pkg.CommitID=222a16befff613ad97cd76da6e14c1511746620b" \
	./cmd/aws-iam-authenticator/
make[2]: Leaving directory '/home/prow/go/src/github.com/kubernetes-sigs/aws-iam-authenticator'
make[1]: Leaving directory '/home/prow/go/src/github.com/kubernetes-sigs/aws-iam-authenticator'
Error: cluster not found "test-cluster-10535.k8s.local"
###
## Setting up roles
#

An error occurred (NoSuchEntity) when calling the GetRole operation: The role with name aws-iam-authenticator-test-role-KubernetesAdmin cannot be found.
###
## Creating aws-iam-authenticator-test-role-KubernetesAdmin role
#
admin role: arn:aws:iam::607362164682:role/aws-iam-authenticator-test-role-KubernetesAdmin

An error occurred (NoSuchEntity) when calling the GetRole operation: The role with name aws-iam-authenticator-test-role-KubernetesUsers cannot be found.
###
## Creating aws-iam-authenticator-test-role-KubernetesUsers role
#
user role: arn:aws:iam::607362164682:role/aws-iam-authenticator-test-role-KubernetesUsers
###
## Generating SSH key /home/prow/go/src/github.com/kubernetes-sigs/aws-iam-authenticator/hack/e2e/e2e-test-artifacts/id_rsa
... skipping 12 lines ...
| *.. .+ S o .    |
|+o=.o..B +       |
|++=o..+ = .      |
|oo.+.+ B o       |
|  ++++O .        |
+----[SHA256]-----+
Error: cluster not found "test-cluster-10535.k8s.local"
###
## Creating cluster test-cluster-10535.k8s.local with /home/prow/go/src/github.com/kubernetes-sigs/aws-iam-authenticator/hack/e2e/e2e-test-artifacts/test-cluster-10535.k8s.local.json (dry run)
#
I0121 17:15:09.465375   17809 new_cluster.go:248] Inferred "aws" cloud provider from zone "us-west-2a"
I0121 17:15:09.465554   17809 new_cluster.go:1102]  Cloud Provider ID = aws
I0121 17:15:09.807508   17809 subnets.go:182] Assigned CIDR 172.20.32.0/19 to subnet us-west-2a
... skipping 77 lines ...
Unable to connect to the server: dial tcp: lookup api-test-cluster-10535-k8-e0d1r1-856975279.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
Unable to connect to the server: dial tcp: lookup api-test-cluster-10535-k8-e0d1r1-856975279.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
Unable to connect to the server: dial tcp: lookup api-test-cluster-10535-k8-e0d1r1-856975279.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
Unable to connect to the server: dial tcp: lookup api-test-cluster-10535-k8-e0d1r1-856975279.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
Unable to connect to the server: dial tcp: lookup api-test-cluster-10535-k8-e0d1r1-856975279.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
Unable to connect to the server: dial tcp: lookup api-test-cluster-10535-k8-e0d1r1-856975279.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
error: Get "https://api-test-cluster-10535-k8-e0d1r1-856975279.us-west-2.elb.amazonaws.com/api?timeout=32s": dial tcp: lookup api-test-cluster-10535-k8-e0d1r1-856975279.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host - error from a previous attempt: EOF
Unable to connect to the server: EOF
Unable to connect to the server: EOF
###
## Cluster is up!
#
###
... skipping 44 lines ...
ip-172-20-79-74.us-west-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/aws-iam-authenticator-42qls	system-node-critical pod "aws-iam-authenticator-42qls" is pending

Validation Failed
W0121 17:21:33.859917   18328 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 8 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-proxy-ip-172-20-42-17.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-42-17.us-west-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-79-74.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-79-74.us-west-2.compute.internal" is pending

Validation Failed
W0121 17:21:46.149269   18328 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 43 lines ...