---
# System prepended metadata

title: testgrid-daily-monitoring-notes
tags: [CI Monitoring]

---

### 17 August
The three tests continues to fail with the following error messgaes.

- https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api#capi-e2e-dualstack-and-ipv6-main
- https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api#capi-e2e-main
- https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api#capi-e2e-mink8s-main


considering Adil's message about the CA error, I'll skip those log lines but even after that there are several time outs issues and other related items
```bash
Trace[229352142]: ---"Objects listed" error:Get "https://172.18.0.4:6443/api/v1/pods?resourceVersion=3506": net/http: TLS handshake timeout 10001ms (19:13:46.260)

Trace[328576559]: ---"Objects listed" error:Get "https://172.18.0.5:6443/api/v1/pods?resourceVersion=1045": dial tcp 172.18.0.5:6443: i/o timeout 30001ms (19:35:34.697)

INFO: Error getting pod capi-kubeadm-control-plane-system/capi-kubeadm-control-plane-controller-manager-6f85bb4c9c-2f77d, container manager: Get "https://172.18.0.6:6443/api/v1/namespaces/capi-kubeadm-control-plane-system/pods/capi-kubeadm-control-plane-controller-manager-6f85bb4c9c-2f77d": stream error: stream ID 2603; INTERNAL_ERROR; received from peer
```

- I think the first log message is again about crypto and CA issues.
- We need to debug the other two messages on the e2e-test-main considering Killian is right about CA errors not failing usually.