Second attempt: Plumb context to Kubelet CRI calls (#113591)
* plumb context from CRI calls through kubelet * clean up extra timeouts * try fixing incorrectly cancelled context
This commit is contained in:
@@ -17,6 +17,7 @@ limitations under the License.
|
||||
package e2enode
|
||||
|
||||
import (
|
||||
"context"
|
||||
"time"
|
||||
|
||||
v1 "k8s.io/api/core/v1"
|
||||
@@ -77,7 +78,7 @@ var _ = SIGDescribe("ContainerLogRotation [Slow] [Serial] [Disruptive]", func()
|
||||
id := kubecontainer.ParseContainerID(pod.Status.ContainerStatuses[0].ContainerID).ID
|
||||
r, _, err := getCRIClient()
|
||||
framework.ExpectNoError(err)
|
||||
resp, err := r.ContainerStatus(id, false)
|
||||
resp, err := r.ContainerStatus(context.Background(), id, false)
|
||||
framework.ExpectNoError(err)
|
||||
logPath := resp.GetStatus().GetLogPath()
|
||||
ginkgo.By("wait for container log being rotated to max file limit")
|
||||
|
Reference in New Issue
Block a user