Open jsturtevant opened 1 month ago
We have setup crash dump reporting but it appears the service didn't generate dumps this time
https://github.com/kubernetes-sigs/windows-testing/pull/438 should enable (or re-enable) crash dump collection for most of our Windows CI jobs in K8s. I really thought this was already enabled...
We are seeing errors in the upstream Kubernetes tests that have this error in containerd. I've posted some more details in https://github.com/kubernetes/kubernetes/issues/125195#issuecomment-2145586842
We are also seeing this error in the logs:
`` [1429] {"Timestamp":"2024-05-29T00:52:27.9870075+00:00","ProviderName":"ContainerD","Level":4,"Keywords":0,"Payload":{"ID":1,"EventName":"LogrusEntry","TraceEventProcessID":5084,"TraceEventProcessName":"","Message":"Container to stop \"b6eacb5bab6ce42f8f0d173a9b0fae2175623c982adbf2cd8f3b9f89825e8215\" must be in running or unknown state, current state \"CONTAINER_EXITED\"","Time":"2024-05-29T00:52:28.0224034+00:00"}}
5/29/2024 12:21:00 AM 7031 Error The Host Network Service service terminated
unexpectedly. It has done this 1 time(s). The
following corrective action will be taken in 120000
milliseconds: Restart the service.