Surface Cloud Hypervisor guest network init failures#53969
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
PR Triage
Draft PR surfacing Cloud Hypervisor guest network init failures at the sandbox boundary. Still WIP; defer until out of draft.
|
PR TriageCategory: bug · Risk: medium · Score: 43/100 (impact 20 + urgency 15 + quality 8) Draft infra-visibility fix (surfaces failures, does not fix root cause); moderate value, not urgent. Automated triage — see run report for full details.
|
PR Triage
Draft PR surfacing Cloud Hypervisor guest network init failures via a pre-flight check. Lower urgency until undrafted. Automated triage by PR Triage Agent.
|
PR TriageCategory: bug | Risk: medium | Priority: low (score 37/100)
|
PR TriageCategory: Draft, no CI results recorded yet. Automated triage — see the triage report issue for full context.
|
Cloud Hypervisor sandbox runs could spend the full engine timeout when guest networking never initialized, then report misleading engine-specific failures. The root failure is now detected and labeled at the sandbox boundary.
Cloud Hypervisor preflight retry
teelog pipelines.Explicit failure signal
SANDBOX_NETWORK_INIT_FAILEDActions annotation when the guest connectivity probe fails after retry.agent-stdio.log.