mirror of
https://github.com/kata-containers/kata-containers.git
synced 2025-10-22 12:29:49 +00:00
24c163e6e1
Currently, the checking for kata-deploy is running assume that the daemonset scheduled at least one pod, however it might not had and the kubectl wait command fails due to "error: no matching resources found". On CI I've observed that fail intermittently. I suspect the service account kata-deploy-sa take a while to show up then no kata-deploy is scheduled in meanwhile. Changed the checker logic to use waitForProcess() to keep testing if it is already running, or hit the timeout (still 10m). Fixes #9183 Signed-off-by: Wainer dos Santos Moschetta <wainersm@redhat.com>