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

@ -215,3 +215,43 @@ Live lasuite-meet probe:
- Conclusion: this is not a stale-test case yet; `recipe-maintainers/lasuite-meet` is not enrolled in the
bridge poll set, so `!testme` never entered the real CI path. Keep V5/V6 search on already-enrolled
recipes.
## 2026-06-01 — Operator steer: enroll lasuite-meet; activation left host offline
Re-oriented from the current Phase 5 SSOT and the phase ledgers. There is no separate `plan-phase6-*`
file in `/srv/cc-ci/cc-ci-plan`; the operator steer maps to Phase 5 V5/V6.
Minimal code change:
- `nix/modules/bridge.nix`: added `recipe-maintainers/lasuite-meet` to `POLL_REPOS`
- committed + pushed as `f28a2a3 fix(bridge): enroll lasuite-meet for !testme`
Host rollout attempts:
- `ssh cc-ci "test -d /root/builder-clone && git -C /root/builder-clone pull --rebase"`
-> fast-forwarded host clone to `f28a2a3`
- `ssh cc-ci "nixos-rebuild build --flake path:/root/builder-clone#cc-ci"`
-> build completed (new system store path created)
- `ssh cc-ci "nixos-rebuild switch --flake path:/root/builder-clone#cc-ci"`
-> activation reached the known bootloader failure:
`efiSysMountPoint = '/boot' is not a mounted partition`
`Failed to install bootloader`
but did not roll the bridge task
- `ssh cc-ci "systemctl show -P ExecStart deploy-bridge.service"`
showed the old active helper path, and the running swarm task still used `cc-ci-bridge:3761c4221042`
- `ssh cc-ci "nixos-rebuild test --flake path:/root/builder-clone#cc-ci"`
was used to activate the updated config without touching the bootloader; it restarted multiple units,
including `deploy-bridge.service`, and then the SSH session dropped with:
`Timeout, server 100.95.31.88 not responding.`
Post-activation reachability probes from the orchestrator:
- `ssh cc-ci "systemctl status deploy-bridge.service --no-pager"`
-> `connect to host 100.95.31.88 port 22: Connection timed out`
- `tailscale status`
-> `100.95.31.88 cc-ci ... active; relay "nue"; offline`
- `tailscale ping -c 3 cc-ci`
-> `no reply`
- after a 2-minute warm poll: SSH still timed out
Current state:
- The repo-side enrollment fix is durable on origin/main.
- Live verification that the bridge poller now watches `recipe-maintainers/lasuite-meet` is blocked on
host reachability returning.