This job view page is being replaced by Spyglass soon. Check out the new job view.
PRfengzixu: add volume kubelet_volume_stats_health_abnormal to kubelet
ResultABORTED
Tests 0 failed / 0 succeeded
Started2021-11-25 16:25
Elapsed42m49s
Revision218d4978c108050f0455c118875942bd470bc9b6
Refs 105585

No Test Failures!


Error lines from build-log.txt

... skipping 714 lines ...
Looking for address 'e2e-105585-95a39-master-ip'
Looking for address 'e2e-105585-95a39-master-internal-ip'
Using master: e2e-105585-95a39-master (external IP: 34.138.57.238; 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-21_e2e-105585-95a39" set.
User "k8s-infra-e2e-boskos-scale-21_e2e-105585-95a39" set.
Context "k8s-infra-e2e-boskos-scale-21_e2e-105585-95a39" created.
Switched to context "k8s-infra-e2e-boskos-scale-21_e2e-105585-95a39".
... skipping 227 lines ...
e2e-105585-95a39-minion-group-zg6c   Ready                         <none>   61s    v1.24.0-alpha.0.18+17734caf9b90fd
e2e-105585-95a39-minion-group-zhtf   Ready                         <none>   62s    v1.24.0-alpha.0.18+17734caf9b90fd
e2e-105585-95a39-minion-heapster     Ready                         <none>   89s    v1.24.0-alpha.0.18+17734caf9b90fd
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.57.238
GLBCDefaultBackend is running at https://34.138.57.238/api/v1/namespaces/kube-system/services/default-http-backend:http/proxy
CoreDNS is running at https://34.138.57.238/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
Metrics-server is running at https://34.138.57.238/api/v1/namespaces/kube-system/services/https:metrics-server:/proxy
... skipping 333 lines ...
I1125 16:50:13.101092   88012 framework.go:274] Applying /home/prow/go/src/k8s.io/perf-tests/clusterloader2/pkg/prometheus/manifests/default/prometheus-serviceMonitorLegacyKubeDNS.yaml
I1125 16:50:13.137392   88012 prometheus.go:296] Exposing kube-apiserver metrics in the cluster
I1125 16:50:13.273322   88012 framework.go:274] Applying /home/prow/go/src/k8s.io/perf-tests/clusterloader2/pkg/prometheus/manifests/master-ip/master-endpoints.yaml
I1125 16:50:13.308980   88012 framework.go:274] Applying /home/prow/go/src/k8s.io/perf-tests/clusterloader2/pkg/prometheus/manifests/master-ip/master-service.yaml
I1125 16:50:13.345351   88012 framework.go:274] Applying /home/prow/go/src/k8s.io/perf-tests/clusterloader2/pkg/prometheus/manifests/master-ip/master-serviceMonitor.yaml
I1125 16:50:13.382877   88012 prometheus.go:375] Waiting for Prometheus stack to become healthy...
W1125 16:50:43.419066   88012 util.go:72] error while calling prometheus api: the server is currently unable to handle the request (get services http:prometheus-k8s:9090), response: "k8s\x00\n\f\n\x02v1\x12\x06Status\x12]\n\x06\n\x00\x12\x00\x1a\x00\x12\aFailure\x1a3no endpoints available for service \"prometheus-k8s\"\"\x12ServiceUnavailable0\xf7\x03\x1a\x00\"\x00"
I1125 16:51:13.526014   88012 util.go:101] 85/112 targets are ready, example not ready target: {map[endpoint:http-metrics instance:10.40.0.49:10249 job:kube-proxy namespace:kube-system pod:kube-proxy-e2e-105585-95a39-minion-group-hw09 service:kube-proxy] unknown}
I1125 16:51:43.468037   88012 util.go:104] All 112 expected targets are ready
I1125 16:51:43.544039   88012 util.go:104] All 1 expected targets are ready
I1125 16:51:43.544090   88012 prometheus.go:240] Prometheus stack set up successfully
I1125 16:51:43.544251   88012 exec_service.go:62] Exec service: setting up service!
I1125 16:51:43.648695   88012 framework.go:274] Applying pkg/execservice/manifest/exec_deployment.yaml
... skipping 41 lines ...
I1125 16:52:40.785999   88012 util.go:101] 1/3 targets are ready, example not ready target: {map[container:dns endpoint:metrics instance:10.64.62.3:8080 job:dns namespace:probes pod:dns-7c5f768667-k82mt service:dns] unknown}
I1125 16:52:40.950699   88012 util.go:104] All 6 expected targets are ready
I1125 16:52:55.787790   88012 util.go:104] All 3 expected targets are ready
I1125 16:52:55.787852   88012 prometheus_measurement.go:75] SLOMeasurement has started
I1125 16:52:55.787868   88012 simple_test_executor.go:173] Step "[step: 01] starting measurements" ended
I1125 16:52:55.787888   88012 simple_test_executor.go:145] Step "[step: 02] Creating k8s services" started
E1125 16:52:56.087688   88012 etcd_metrics.go:147] EtcdMetrics: failed to collect etcd database size
I1125 16:53:01.573418   88012 simple_test_executor.go:173] Step "[step: 02] Creating k8s services" ended
I1125 16:53:01.573456   88012 simple_test_executor.go:145] Step "[step: 03] Creating PriorityClass for DaemonSets" started
I1125 16:53:01.609054   88012 simple_test_executor.go:173] Step "[step: 03] Creating PriorityClass for DaemonSets" ended
I1125 16:53:01.609091   88012 simple_test_executor.go:145] Step "[step: 04] create objects configmaps and secrets" started
I1125 16:53:06.104749   88012 simple_test_executor.go:173] Step "[step: 04] create objects configmaps and secrets" ended
I1125 16:53:06.104778   88012 simple_test_executor.go:145] Step "[step: 05] Starting measurement for 'create objects'" started
I1125 16:53:06.104834   88012 wait_for_controlled_pods.go:175] WaitForControlledPodsRunning: starting wait for controlled pods measurement...
I1125 16:53:06.104930   88012 wait_for_controlled_pods.go:175] WaitForControlledPodsRunning: starting wait for controlled pods measurement...
I1125 16:53:06.104982   88012 wait_for_controlled_pods.go:175] WaitForControlledPodsRunning: starting wait for controlled pods measurement...
I1125 16:53:06.105024   88012 wait_for_controlled_pods.go:175] WaitForControlledPodsRunning: starting wait for controlled pods measurement...
I1125 16:53:06.205706   88012 simple_test_executor.go:173] Step "[step: 05] Starting measurement for 'create objects'" ended
I1125 16:53:06.205745   88012 simple_test_executor.go:145] Step "[step: 06] create objects" started
{"component":"entrypoint","file":"prow/entrypoint/run.go:169","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Entrypoint received interrupt: terminated","severity":"error","time":"2021-11-25T16:53:10Z"}
++ early_exit_handler
++ '[' -n 173 ']'
++ kill -TERM 173
++ cleanup_dind
++ [[ true == \t\r\u\e ]]
++ echo 'Cleaning up after docker'
... skipping 4 lines ...