github/kata-containers
1
0
Fork 1
mirror of https://github.com/kata-containers/kata-containers.git synced 2025-05-05 15:07:31 +00:00
Code Issues Projects Releases Wiki Activity

tests: k8s-inotify: longer pod termination timeout

Browse Source 
inotify-configmap-pod.yaml is using: "inotifywait --timeout 120",
so wait for up to 180 seconds for the pod termination to be
reported.

Hopefully, some of the sporadic errors from  will be avoided
this way:

not ok 1 configmap update works, and preserves symlinks
waitForProcess "${wait_time}" "$sleep_time" "${command}" failed

Signed-off-by: Dan Mihai <dmihai@microsoft.com>
This commit is contained in:
Dan Mihai 2024-10-10 22:29:04 +00:00
parent ccfb7faa1b
commit ece0f9690e
1 changed files with 6 additions and 2 deletions

8
tests/integration/kubernetes/k8s-inotify.bats
View File

@ -32,10 +32,14 @@ setup() {
# Update configmap
kubectl apply -f "${pod_config_dir}"/inotify-updated-configmap.yaml
# inotify-configmap-pod.yaml is using: "inotifywait --timeout 120", so wait for
# up to 180 seconds for the pod termination to be reported.
pod_termination_wait_time=180
# Wait for the pod to complete
command="kubectl describe pod ${pod_name} | grep \"State: \+Terminated\""
info "Waiting ${wait_time} seconds for: ${command}"
waitForProcess "${wait_time}" "$sleep_time" "${command}"
info "Waiting ${pod_termination_wait_time} seconds for: ${command}"
waitForProcess "${pod_termination_wait_time}" "$sleep_time" "${command}"
# Verify we saw the update
result=$(kubectl get pod "$pod_name" --output="jsonpath={.status.containerStatuses[]}")