mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-07-20 18:31:15 +00:00
node: e2e: device plugins: Add more logs for clarity
The device plugin test in https://testgrid.k8s.io/sig-node-release-blocking#node-kubelet-serial-containerd has been flaky for a while now when it runs on the test infrastructure. Locally running this test resulted in test passing without issues. Based on the existing logs, it is not clear why podresource API endpoint is returning 3 pods rather than the expected two pods (device plugin pod and the test pod requesting devices). For more clarity and debugaability on why an addtional pod seems to be appearing we expose the output from podresource API endpoint. Signed-off-by: Swati Sehgal <swsehgal@redhat.com>
This commit is contained in:
parent
6c6865af28
commit
ef54dbb5cc
@ -181,6 +181,11 @@ func testDevicePlugin(f *framework.Framework, pluginSockDir string) {
|
||||
v1PodResources, err := getV1NodeDevices()
|
||||
framework.ExpectNoError(err)
|
||||
|
||||
framework.Logf("v1alphaPodResources.PodResources:%+v\n", v1alphaPodResources.PodResources)
|
||||
framework.Logf("v1PodResources.PodResources:%+v\n", v1PodResources.PodResources)
|
||||
framework.Logf("len(v1alphaPodResources.PodResources):%+v", len(v1alphaPodResources.PodResources))
|
||||
framework.Logf("len(v1PodResources.PodResources):%+v", len(v1PodResources.PodResources))
|
||||
|
||||
framework.ExpectEqual(len(v1alphaPodResources.PodResources), 2)
|
||||
framework.ExpectEqual(len(v1PodResources.PodResources), 2)
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user