Harshal Patil
Harshal Patil
We run these tests in upstream k8s CI (with `runc` and `crio`) - https://testgrid.k8s.io/sig-node-cri-o#ci-crio-cgroupv1-node-e2e-conformance You can click on individual `green` box to get test report and click `Raw Build-log.txt` to...
Another pointer - https://github.com/kubernetes/kubernetes/blob/master/hack/e2e-node-test.sh
But eventually it boils down to this command, `/usr/local/bin/runc --root /run/runc delete --force f6b72c56564b7cc16dfc7492cda08f1624035114212ab27b28668be0b052ea4b` So you may not actually have to deal with k8s node e2e to reproduce this. @utam0k
Thanks @Priyankasaggu11929 for reaching out. I am planning to raise a PR by coming Monday.
@Priyankasaggu11929 I just raised a PR - https://github.com/kubernetes/kubernetes/pull/111384
API Changes PR - https://github.com/kubernetes/kubernetes/pull/111642
@Priyankasaggu11929 Request for the exception has been raised - https://groups.google.com/g/kubernetes-sig-node/c/H_jmCppaurU/m/vwOzc-EFAAAJ
@rhockenbury Link to the PR - https://github.com/kubernetes/enhancements/pull/3575
@paulnivin thanks for reporting the issue. I will take a look at in upcoming week.