Skip to content

[Workflow Health] P0: cloud-hypervisor EACCES sandbox failure — 44 open occurrences across 40+ workflows (predecessor #61528 aut #61952

Closed as not planned

Description

@github-actions

Incident

The cloud-hypervisor sandbox EACCES regression first reported in #61528 (auto-closed by its
expires: 1d setting on 2026-09-18T04:46Z, not because it was fixed) is still active and has
grown from 30 to 44 open occurrences in the 24h since the last dashboard run.

Every affected job fails identically before the agent produces any output:

Error: Unable to execute "/run/awf-cloud-hypervisor/trusted-artifacts/run-<id>/cloud-hypervisor --version";
verify the trusted Cloud Hypervisor artifact exists, is executable, and is complete: code=EACCES

Impact

Every scheduled/triggered run of an affected workflow fails before the agent engine starts,
producing zero safe outputs and burning a full CI run. This is a cascading, ecosystem-wide P0 —
not a single-workflow defect.

Action requested

  1. Reproduce the EACCES failure locally with the pinned v0.28.20 cloud-hypervisor sandbox and
    inspect the trusted-artifact staging step (permission bits, noexec mount flags, ownership) for
    the copied cloud-hypervisor binary.
  2. Either fix the staging/permission step in the firewall/sandbox tooling, or temporarily disable
    cloud-hypervisor sandboxing for affected workflows until a fix lands, to stop the cascade.
  3. Do not close this issue via expires: 1d (or similar short auto-expiry) until the fix is
    verified by at least one clean run of a previously-affected workflow — the predecessor ([Workflow Health] P0: cloud-hypervisor "--version exited with code undefined" — 29 workflows affected across 3 engines #61528)
    auto-expired without being fixed, which caused this exact incident to look "resolved" when it
    was not.

Do not re-file

Do NOT file new per-workflow issues for this signature — all 44 open occurrences (e.g. #61627,
#61770, #61815, #61817, #61823, #61826, #61831, #61832, #61849, #61850, #61852, #61856, #61858,
#61872, #61875, #61876, #61877, #61880, #61882, #61884, #61885, #61886, #61887, #61911, #61925,
#61926, #61927, #61928, #61930, #61931, #61932, #61933, #61937, #61939, #61941, #61942, #61944)
are the same root cause and should be consolidated under this tracker.

Filed by Workflow Health Manager, run 35421585500.

Generated by 🏥 Workflow Health Manager - Meta-Orchestrator · copilot · auto · 89.5 AIC · ⌖ 7.16 AIC · ⊞ 12.3K · ◷

  • expires on Sep 19, 2026, 8:42 PM UTC-08:00

Activity

  1. github-actions commented on Sep 19, 2026

    @github-actions
    ContributorAuthor

    🍪 Issue Monster selected this for Copilot

    I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.

    If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    🍪 Om nom nom by Issue Monster · pi · gpt54 · 8.22 AIC · ⊞ 12.1K · ◷

  2. github-actions commented on Sep 20, 2026

    @github-actions
    ContributorAuthor

    Status update — 2026-09-20T04:35Z (Workflow Health Manager)

    Still unresolved, ~24h after filing. No fix PR has landed and no comment beyond the automated
    "Issue Monster selected this for Copilot" assignment note (2026-09-19T08:48Z) — no PR was produced
    by that assignment attempt.

    • Occurrence rate unchanged/still active: 33 new [aw] <workflow> failed issues carrying the
      same code=EACCES ... cloud-hypervisor --version signature were opened between
      2026-09-19T14:54Z and 2026-09-20T03:50Z (~13h window), including repeats for workflows already
      cited in this tracker (LintMonster [aw] LintMonster failed #62104, Metrics Collector [aw] Metrics Collector failed #62103, Code Simplifier [aw] Code Simplifier failed #62109,
      jsweep [aw] jsweep - JavaScript Unbloater failed #62111).
    • No new fix PR found: searched repo:github/gh-aw EACCES is:pr and cloud-hypervisor is:pr
      — no open PR references this tracker or touches the trusted-artifact staging step.
    • Recommendation stands: either fix the trusted-artifact permission/staging step for
      cloud-hypervisor (chmod/exec bit or noexec mount) or temporarily disable cloud-hypervisor
      sandboxing for affected workflows to stop the cascade. DO NOT re-file per-workflow duplicates —
      consolidate under this tracker.

    Metrics Collector itself remains affected (its own daily-firewall-report / lint-monster style runs
    fail with the same EACCES), which explains why metrics/latest.json is now stale for an 8th
    consecutive run (dated 2026-09-01, 19 days stale).

    Generated by 🏥 Workflow Health Manager - Meta-Orchestrator · copilot · auto · 70.3 AIC · ⌖ 11.3 AIC · ⊞ 12.3K · ◷

  3. github-actions commented on Sep 20, 2026

    @github-actions
    ContributorAuthor

    This issue was automatically closed because it expired on 2026-09-20T04:42:01.213Z.

    Closed by Workflow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions