generated from coulomb/repo-seed
docs(workplan): record railiance01 llm-connect smoke evidence
Note the 2026-06-19 live reconciliation on railiance01: llm-connect deployed, worker restarted with LLM_CONNECT_URL, fixture smoke passed. Manual daily triage still blocked on actcore-state-hub-bridge reachability.
This commit is contained in:
@@ -8,7 +8,7 @@ status: blocked
|
|||||||
owner: codex
|
owner: codex
|
||||||
topic_slug: custodian
|
topic_slug: custodian
|
||||||
created: "2026-06-18"
|
created: "2026-06-18"
|
||||||
updated: "2026-06-18"
|
updated: "2026-06-19"
|
||||||
state_hub_workstream_id: "f2c73ac6-13f0-4005-82cc-76c7c9f9c8b9"
|
state_hub_workstream_id: "f2c73ac6-13f0-4005-82cc-76c7c9f9c8b9"
|
||||||
---
|
---
|
||||||
|
|
||||||
@@ -107,6 +107,20 @@ Current wait reason: this is Railiance/operator-owned live cluster work. State
|
|||||||
Hub handoff message `9a074b7c-4b87-4e3c-a6bf-e1fe5580daa8` asks
|
Hub handoff message `9a074b7c-4b87-4e3c-a6bf-e1fe5580daa8` asks
|
||||||
`railiance-cluster` to reconcile the updated config and smoke it.
|
`railiance-cluster` to reconcile the updated config and smoke it.
|
||||||
|
|
||||||
|
2026-06-19 recheck:
|
||||||
|
|
||||||
|
- Deployed `llm-connect` into the `activity-core` namespace on `railiance01`
|
||||||
|
(the cluster that runs `actcore-worker`). `coulombcore` had llm-connect only;
|
||||||
|
the in-cluster Service URL is cluster-local.
|
||||||
|
- `actcore-runtime-config` already exposed the verified URL and timeout;
|
||||||
|
`deployment/actcore-worker` was restarted and now reports
|
||||||
|
`LLM_CONNECT_URL=http://llm-connect.activity-core.svc.cluster.local:8080`.
|
||||||
|
- `llm-connect-provider-secrets` reports `DATA 1`; no Secret values were
|
||||||
|
inspected.
|
||||||
|
- Worker health probe to llm-connect `/health` returns `{"status": "ok"}`.
|
||||||
|
- `actcore-state-hub-bridge` remains `0/1` Ready with upstream timeouts, so T02
|
||||||
|
is not fully closed until the node-local State Hub tunnel is restored.
|
||||||
|
|
||||||
## Run Daily Triage Fixture Smoke
|
## Run Daily Triage Fixture Smoke
|
||||||
|
|
||||||
```task
|
```task
|
||||||
@@ -128,6 +142,17 @@ Done when:
|
|||||||
detail;
|
detail;
|
||||||
- `scripts/verify_daily_triage.py` reports the smoke/manual run as present.
|
- `scripts/verify_daily_triage.py` reports the smoke/manual run as present.
|
||||||
|
|
||||||
|
2026-06-19 recheck:
|
||||||
|
|
||||||
|
- In-namespace llm-connect fixture smoke on `railiance01` passed:
|
||||||
|
`smoke: pass health=ok latency_seconds=1.681 recommendations=1`.
|
||||||
|
- Manual `POST /activity-definitions/6fca51fa-387a-4fd0-bc4e-d62c29eb859a/trigger`
|
||||||
|
reached llm-connect, but the workflow failed at `persist_instruction_reports`
|
||||||
|
with `state-hub-progress` sink `Connection refused` while
|
||||||
|
`actcore-state-hub-bridge` is unhealthy.
|
||||||
|
- T03 therefore remains open until State Hub bridge reachability is restored and
|
||||||
|
a run emits non-secret `daily_triage` progress with `output_validated=true`.
|
||||||
|
|
||||||
## Collect Three Clean Scheduled Runs
|
## Collect Three Clean Scheduled Runs
|
||||||
|
|
||||||
```task
|
```task
|
||||||
|
|||||||
Reference in New Issue
Block a user