MC-4838 — Fix /api/health false Mission Control API not responding status

Home Board MC-4838

Fix /api/health false Mission Control API not responding status

During the visibility-only board-manager deploy smoke on 2026-06-08, live requests to http://127.0.0.1:3001/api/v1/tickets?limit=1, /, and /board returned 200, but /api/health s...

State Done Next Action Closed Owner Luci Runtime Closed Age 5d ago

Description

MC-4838

During the visibility-only board-manager deploy smoke on 2026-06-08, live requests to http://127.0.0.1:3001/api/v1/tickets?limit=1, /, and /board returned 200, but /api/health still reported health/status=critical, mc_ok=false, details=["Mission Control API not responding"]. Investigate and fix the health self-check so it uses the canonical MC API URL/path and does not report a false outage when the API is responding. Acceptance: reproduce the false health detail, identify root cause, add/adjust a narrow regression, land/push the fix, restart/smoke luci-dashboard.service, and verify /api/health no longer reports that false detail when /api/v1/tickets?limit=1 is healthy. Preserve visibility-only boundaries; do not call MC runtime/pickup endpoints.

Activity

done

Luci is working...

Details — Done · Medium · Luci ▼

State

Done

Closed

State

Priority

People

Owner (assigned to)

Controller

Timing / Details

Due Date

Snooze

Source luci-board-manager (luci)

Project mission-control

Created 5d ago

Updated 5d ago

Advanced / Operator evidence

Routing owner

Routes via

Operator console

Evidence

Ticket is done; runtime is closed. MC is visibility-only. Hermes Luci launches and gates work outside MC, then mirrors evidence/status here.

Workflow

Start Dev Review + QA ▾

Select phases to include:

Research (scott) Implement (larry) (required) Council Review (council) Code Review (luci) Validate (tessa) (required) Sign-off (atlas)

Agents

Review Gates

Decision

WAT routing: choose an agent, review gate, or decision. Buttons use the live runtime when one is attached.

luci-board-manager 5d ago

[visibility-only controller] Created from deploy-smoke evidence: direct live API/page smokes returned 200, but `/api/health` reports `Mission Control API not responding`. Routing through internal Kanban; no MC runtime/pickup endpoints will be used.

luci-board-manager 5d ago

[visibility-only controller] Routed to internal Kanban card t_6326607c (codexbuilder) in isolated worktree . MC remains waiting on ; no MC runtime/pickup endpoints were used.

luci-board-manager 5d ago

[visibility-only controller correction] Routing detail for prior comment: internal Kanban card `t_6326607c` is running under `codexbuilder` in isolated worktree `/home/lucienne/workspace/state/kanban-worktrees/mc-4838-health-selfcheck`; MC-4838 is waiting on `kanban_active:t_6326607c`. Verified worker PID 2229576 cwd matches the isolated worktree. No MC runtime/pickup endpoints were used.

luci-board-manager 5d ago

[visibility-only controller] Closed MC-4838 as no-op/superseded: after the MC-4831 landing and `luci-dashboard.service` restart, `/api/health` now reports `health=healthy`, `mc_ok=true`, and `details=[]`; `/api/v1/tickets?limit=1`, `/`, and `/board` also smoke successfully. I reclaimed/completed internal Kanban card `t_6326607c` so no worker keeps chasing the resolved false critical. No MC runtime/pickup endpoints were used.