Files
felhom.eu/documentation/audits/evidence-chaos-night-2026-09-17/postinstall_fix.sh
T
admin 9fae6dfa98
gates / gates (push) Successful in 23s
CHAOS NIGHT phase 0: golden 0.245.0, a self-installing box, and R-546
The schedule was drawn from seed 20260917 and written into the findings document
BEFORE round 1, with its re-draw log.

Phase 0 measured:
- golden 0.245.0 baked, published (registry 200, not an exit code) and vouched;
  the box installed itself from the published ISO 1.28.0 and landed on it with
  no hand upgrade (controller 0.245.0, agent 0.131.0).
- ZERO operator presses: the waiting self-bind mail worked, and the acknowledged
  -delete path re-issued off-site AND PBS-DR credentials by itself
  (pbsdr_auto_reissue) - the F-14 half nobody had watched happen live.
- R-546 filed (P2): tonight's own guide sends the household to create the
  recovery code ~17 minutes before the box can do it. It self-heals; the bar
  urges them there the whole time. Measured on both sides, not inferred.
- R-543 proven through its whole lifecycle on a fresh box: bar present while
  paused, gone for good once escrowed.
- Known rows met and recorded, not re-filed: R-542, R-536's failure events.

Also recorded honestly: three harness errors of mine (a script that announced
"all twelve deploys ACCEPTED" without checking, a "login ok (csrf 0)" that
turned eleven of my own 401s into what looked like product refusals, and a
head -12 that hid a disk), and a near-miss where I almost filed a defect
against a drive gate that was working and logging at DEBUG.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
2026-09-16 22:56:08 +02:00

18 lines
834 B
Bash
Executable File

#!/bin/bash
# Run on demo-hp AFTER the PVE install finishes.
#
# Why this exists: "Automatically reboot after successful installation" is ticked and the boot order
# is ide2;scsi0, so the box reboots straight back INTO the installer — and a completed install then
# looks exactly like a stuck one. A running guest also keeps the QEMU boot order it started with, so
# editing the config mid-run is not enough: the VM must be stopped.
#
# Completion is judged from the DISK, not from the screen.
set -u
V=336
echo "disk usage before: $(du -sh --block-size=1M /mnt/hdd_1/images/$V/vm-336-disk-1.raw 2>/dev/null | cut -f1) MiB"
qm stop $V; sleep 5
qm set $V --delete ide2
qm set $V --boot order=scsi0 # its OWN call, always
qm config $V | grep -E '^(boot|ide2|scsi)'
qm start $V && echo "started from disk at $(date -u +%FT%TZ)"