I wonder if this is a bug in our cri? Do you know if that's the case? Tried to capture the elapsed time before and after container was stopped with a timeout but even without this fix, I see that containerStopWithTimeout() in test/cri-containerd waits for the entire timeout period even if the container exits before the specified timeout has elapsed. Stopcontainer_test.go:68: error getting container container stats after stop: rpc error: code = Unknown desc = unexpected metrics response: = RUN Test_Gracefultermination_WCOW_Hypervisor_ServercoreĮrror getting container container stats after stop: rpc error: code = Unknown desc = unexpected metrics response: This function currently kills the container after the timeout has passed and trying to get status after that results in the following error : I am using the StopContainerWithTimeout() function to stop the container with timeout in the cri test. Tried to capture the time elapsed since the container exited using container stats but this is not supported for a container that has already existed.Ĭould you clarify what the problem with this is? I would think getting stats on an exited container (so long as it's not cleaned up) would be supported.
0 kommentar(er)
