status(5): record lasuite-meet enrollment rollout block
Some checks failed
continuous-integration/drone Build is failing

This commit is contained in:
autonomic-bot
2026-06-01 13:00:34 +00:00
parent f28a2a37ff
commit a147e0772d
2 changed files with 58 additions and 4 deletions

View File

@ -6,9 +6,10 @@
## Current focus
V5 next: find a genuinely stale test on an already-enrolled sandbox recipe. `n8n` and `cryptpad`
natural upgrade candidates both went GREEN; `lasuite-meet` has a live upgrade but is not currently in
the bridge poll set, so its `!testme` PR never triggered.
Minimal enrollment fix for `lasuite-meet` is committed (`f28a2a3`). Current work is verifying the live
bridge rollout so Phase-5 V5/V6 can continue on `lasuite-meet` PR #2. Verification is currently paused
on host reachability: after `nixos-rebuild test --flake path:/root/builder-clone#cc-ci`, `cc-ci`
stopped answering Tailscale SSH.
## Fixes applied (A5-1, A5-2, related)
@ -101,6 +102,13 @@ preferred, `/root/cc-ci` fallback) instead of hard-coding `/root/cc-ci`.
`https://git.autonomic.zone/recipe-maintainers/lasuite-meet/pulls/2` stayed `VERDICT=PENDING BUILD=?`
across repeated `POST=0` polls because `recipe-maintainers/lasuite-meet` is not in the bridge's
enrolled poll list. That makes it unusable for V5/V6 until explicitly enrolled.
- Enrollment fix authored and pushed: `f28a2a3 fix(bridge): enroll lasuite-meet for !testme` adds
`recipe-maintainers/lasuite-meet` to `nix/modules/bridge.nix` `POLL_REPOS`.
## Verification next step
- When `ssh cc-ci` returns, verify the live bridge poller logs include `recipe-maintainers/lasuite-meet`,
then re-run `POST=1/POST=0 /srv/cc-ci/.claude/skills/recipe-upgrade/testme-on-pr.sh lasuite-meet 2`.
## Phase 5 gates
@ -108,4 +116,10 @@ preferred, `/root/cc-ci` fallback) instead of hard-coding `/root/cc-ci`.
## Blocked
(none)
- `cc-ci` host is currently unreachable over Tailscale after `nixos-rebuild test --flake
path:/root/builder-clone#cc-ci` (used to activate the `lasuite-meet` bridge enrollment without touching
the bootloader). Current probes from the orchestrator:
- `ssh cc-ci ...` -> `connect to host 100.95.31.88 port 22: Connection timed out`
- `tailscale status` shows `100.95.31.88 cc-ci ... active; relay "nue"; offline`
- `tailscale ping -c 3 cc-ci` -> `no reply`
The code change is pushed; live verification is blocked until host reachability returns.