Files
Paul Holzinger 5004e99e3b pkg/machine/hyperv: fix incorrect timeout
The timeout is simply to low, I don't know the previous numbers were
collected because they are simply wrong. A machine init takes around 50s
total. And while the ready timeout itself could be shorter there is
really no good reason to set such a low limit as it will cause wrong
failures.

This is currently flaking a lot in CI, I see it in most hyperV logs I
looked at[1]. While there is likely another problem with the boot
failures I think this added a ton of false positives as it errors out
early.

[1] https://github.com/podman-container-tools/podman/actions/runs/34146238887/job/101820830173

Fixes: dd28c14f8c ("hyperv: add timeout to vsock ready wait")

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
2026-09-08 12:42:15 +02:00
..
2026-09-04 11:53:04 +02:00