New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI: Conformance Ginkgo: Provision LVH VMs #32400
Comments
Looking at the timestamps provided by GitHub, it's just the |
No sysdump unfortunately, it's failing too early. Hit another one here: https://github.com/cilium/cilium/actions/runs/8991412734/workflow |
Hit a similar one in Conformance E2E |
The LVH GitHub Action already outputs the content of error code Taking a closer look at the console output of the reported workflow runs it looks like the issue is a parallel write / interleaved output to the console file exactly on the logline that we're trying to grep to verify a successful start of the SSH server. ( https://github.com/cilium/cilium/actions/runs/8978306359/job/24662060373
https://github.com/cilium/cilium/actions/runs/9011258778/job/24758598656
https://github.com/cilium/cilium/actions/runs/8991412734/attempts/1
lvh flag But i can try to optimize the regex to include line breaks - with the hope that the output not breaks in between words as well 😕 edit: or we could simply skip the "ssh availability log check" and only rely on the retries of the SSH connect (and increase the number of connection attempts) |
reopening until LVH release (with potential fix in it) lands in cilium/cilium edit: related dependency update PR: #32566 |
CI failure
I've seen this failure a couple times in the past day. It looks like the LVH VM took longer than usual to provision and breached the timeout. It's not immediately clear what is taking too long from scanning through the logs.
Full output in this gist: https://gist.github.com/thorn3r/d9d138759c8bbc639e8da138803af243
Workflow run: https://github.com/cilium/cilium/actions/runs/8978306359/job/24662060373
PR: #32353
The text was updated successfully, but these errors were encountered: