This job view page is being replaced by Spyglass soon. Check out the new job view.
PRkevindelgado: server-side metadata unknown field validation
ResultABORTED
Tests 0 failed / 0 succeeded
Started2022-07-07 19:34
Elapsed50m38s
Revision2ad9aa22fb9f2e053d5b3221aa213479a45d7db1
Refs 109494

No Test Failures!


Error lines from build-log.txt

... skipping 718 lines ...
Looking for address 'e2e-109494-95a39-master-ip'
Looking for address 'e2e-109494-95a39-master-internal-ip'
Using master: e2e-109494-95a39-master (external IP: 34.138.175.159; 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-26_e2e-109494-95a39" set.
User "k8s-infra-e2e-boskos-scale-26_e2e-109494-95a39" set.
Context "k8s-infra-e2e-boskos-scale-26_e2e-109494-95a39" created.
Switched to context "k8s-infra-e2e-boskos-scale-26_e2e-109494-95a39".
... skipping 227 lines ...
e2e-109494-95a39-minion-group-z61t   Ready                         <none>   60s    v1.25.0-alpha.2.121+30836cce1587f5
e2e-109494-95a39-minion-group-zbsb   Ready                         <none>   61s    v1.25.0-alpha.2.121+30836cce1587f5
e2e-109494-95a39-minion-heapster     Ready                         <none>   73s    v1.25.0-alpha.2.121+30836cce1587f5
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 https://34.138.175.159
GLBCDefaultBackend is running at https://34.138.175.159/api/v1/namespaces/kube-system/services/default-http-backend:http/proxy
CoreDNS is running at https://34.138.175.159/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
Metrics-server is running at https://34.138.175.159/api/v1/namespaces/kube-system/services/https:metrics-server:/proxy
... skipping 851 lines ...