This job view page is being replaced by Spyglass soon. Check out the new job view.
PRnitishchauhan0022: Fixing Node Allocatable dead link
ResultABORTED
Tests 0 failed / 0 succeeded
Started2022-11-24 10:56
Elapsed42m43s
Revisionb198bf2a279c110d0ba49d619be7117d46a1a5e3
Refs 114020

No Test Failures!


Error lines from build-log.txt

... skipping 690 lines ...
Looking for address 'e2e-114020-95a39-master-ip'
Looking for address 'e2e-114020-95a39-master-internal-ip'
Using master: e2e-114020-95a39-master (external IP: 34.138.156.143; internal IP: 10.40.0.2)
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-01_e2e-114020-95a39" set.
User "k8s-infra-e2e-boskos-scale-01_e2e-114020-95a39" set.
Context "k8s-infra-e2e-boskos-scale-01_e2e-114020-95a39" created.
Switched to context "k8s-infra-e2e-boskos-scale-01_e2e-114020-95a39".
... skipping 238 lines ...
e2e-114020-95a39-minion-group-zh6z   Ready                         <none>   51s    v1.27.0-alpha.0.49+3ee8ee9e121da0
e2e-114020-95a39-minion-group-zm63   Ready                         <none>   51s    v1.27.0-alpha.0.49+3ee8ee9e121da0
e2e-114020-95a39-minion-heapster     Ready                         <none>   69s    v1.27.0-alpha.0.49+3ee8ee9e121da0
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":""}   
controller-manager   Healthy   ok                              
scheduler            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 https://34.138.156.143
GLBCDefaultBackend is running at https://34.138.156.143/api/v1/namespaces/kube-system/services/default-http-backend:http/proxy
CoreDNS is running at https://34.138.156.143/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
Metrics-server is running at https://34.138.156.143/api/v1/namespaces/kube-system/services/https:metrics-server:/proxy
... skipping 365 lines ...