This job view page is being replaced by Spyglass soon. Check out the new job view.
PRchendave: kubeadm: Honor `cert-dir` for cert operations
Tests 0 failed / 65 succeeded
Started2022-06-23 10:57
Refs 110709

No Test Failures!

Show 65 Passed Tests

Error lines from build-log.txt

... skipping 673 lines ...
e2e-110709-95a39-master  us-east1-b  n1-standard-8       RUNNING
Setting e2e-110709-95a39-master's aliases to 'pods-default:;' (added
Updating network interface [nic0] of instance [e2e-110709-95a39-master]...
Updated [].
Failed to execute 'sudo /bin/bash /home/kubernetes/bin/' on e2e-110709-95a39-master despite 5 attempts
Last attempt failed with: /bin/bash: /home/kubernetes/bin/ No such file or directory
Creating firewall...
..Created [].
NAME                         NETWORK           DIRECTION  PRIORITY  ALLOW                     DENY  DISABLED
e2e-110709-95a39-minion-all  e2e-110709-95a39  INGRESS    1000      tcp,udp,icmp,esp,ah,sctp        False
Creating nodes.
... skipping 32 lines ...
Looking for address 'e2e-110709-95a39-master-ip'
Looking for address 'e2e-110709-95a39-master-internal-ip'
Using master: e2e-110709-95a39-master (external IP:; internal IP:
Waiting up to 300 seconds for cluster initialization.

  This will continually check to see if the API for kubernetes is reachable.
  This may time out if there was some uncaught error during start up.

Kubernetes cluster created.
Cluster "k8s-infra-e2e-boskos-scale-11_e2e-110709-95a39" set.
User "k8s-infra-e2e-boskos-scale-11_e2e-110709-95a39" set.
Context "k8s-infra-e2e-boskos-scale-11_e2e-110709-95a39" created.
Switched to context "k8s-infra-e2e-boskos-scale-11_e2e-110709-95a39".
... skipping 227 lines ...
e2e-110709-95a39-minion-group-zw4n   Ready                         <none>   59s    v1.25.0-alpha.1.101+847a5af70277b4
e2e-110709-95a39-minion-group-zxrc   Ready                         <none>   61s    v1.25.0-alpha.1.101+847a5af70277b4
e2e-110709-95a39-minion-heapster     Ready                         <none>   83s    v1.25.0-alpha.1.101+847a5af70277b4
Warning: v1 ComponentStatus is deprecated in v1.19+
Validate output:
Warning: v1 ComponentStatus is deprecated in v1.19+
NAME                 STATUS    MESSAGE                         ERROR
etcd-1               Healthy   {"health":"true","reason":""}   
etcd-0               Healthy   {"health":"true","reason":""}   
scheduler            Healthy   ok                              
controller-manager   Healthy   ok                              
Cluster validation encountered some problems, but cluster should be in working order
...ignoring non-fatal errors in validate-cluster
Done, listing cluster services:

Kubernetes control plane is running at
GLBCDefaultBackend is running at
CoreDNS is running at
Metrics-server is running at
... skipping 851 lines ...