R-50 island-bridge: SPIKED -> GO (probes P1-P8 pass live on t740 drill)
Provisioned nested-PVE drill 'drill-r50' (qm300 on demo-hp) via the v1.25.0 nested-vm ISO through the real day-0, then ran the R-50 empirical spike: - vmbr9 portless island bridge + guest island NIC hot-add (LAN undisturbed) - F1 replay money shot: LAN move survives on the island; LAN-literal bind reproduces the 2026-07-20 daemon-exit bug verbatim - dnsmasq trap confirmed live + lan_resolver.host_ip fix proven - pin address-independent (leaf SHA-256 unchanged, HTTP 200 over island) - survival matrix: agent/guest/host-cold-reboot all return on the island Docs: SPIKE verdict BLOCKED->GO, ROADMAP R-50 SPIKED->GO, nodes.md drill VM, REPORT overwrite.
This commit is contained in:
@@ -1,54 +1,55 @@
|
||||
# REPORT — R-50 island-bridge SPIKE, empirical attempt 2 (t740): STILL BLOCKED (2026-07-25)
|
||||
# REPORT — R-50 island-bridge drill + empirical spike (RUNBOOK, 2026-07-25 PM)
|
||||
|
||||
**Overwritten** per the standing rule. This session re-attempted the empirical half of
|
||||
`SPIKE-island-bridge-2026-07-25.md` on the t740 (per the operator's 2026-07-25 drill-host ruling).
|
||||
Docs-only; no code, no version bumps.
|
||||
## What ran
|
||||
Provisioned the first **nested-PVE drill appliance on the t740 (`demo-hp`)** and ran the **R-50
|
||||
island-bridge empirical spike** end-to-end. Verdict: **GO.**
|
||||
|
||||
## t740 access method
|
||||
Discovery was read-only (no LAN scan): the SSH config's `demo-hp` entry (t740 = Tailscale
|
||||
`100.76.96.79` / LAN `192.168.0.87`, host_id `demo-hp-bb76ea`) + the hub registry. The t740 has **no
|
||||
baked SSH key**, so access used the **hub-vaulted G1 break-glass root credential** —
|
||||
`host_recovery/demo-hp-bb76ea` (read from the hub SQLite via `kubectl cp` + `sqlite3`), `sshpass -e`
|
||||
(secret redacted, never printed). Connected: `felhom-host`, PVE 9.2.2.
|
||||
## Part A — drill provisioned through the REAL day-0
|
||||
- **VM 300 `drill-r50`** on `demo-hp`: 8 GiB / 4 vCPU (cpu=host) / 32 GiB local-lvm / OVMF (SB off) / one
|
||||
NIC on `vmbr0` DHCP. Nested-virt already enabled on the host (A2 no-op; no QEMU VM was running at A1).
|
||||
- Installed from **`felhom-pve-9.2-1-v1.25.0-nested-vm-generic-mkimage.iso`** (current release; the
|
||||
RUNBOOK's stated *v1.22.0* was both stale **and** the wrong profile — v1.22.0-nested-**canary** is a
|
||||
deliberate match-nothing installer that aborts touching no disk; corrected to the v1.25.0 **nested-vm**
|
||||
profile. Friction finding, not a day-0 defect).
|
||||
- Day-0 drove itself: install → first-boot → **self-register** (appliance #9, pairing `9MB-4QX`) →
|
||||
**operator bind** to a scratch customer `drill-r50` (minimal config, no DNS/offsite/PBS side-effects) →
|
||||
**deliver** → nested guest **9201** provisioned, controller stack healthy (agent 0.93.0, golden 0.161.0).
|
||||
- **R-50 starting condition reached & confirmed:** agent `listen_addr = 192.168.0.176:8443` **and** guest
|
||||
`bootstrap.json local_api.endpoint = 192.168.0.176:8443` — the F1 LAN literal baked in both places.
|
||||
- Snapshot **`r50pre`** taken (clean day-0). Break-glass vaulted `host_recovery/drill-r50-0a4f9a`.
|
||||
- **Day-0 tail not driven:** *claim* is customer-email-gated (scratch customer has no inbox; forcing it
|
||||
needs a real email + a production Resend send) — left PENDING; *escrow* is N/A (no DR/PBS tier on the
|
||||
minimal drill). Neither gates the control-plane probes. **Operator decision if the full customer-side
|
||||
tail should be exercised (needs an email address + DR-tier choice).**
|
||||
|
||||
## P1 inventory — the finding: there is NO drill VM to probe
|
||||
- **t740 (`demo-hp`):** `qm list` → **empty**; `/etc/pve/qemu-server/` → **empty**; standalone (no
|
||||
cluster); only its own LXC guest 9201 + the guest-9201 LVM volumes. **No nested drill PVE VM.**
|
||||
- **Hub registry:** only `demo-hp-bb76ea` (t740) + `demo-felhom-8363b5` (N100) — **no drill appliance**
|
||||
(no `2f4b00`/`demo-vm`/`drill` host).
|
||||
- **felhom-pve:** `qm list` empty (confirmed in attempt 1).
|
||||
- **DooPlex:** the historical drill appliance `drill.qcow2` exists (`/mnt/5_hdd/felhom.eu/drill/`, 18G)
|
||||
but is **powered off** — a **golden-bake** VM (bake logs to 0.153.0, last Jul 18–20) whose nested
|
||||
guest is purged after each bake, so it has **no island-bridge topology** (agent + nested guest +
|
||||
bootstrap) to probe. DooPlex is the production k3s node and is loaded (~17G of 62G free).
|
||||
## Part B — probes P1–P8, ALL PASS (verdict GO)
|
||||
- **P2** `vmbr9` portless island bridge `169.254.253.1/30` — vmbr0 untouched, LAN gw reachable.
|
||||
- **P3** guest island NIC `eth1 169.254.253.2/30` hot-added — eth0/LAN undisturbed, bidirectional island ping.
|
||||
- **P4 (dnsmasq trap + fix)** — with `host_ip` unset, moving `listen_addr` to the island rebound dnsmasq
|
||||
to `169.254.253.1:53` and **killed LAN DNS**; `lan_resolver.host_ip=192.168.0.176` restored it while the
|
||||
API bind stayed on the island. Finding 1 confirmed + fixed, live.
|
||||
- **P5 (pin)** — served leaf SHA-256 over the island **identical** (`4ef1d953…`), authenticated
|
||||
`GET /storage` from the guest over the island → **HTTP 200**. No cert re-issue (Finding 6 live).
|
||||
- **P6 (F1 replay — money shot)** — LAN `192.168.0.176→.200`, `listen_addr` on the island → agent stays
|
||||
active + serves (200). LAN-literal contrast reproduced the 2026-07-20 bug verbatim
|
||||
(`localapi: bind 192.168.0.176:8443` → daemon exit 1).
|
||||
- **P7 (survival)** — agent restart / guest reboot / **host cold reboot** all return the control plane on
|
||||
the island with zero intervention (vmbr9, island bind, dnsmasq on LAN IP, guest autostart, controller).
|
||||
- **Method caveat:** probes drove the runtime chain via manual config edits; the *provisioning* path
|
||||
(host-install + golden-bake bootstrap template) is the implementation task — now fully de-risked.
|
||||
|
||||
**Snapshot: N/A** (no drill VM existed to snapshot).
|
||||
## Docs updated
|
||||
- `documentation/audits/SPIKE-island-bridge-2026-07-25.md` — verdict flipped BLOCKED → **GO**, empirical
|
||||
P1–P8 results added, old BLOCKED/NOT-RUN sections marked superseded.
|
||||
- `documentation/backlog/ROADMAP.md` — R-50 → **SPIKED → GO**; next = Phase A/B/C production spec.
|
||||
- `documentation/operations/nodes.md` — the drill VM 300 now documented on the t740 (access, snapshot,
|
||||
teardown).
|
||||
|
||||
## Per-probe outcomes
|
||||
P2–P7 (bridge create / NIC hot-add / island bind / pin / **F1 replay** / survival) — **NOT RUN.** The
|
||||
operator's ruling ("drill+build VMs on the HP from now on") is **forward-looking and not yet realized**:
|
||||
no probeable drill appliance exists on the t740, and the only artifact is a stale bake VM on the
|
||||
production node. **Per the hard rule ("do not improvise on production"), felhom-pve, the t740 host
|
||||
networking, and guest 9201 were left UNTOUCHED.** No config was changed anywhere → **the rollback table
|
||||
is empty**, and there is no island end-state to leave in place.
|
||||
## State left behind
|
||||
Drill VM 300 left **running in the working island configuration** (snapshot `r50pre` preserves clean
|
||||
day-0). Scratch hub records `drill-r50` (customer + appliance #9) remain — throwaway; teardown noted in
|
||||
nodes.md. `demo-hp` host networking, guest 9201, and felhom-pve were **untouched**.
|
||||
|
||||
## GO/NO-GO: PENDING (unchanged) — the design half still stands
|
||||
The source-grounded half of the parent doc (address plan `169.254.253.1/30`↔`.2/30`; the F1 two-place
|
||||
literal; the **dnsmasq trap** — `LANResolverConfig.WithDefaults` derives the DNS listen-addr from
|
||||
`listen_addr`, so the spec MUST set `lan_resolver.host_ip = LAN IP`; leaf-DER pin → no cert re-issue
|
||||
expected; provisioning inventory; cluster parity) is unchanged and ready. Only the **empirical**
|
||||
validation remains blocked.
|
||||
|
||||
## Operator decision + docs
|
||||
**Operator chose (2026-07-25): they will provision a nested-PVE drill VM on the t740 (agent + a nested
|
||||
guest); this spike re-runs then.** Commits (docs-only): the spike doc amended (attempt-2 section +
|
||||
verdict), ROADMAP R-50 note appended, `documentation/operations/nodes.md` gains a "designated drill+build
|
||||
VM host" subsection (t740 ruling + the not-yet-realized state + break-glass recipe), and the
|
||||
controller/agent `CLAUDE.md` env tables gain a `demo-hp` row/note. **The build-PIPELINE relocation to the
|
||||
t740 is explicitly NOT ruled or implemented — only the VM-hosting ruling is recorded.**
|
||||
|
||||
## Observations
|
||||
- The t740 is a genuinely better drill host than DooPlex (dedicated demo node, ~30G RAM / ~49G free
|
||||
local-lvm, not the production k3s node) — the ruling is sound; it just needs the VM created.
|
||||
- The t740's agent is **0.93.0**, behind demo-felhom's 0.95.0 — a publish-when-convenient gap (noted in
|
||||
nodes.md), unrelated to this spike.
|
||||
## Not done here (by design / veto)
|
||||
- **Part C** (deploy agent 0.95.0 → demo-hp) — veto-able; pending after this evidence.
|
||||
- **Forensic** (qm300 disappearance on felhom-pve) — optional, read-only; pending.
|
||||
|
||||
Reference in New Issue
Block a user