deploy(#52): DelmiaReceiver child-name fix applied on DEV + QA (Z28061 excluded)

CvdReactor.ProcessRecipeDownload now addresses Children["DelmiaReceiver"] on DEV vd03
and QA vq03/vq04. Redeployed DEV Z28062 + Z28061Sim, QA Z28062-Z28069; Z28061 left
stale on both tiers (shared with another team, no slot agreed). Traced read-only call
on Z28062 (ReadyFlag False): the pre-fix 'DelmiaRecv.ReadyFlag not found' warning is
gone after the fix.

apply.sh: every CLI call passes --url/--username/--password explicitly (an env-only
SCADABRIDGE_URL silently reached DEV), plus SB_EXPECT (refuse unless the expected
instances exist = tier proof) and SB_SKIP (never deploy the listed instances).

Record: docs/deployment/deployment-records/2026-11-15-gate-52-delmiareceiver-fix.md

Claude-Session: https://claude.ai/code/session_01GT67AFKC45MBz1wPZnVbX8
This commit is contained in:
Joseph Doherty
2026-11-15 17:25:37 -05:00
parent 6489c9fc0f
commit 125db03232
2 changed files with 79 additions and 3 deletions
@@ -0,0 +1,55 @@
# 2026-11-15: #52 `CvdReactor.ProcessRecipeDownload` child-name fix, DEV vd03 + QA vq03/vq04 (Z28061 excluded)
**Owner go:** 2026-11-15, "yeah" to applying #52 (DEV first, then QA). **Z28061 is excluded on both tiers**: another team uses it and no redeploy slot has been agreed.
**Change:** one line in template `CvdReactor` (id 1), script `ProcessRecipeDownload` (id 4): `Children["DelmiaRecv"]` becomes `Children["DelmiaReceiver"]`. The body is `deploy-prep/2026-11-12-gates-52-131/fixed/CvdReactor.ProcessRecipeDownload.cs`. Every other script field is re-sent from `original/CvdReactor.ProcessRecipeDownload.meta.json` and read back unchanged.
**Scope:** management API only, through the ScadaBridge CLI (built from `main`) run from the Mac.
- No binary, no migration, no service restart, no WinRM. Only the redeployed instance actors restarted.
- Not touched: Z28061 (template change only; its deployment was left alone), every other template, script and instance, OtOpcUa, mxaccessgw, HistorianGateway and Overview.
**Tooling change (`apply.sh`, same commit):** every CLI call now passes `--url`, `--username` and `--password` explicitly. Earlier on 2026-11-15, an env-only `SCADABRIDGE_URL` pointing at QA had silently reached **DEV**, because the CLI fell back to its configured default central. Two optional guards were added:
- `SB_EXPECT=<names>` refuses to run unless the listed instances exist on the central, which proves the tier. The full instance list is printed first.
- `SB_SKIP=<names>` never deploys the listed instances. They are left stale.
## Functional check (read-only)
The call is `flow-debug run-script --instance-id 2 --script ProcessRecipeDownload --params '{}'` on **Z28062**, made only after confirming `DelmiaReceiver.ReadyFlag` is **False / Good**. In that state, the script returns before its `try` block, so nothing is written to the PLC.
- The returned text is the same before and after: `Receiver ready flag not set to true`. That is the correct answer when the real flag is False, so the text alone does not prove the fix.
- The evidence is the trace instead. **Before** the fix, the run logged `WARN runtime GetAttribute: attribute 'DelmiaRecv.ReadyFlag' not found on instance 'Z28062'`. This is the #52 defect: a null child, so the hard-coded text came back regardless of the real flag. **After** the fix, the warning is gone, and the script read the existing `DelmiaReceiver.ReadyFlag`.
- Not exercised: the download path with `ReadyFlag` True. It writes `RecipeDownloadFlag` and the recipe fields to the receiver and waits on `RecipeProcessedFlag`. Running it needs a planned recipe download.
- On QA, **Z28063 has `DelmiaReceiver.ReadyFlag` True**. A call there would take the write path, so it was **not** called. Its first real `DelmiaRecipeDownload` will now take the download path, which it did not before.
## DEV vd03 (`http://wonder-app-vd03.zmr.zimmer.com:8085`, DisableLogin)
| Step | Result |
|---|---|
| Tier proof | Instances: SBTEST01, SBTEST02, Z28061, Z28061Sim, Z28062, ZIPSEN. This is DEV's set |
| `check 52` | Live body **ORIGINAL**. Z28061, Z28061Sim and Z28062 not stale (deployed 2026-10-28) |
| Negative control | The trace logs `DelmiaRecv.ReadyFlag' not found` |
| `apply 52` (`SB_SKIP=Z28061`) | Script 4 updated; metadata read back unchanged. Deployed **Z28061Sim** (deployment 97) and **Z28062** (98). Z28061 skipped |
| `check 52` after | Body **FIXED**. Z28061Sim and Z28062 not stale (22:23:20–21Z). **Z28061 `stale=True`**, as intended |
| Trace after | RouteCall and ScriptRun Delivered, with the same ResultText and **no `not found` warning** |
## QA vq03/vq04 (active central **vq04** `:8085`, login `multi-role`)
**The active central is vq04.** `/health/active` returns vq03 503 and vq04 200. On 2026-11-13 it was vq03. Live flow-debug runs are refused on the standby (`STANDBY_NODE`), so every QA call went to vq04. Reads and writes go through the active node either way.
| Step | Result |
|---|---|
| Safety re-check (22:24Z) | The 8 instances to redeploy: `CycleRunning` False/False on both sides, FurnaceTemp 23–25 °C. All SAFE. Open batches: Z28063 L 29049, Z28065 R 29020, Z28068 L 29081 |
| Tier proof | Instances: WarmCanary, Z28061–Z28069, ZIPSEN. This is QA's set |
| `check 52` | Live body **ORIGINAL**. All 9 CvdReactor instances not stale (deployed 2026-11-06) |
| Negative control | Z28062 trace logs `DelmiaRecv.ReadyFlag' not found` |
| `apply 52` (`SB_SKIP=Z28061`) | Script 4 updated; metadata read back unchanged. Deployed **Z28062–Z28069** (deployments 233–240). Z28061 skipped |
| `check 52` after | Body **FIXED**. Z28062–Z28069 not stale (22:24:33–37Z). **Z28061 `stale=True`** |
| Trace after | Z28062: RouteCall and ScriptRun Delivered, with **no `not found` warning** |
| Post-redeploy | All 8 instances 244/244 attributes Good. `CycleRunning` False. The open batches and current steps are unchanged (Z28063 L 29049/step 2, Z28065 R 29020/step 2, Z28068 L 29081/step 6). `ReadyFlag` values unchanged |
## Follow-up
**Z28061 still runs the old script on both tiers.** It shows `stale=True` and still carries the #52 defect. Redeploy it once the other team agrees a slot. The tracking issue is in Gitea (#52 follow-up). The command is either `instance deploy --id 1` (explicit `--url`), or `apply.sh apply 52` without `SB_SKIP`, which is a no-op for the script and deploys only the stale instances.
## Rollback
Per tier: `SCADABRIDGE_URL=<central> SCADABRIDGE_USERNAME=… SCADABRIDGE_PASSWORD=… SB_SKIP=Z28061 bash apply.sh rollback 52`. It refuses unless the live body is FIXED. It writes the original body back, and the instances redeploy onto it.