[P0] aw-gpu-runner-T4: node not found — Daily News, Daily Fact, Daily Issues Report failing 100%

[github-actions]

Problem

Three workflows running on aw-gpu-runner-T4 are failing 100% of the time with node: command not found. All three use the copilot engine, which requires Node.js to be available on the runner.

Error:

/bin/bash: line 1: node: command not found

Affected Workflows

Workflow	MD File	Recent Failure Rate	Example Run
Daily Issues Report Generator	daily-issues-report.md	100% (15+ consecutive)	§24954338914
Daily News	daily-news.md	100% (8+ consecutive)	§24881782690
Daily Fact About gh-aw	daily-fact.md	100% (8+ consecutive)	§24887335913

All three workflows have runs-on: aw-gpu-runner-T4 in their frontmatter.

Root Cause

The aw-gpu-runner-T4 runner does not have Node.js installed (or it's not in PATH), but the copilot engine requires Node.js to execute the Copilot CLI. The runtimes: node: version: "24" frontmatter in these workflows does not appear to be provisioning Node.js correctly on this runner type.

History

A prior auto-issue (#27534) was created for the same error on Apr 21, 2026 and closed as "not planned". The failure has continued uninterrupted since before Apr 12.

Impact

• 3 daily reporting workflows completely non-functional
• Duplicate failure issues auto-created each day (e.g. [aw] Daily Fact About gh-aw failed #28245, [aw] Daily Issues Report Generator failed #28568)
• No daily news, issue reports, or facts being generated

Suggested Fixes

1. Install Node.js on aw-gpu-runner-T4 — ensure the runner image has Node 20+ in PATH, matching the ubuntu-latest runner setup
2. Use a different runner type — change these workflows to ubuntu-latest if GPU is not needed for the copilot engine (verify if T4 GPU is actually used)
3. Add node setup step — as a workaround, add a setup-node action step before the copilot engine step

Verification

Check if daily-news.md, daily-fact.md, or daily-issues-report.md actually require GPU acceleration. If not, removing runs-on: aw-gpu-runner-T4 and using the default runner would immediately fix all three workflows.

Note

🔒 Integrity filter blocked 1 item

The following item was blocked because it doesn't meet the GitHub integrity level.

• #19099 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Workflow Health Manager - Meta-Orchestrator · ● 2.5M · ◷

• expires on Apr 27, 2026, 12:08 PM UTC

[github-actions]

🍪 *Issue Monster selected this for Copilotecho BEGIN___COMMAND_OUTPUT_MARKER ; PS1= ; PS2= ; unset HISTFILE ; EC=0 ; echo ___BEGIN___COMMAND_DONE_MARKER___0 ; }

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! 🍪

Caution

Security scanning requires review for Issue Monster

Details

Potential security threats were detected in the agent output. The workflow output should be reviewed before merging.

Review the workflow run logs for details.

🍪 Om nom nom by Issue Monster · ● 23K · ◷

[lpcox]

🔗 AWF tracking issue: https://github.com/github/gh-aw-firewall/issues/github/gh-aw-firewall#2222

Generated by Firewall Issue Dispatcher · ● 657.8K · ◷