v0.5.27: rd.luks.uuid via grubby, GRUB rebrand, fbcon=nodefer, ASCII gum cursor
Critical install bug fix + cosmetic round-up + first formal test procedure document. ## Critical: LUKS unlock on first boot Generated installer kickstart's %post was injecting `rd.luks.uuid=…` into `/etc/default/grub` only. Fedora 43 uses BLS (Boot Loader Specification) entries in `/boot/loader/entries/*.conf`; those are NOT regenerated by `grub2-mkconfig`. Result: the kernel boots without `rd.luks.uuid=`, dracut's cryptsetup-generator never spawns the unlock unit, plymouth has no password to ask for, and dracut-initqueue loops on dev-disk-by-uuid for ~3min before dropping to emergency shell. The fix layers both write paths: - `/etc/default/grub` — keeps the args around for future kernels (kernel-install reads this when adding new entries). - `grubby --update-kernel=ALL --args=...` — rewrites the `options` line of every existing BLS entry so the kernel that boots NEXT actually has the args. Verified by reading `/proc/cmdline` from the dracut emergency shell on a v0.5.26 install; old cmdline had only `root=UUID=… ro rootflags=subvol=root` and was missing the LUKS arg entirely. ## GRUB / branding - `/etc/default/grub` is sed'd to `GRUB_DISTRIBUTOR="veilor-os"` (was already there, kept). - BLS entries' `title` line is rewritten in-place to "veilor-os (<kver>)" for every kernel — `grub2-mkconfig` does not touch BLS titles, so this is the only path. - `/boot/loader/entries/*-0-rescue-*.conf` is removed: the auto-built rescue entry was leaking "Fedora Linux" into the GRUB menu and showing a second boot option that nobody asked for. The rescue kernel image itself is left in /boot. - Hostname defaults to `veilor` (was inheriting the `localhost-live` name anaconda writes when the kickstart's network directive is ignored under cmdline mode). - `/etc/machine-info` adds `PRETTY_HOSTNAME="veilor-os"` so `hostnamectl status` and any consumer reading machine-info see the brand. ## Boot UX - `fbcon=nodefer` added to live-ISO bootloader cmdline. On real laptops with a hardware GPU, the kernel modeset blanks the framebuffer console mid-boot; without `nodefer` the installer banner draws into a frozen framebuffer and the user sees a black screen with a blinking cursor for ~30s. virtio-vga in QEMU doesn't trigger this so it never reproduced in VM. Symptom report on v0.5.26 was the trigger to investigate. ## Installer cosmetics - `GUM_CHOOSE_CURSOR` and `GUM_INPUT_PROMPT` switched from `❯ ` to `> `. The unicode arrow falls back to a fixed-width block on the linux fbcon font and lipgloss then duplicates that block at col +23, producing the "Install Install" double-render and the stray-T artifact in password fields. Plain ASCII renders identically across fbcon, virtio-vga, and X/Wayland gum runs. - `VERSION_ID` bumped 0.5.8 → 0.5.27 in the os-release drop-in. The installer banner reads this at runtime, so the live ISO + installed system both now show "veilor-os 0.5.27". ## Test procedure - `test/TESTING.md` — first canonical test procedure document. Splits VM (cheap iteration, hybrid sendkey + human passwords) from real hardware (mandatory for tag). Documents the standard test passwords (`veilortest1` for both LUKS and admin), the kill-and-relaunch step to skip CD on second boot, and the per-step pass/fail contract. - `test/METHOD-CHANGELOG.md` — append-only audit trail for changes to the procedure. Future releases that alter the test method must add an entry here with the why. - `test/test-runs/_TEMPLATE.md` — per-run report template. Each tagged release should land a filled report alongside it. ## test/run-vm.sh Decoupled QEMU monitor sock setup from auto-inject. Previously `NO_INJECT=1` (used to suppress autotype noise into prompts) also killed the monitor sock, leaving the VM undriveable. Monitor sock is now always exposed; only the inject helper is gated on the pubkey detection.
This commit is contained in:
veilor-org
parent
c89c73ee84
commit
1881c14ea7
8 changed files with 398 additions and 17 deletions
|
|
@ -28,7 +28,13 @@ export GUM_CHOOSE_HEADER_FOREGROUND="$VEILOR_FG"
|
|||
export GUM_CHOOSE_ITEM_FOREGROUND="$VEILOR_FG"
|
||||
export GUM_CHOOSE_SELECTED_FOREGROUND="$VEILOR_FG"
|
||||
export GUM_CHOOSE_SELECTED_BACKGROUND="$VEILOR_DIM"
|
||||
export GUM_CHOOSE_CURSOR="❯ "
|
||||
# Plain ASCII cursor `> ` (was `❯ `). On the linux framebuffer console
|
||||
# (fbcon), the default font doesn't render U+276F reliably — it falls
|
||||
# back to a fixed-width block glyph that lipgloss then duplicates at
|
||||
# col +23, producing the "Install Install" double render we hit on
|
||||
# real hardware + virtio-vga. ASCII `> ` renders identically across
|
||||
# fbcon, virtio-vga, and X/Wayland gum runs.
|
||||
export GUM_CHOOSE_CURSOR="> "
|
||||
|
||||
# ── gum input ──────────────────────────────────────────
|
||||
# Single-line text entry (hostname).
|
||||
|
|
@ -36,7 +42,7 @@ export GUM_INPUT_PROMPT_FOREGROUND="$VEILOR_DIM"
|
|||
export GUM_INPUT_CURSOR_FOREGROUND="$VEILOR_FG"
|
||||
export GUM_INPUT_PLACEHOLDER_FOREGROUND="$VEILOR_MUTE"
|
||||
export GUM_INPUT_HEADER_FOREGROUND="$VEILOR_FG"
|
||||
export GUM_INPUT_PROMPT="❯ "
|
||||
export GUM_INPUT_PROMPT="> "
|
||||
|
||||
# ── gum write (multi-line) ─────────────────────────────
|
||||
# Reserved for any longer-form prompts; not used in v0.5.1 yet.
|
||||
|
|
|
|||
|
|
@ -51,7 +51,14 @@ user --name=admin --groups=wheel --gecos="veilor admin" --password="" --plaintex
|
|||
# Note: init_on_alloc/init_on_free removed from default live cmdline —
|
||||
# they zero every memory page at boot which 5x'd KVM live boot time.
|
||||
# Re-enable per-install via veilor-firstboot.service for production.
|
||||
bootloader --location=mbr --append="lockdown=integrity slab_nomerge randomize_kstack_offset=on vsyscall=none plymouth.enable=0"
|
||||
# `fbcon=nodefer` keeps the linux framebuffer console alive across the
|
||||
# KMS modeset that intel/amdgpu/nvidia drivers do during userspace init.
|
||||
# Without it, on real hardware the screen blanks the moment the GPU
|
||||
# driver loads and the installer's tty1 redraw lands on a frozen
|
||||
# framebuffer — symptom: black screen with blinking cursor for ~30s
|
||||
# while the menu IS in fact rendered, just not painted. virtio-vga in
|
||||
# QEMU doesn't trigger this so it never reproed in VM.
|
||||
bootloader --location=mbr --append="lockdown=integrity slab_nomerge randomize_kstack_offset=on vsyscall=none plymouth.enable=0 fbcon=nodefer"
|
||||
|
||||
# ── Live ISO partitioning (flat — for live rootfs build only) ──
|
||||
# NOTE: This is the *live* image kickstart. Final installed system uses
|
||||
|
|
|
|||
|
|
@ -1,9 +1,9 @@
|
|||
NAME="veilor-os"
|
||||
PRETTY_NAME="veilor-os 0.1"
|
||||
PRETTY_NAME="veilor-os 0.5.27"
|
||||
ID=veilor
|
||||
ID_LIKE=fedora
|
||||
VERSION="0.5.8"
|
||||
VERSION_ID="0.5.8"
|
||||
VERSION="0.5.27"
|
||||
VERSION_ID="0.5.27"
|
||||
HOME_URL="https://github.com/veilor-org/veilor-os"
|
||||
DOCUMENTATION_URL="https://github.com/veilor-org/veilor-os/tree/main/docs"
|
||||
BUG_REPORT_URL="https://github.com/veilor-org/veilor-os/issues"
|
||||
|
|
|
|||
|
|
@ -563,14 +563,39 @@ sed -i \
|
|||
/etc/default/grub 2>/dev/null || true
|
||||
|
||||
# Ensure rd.luks.uuid + rd.luks.name in cmdline. Anaconda --cmdline mode
|
||||
# sometimes skips the LUKS auto-args; without these, dracut's
|
||||
# cryptsetup-generator never creates the unlock unit + dracut-initqueue
|
||||
# loops on dev-disk-by-uuid forever. Detect LUKS partition + inject
|
||||
# explicitly if missing.
|
||||
# does not auto-add the LUKS args when partitioning is custom + encrypted
|
||||
# manually; without rd.luks.uuid in cmdline, dracut's cryptsetup-generator
|
||||
# never spawns the unlock unit, plymouth has no password to ask for, and
|
||||
# dracut-initqueue loops on dev-disk-by-uuid for ~3min before dropping
|
||||
# to emergency shell. Detect the LUKS partition + inject explicitly.
|
||||
#
|
||||
# Two write paths because Fedora 43 uses BLS (Boot Loader Specification):
|
||||
# 1. /etc/default/grub — read by `grub2-mkconfig` for the legacy
|
||||
# grub.cfg menu, AND used as the source of
|
||||
# truth for `kernel-install` when adding new
|
||||
# kernels later.
|
||||
# 2. /boot/loader/entries/*.conf — the actual per-kernel BLS entries
|
||||
# that grub reads for cmdline. These
|
||||
# are NOT regenerated by
|
||||
# `grub2-mkconfig`; they are managed
|
||||
# by `grubby` (or `kernel-install`).
|
||||
# Without both, the running kernel boots without rd.luks.uuid and the
|
||||
# user lands in emergency shell on first boot.
|
||||
LUKS_UUID=$(blkid -t TYPE=crypto_LUKS -o value -s UUID 2>/dev/null | head -1)
|
||||
if [ -n "$LUKS_UUID" ] && ! grep -q "rd.luks.uuid" /etc/default/grub 2>/dev/null; then
|
||||
sed -i "s|^GRUB_CMDLINE_LINUX=\"|GRUB_CMDLINE_LINUX=\"rd.luks.uuid=luks-${LUKS_UUID} |" /etc/default/grub
|
||||
echo "[INFO] injected rd.luks.uuid=luks-${LUKS_UUID} into GRUB cmdline"
|
||||
if [ -n "$LUKS_UUID" ]; then
|
||||
LUKS_ARGS="rd.luks.uuid=luks-${LUKS_UUID}"
|
||||
|
||||
# Path 1: persist into /etc/default/grub so future kernels inherit.
|
||||
if ! grep -q "rd.luks.uuid" /etc/default/grub 2>/dev/null; then
|
||||
sed -i "s|^GRUB_CMDLINE_LINUX=\"|GRUB_CMDLINE_LINUX=\"${LUKS_ARGS} |" /etc/default/grub
|
||||
fi
|
||||
|
||||
# Path 2: update existing BLS entries so the kernel that boots NEXT
|
||||
# gets the args. grubby walks /boot/loader/entries/*.conf and edits
|
||||
# the `options` line in-place.
|
||||
grubby --update-kernel=ALL --args="${LUKS_ARGS}" 2>&1 | tail -5 || true
|
||||
|
||||
echo "[INFO] injected ${LUKS_ARGS} into /etc/default/grub + BLS entries"
|
||||
fi
|
||||
|
||||
# Switch plymouth to text-only `details` theme (scrolling boot log, no
|
||||
|
|
@ -586,6 +611,38 @@ grub2-mkconfig -o /boot/grub2/grub.cfg 2>/dev/null || true
|
|||
[ -f /boot/efi/EFI/fedora/grub.cfg ] && \
|
||||
grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg 2>/dev/null || true
|
||||
|
||||
# Suppress the auto-generated "Fedora Linux 0-rescue-…" BLS entry. Fedora
|
||||
# ships a rescue kernel image alongside every install; the BLS entry that
|
||||
# points at it is created by `kernel-install` and shows up in GRUB as a
|
||||
# second menu item. For a branded distro it's noisy + reveals "Fedora"
|
||||
# in the menu. The rescue image itself is harmless to keep on disk.
|
||||
rm -f /boot/loader/entries/*-0-rescue-*.conf 2>/dev/null || true
|
||||
|
||||
# Hostname: default to "veilor" rather than the localhost-live / fedora
|
||||
# fallback that anaconda writes. User can override post-install with
|
||||
# `hostnamectl set-hostname`.
|
||||
echo "veilor" > /etc/hostname
|
||||
|
||||
# /etc/machine-info — feeds `hostnamectl status` and some BLS title
|
||||
# rendering paths. PRETTY_HOSTNAME is what GRUB titles read when
|
||||
# GRUB_DISTRIBUTOR doesn't override (Fedora 43 BLS entry titles ignore
|
||||
# GRUB_DISTRIBUTOR; this is the closest we can get without rewriting
|
||||
# every entry's `title` line).
|
||||
cat > /etc/machine-info <<'MACHINFO'
|
||||
PRETTY_HOSTNAME="veilor-os"
|
||||
MACHINFO
|
||||
|
||||
# Rewrite the `title` line of every remaining BLS entry to use our
|
||||
# brand. `kernel-install` will write new entries with "Fedora Linux …"
|
||||
# but the file we ship + every kernel update goes through grubby which
|
||||
# preserves whatever title was last set.
|
||||
for entry in /boot/loader/entries/*.conf; do
|
||||
[ -f "$entry" ] || continue
|
||||
# Pull kernel version out of the existing title (e.g. "6.17.1-300.fc43.x86_64")
|
||||
kver=$(awk '/^version / {print $2}' "$entry")
|
||||
sed -i "s|^title .*|title veilor-os (${kver})|" "$entry"
|
||||
done
|
||||
|
||||
# Symlink display-manager.service → sddm.service. (Anaconda usually
|
||||
# handles this when sddm is the only DM, but be explicit.)
|
||||
ln -sf /usr/lib/systemd/system/sddm.service /etc/systemd/system/display-manager.service
|
||||
|
|
|
|||
41
test/METHOD-CHANGELOG.md
Normal file
41
test/METHOD-CHANGELOG.md
Normal file
|
|
@ -0,0 +1,41 @@
|
|||
# veilor-os — Test Method Changelog
|
||||
|
||||
Append-only log of changes to `test/TESTING.md`. Each entry: date, the
|
||||
veilor-os version it first applied to, what changed in the procedure,
|
||||
and *why*. The why is the load-bearing part — without it this file
|
||||
becomes a list of opinions.
|
||||
|
||||
Entries are newest-first.
|
||||
|
||||
---
|
||||
|
||||
## 2026-05-05 · v0.5.27 · TESTING.md created
|
||||
|
||||
**Change:** First version of the canonical procedure document.
|
||||
|
||||
**Why:** Through v0.2 → v0.5.26 we'd been reproducing the test
|
||||
procedure ad-hoc each time, which meant test runs were uncomparable
|
||||
and regressions were caught only by accident. The v0.5.26 → v0.5.27
|
||||
debugging session surfaced the LUKS-cmdline bug, the GRUB rebrand
|
||||
gap, the gum-cursor render glitch, and the fbcon KMS issue all in a
|
||||
single VM run — but only because the test happened to walk every step
|
||||
in order. Codifying the steps means the next regression is caught the
|
||||
same way reliably.
|
||||
|
||||
The procedure documents the **hybrid VM method** explicitly: Claude
|
||||
drives every step it can via QEMU monitor `sendkey`, the human types
|
||||
LUKS + admin passwords directly into the QEMU window because plymouth
|
||||
ignores synthesised keystrokes. Past trail (14+ failed sendkey
|
||||
variants) is the source of truth for that limitation; do not re-fight
|
||||
that battle without first rereading the trail.
|
||||
|
||||
The procedure also separates **VM** (cheap iteration, catches install
|
||||
logic) from **real hardware** (mandatory for tag, catches firmware /
|
||||
KMS / GPU). Future releases must produce a `test/test-runs/` report
|
||||
for each before tagging.
|
||||
|
||||
**Files added:**
|
||||
- `test/TESTING.md` — canonical procedure
|
||||
- `test/METHOD-CHANGELOG.md` — this file
|
||||
- `test/test-runs/` — per-run reports go here (template lands with
|
||||
first real run, currently empty)
|
||||
187
test/TESTING.md
Normal file
187
test/TESTING.md
Normal file
|
|
@ -0,0 +1,187 @@
|
|||
# veilor-os — Testing Procedure
|
||||
|
||||
This document is the canonical procedure for validating a veilor-os ISO
|
||||
end-to-end. Every release that gets a tag MUST have a corresponding
|
||||
test-run report in `test/test-runs/` linked from the release notes.
|
||||
|
||||
If reality forces you to deviate from the steps below, **do not silently
|
||||
patch the procedure** — open a commit that updates this file *and*
|
||||
appends an entry to `test/METHOD-CHANGELOG.md` explaining what changed
|
||||
and why. The changelog is what makes the procedure auditable; the
|
||||
procedure itself is just the latest snapshot.
|
||||
|
||||
---
|
||||
|
||||
## Two test environments
|
||||
|
||||
| Environment | Catches | Doesn't catch |
|
||||
|-------------|---------|---------------|
|
||||
| **VM (QEMU + virtio-vga)** | install logic, kickstart bugs, %post failures, anaconda transaction failures, GRUB write, BLS entries, package selection, network stack | KMS / fbcon issues, real-firmware Secure Boot, USB controller quirks, GPU driver compatibility, sleep/wake, battery, thermals |
|
||||
| **Real hardware (USB → spare laptop)** | everything VM doesn't | install repeatability (you only have so many spare laptops) |
|
||||
|
||||
Both are required for any tagged release. VM first (cheap iteration),
|
||||
real hardware second (final sign-off).
|
||||
|
||||
---
|
||||
|
||||
## VM test — hybrid procedure
|
||||
|
||||
The VM cannot type LUKS / admin passwords through QEMU's `sendkey`
|
||||
monitor command — plymouth's IPC ignores synthesised keystrokes (we
|
||||
verified this across 14+ sendkey variants in earlier sessions). The
|
||||
hybrid procedure splits the work: Claude/automation drives every step
|
||||
that doesn't need a password; the human types the two passwords (LUKS
|
||||
+ admin) into the QEMU window directly.
|
||||
|
||||
Standard test passwords (lab use only — never reuse outside this repo):
|
||||
|
||||
| Prompt | Type |
|
||||
|--------|------|
|
||||
| LUKS passphrase | `veilortest1` |
|
||||
| Admin password | `veilortest1` |
|
||||
|
||||
Both passwords identical on purpose — easier to remember mid-test, both
|
||||
satisfy the installer's 8-char min, neither contains shell-special
|
||||
chars (validate_pw rejects `" $ \ \` & | / \n`).
|
||||
|
||||
### Run a VM test
|
||||
|
||||
```bash
|
||||
cd ~/ai-lab/_github/veilor-os
|
||||
# Pull the ISO you want to test (from a CI release or local build)
|
||||
ls /home/admin/Downloads/veilor-os-*.iso
|
||||
|
||||
# Wipe stale state, launch VM with monitor sock (no auto-inject — we
|
||||
# don't want sendkey noise typing into prompts)
|
||||
FRESH=1 NO_INJECT=1 DISPLAY=:0 ./test/run-vm.sh \
|
||||
/home/admin/Downloads/veilor-os-43-YYYYMMDD-HHMMSS.iso
|
||||
```
|
||||
|
||||
Then either (a) drive the install yourself in the QEMU window, or
|
||||
(b) hand the monitor sock to Claude / a script:
|
||||
|
||||
- Monitor sock: `test/veilor-vm.monitor.sock`
|
||||
- Send a key: `echo "sendkey ret" | socat - "UNIX-CONNECT:$SOCK"`
|
||||
- Screendump: `echo "screendump /tmp/x.ppm" | socat - "UNIX-CONNECT:$SOCK"; magick /tmp/x.ppm /tmp/x.png`
|
||||
|
||||
### Steps to verify
|
||||
|
||||
The complete checklist lives in `test/boot-checklist.md` — that file is
|
||||
the granular pass/fail list. The high-level flow is:
|
||||
|
||||
1. **Live boot.** GRUB (legacy menu, no Plymouth splash) → text scroll
|
||||
→ veilor-installer banner on tty1 within ~30s. No "fedora" branding
|
||||
anywhere on screen.
|
||||
2. **Installer menu.** "Install" highlighted by default. No phantom
|
||||
duplicate items, no stray characters in input fields.
|
||||
3. **Disk picker.** `/dev/vda` (or whatever virtio gives you) listed
|
||||
with size + model.
|
||||
4. **Passwords.** LUKS + admin prompts; user types `veilortest1` twice.
|
||||
5. **Locale.** en_GB.UTF-8 picks up.
|
||||
6. **Confirm.** Disk shown with `WILL BE ERASED`, locale + LUKS/admin
|
||||
ticks shown.
|
||||
7. **Anaconda.** "Installing veilor-os to /dev/vda · 10–30 min · logs
|
||||
on tty4". Watch for `Configuring man-db` — if anything fails, this
|
||||
is historically where it dies.
|
||||
8. **Reboot.** VM reboots; ISO must NOT boot first this time. Kill
|
||||
QEMU + relaunch without ISO drive (see *Boot installed disk* below)
|
||||
to skip the GRUB-from-ISO path.
|
||||
9. **GRUB.** Single "veilor-os" entry (no rescue, no "Fedora Linux").
|
||||
10. **LUKS prompt.** Plymouth `details` theme — text-mode prompt for
|
||||
passphrase. User types `veilortest1` in the QEMU window (sendkey
|
||||
will not work).
|
||||
11. **First boot.** SDDM splash → admin user pre-filled → admin types
|
||||
`veilortest1` → password-change prompt (chage -d 0 expired the
|
||||
password) → user picks new password → KDE Plasma session.
|
||||
12. **Hardening checks** per `test/boot-checklist.md` (SELinux
|
||||
enforcing, fail2ban active, USBGuard active, tuned profile, etc.).
|
||||
|
||||
### Boot installed disk (skip ISO)
|
||||
|
||||
After the install reboots, QEMU's CD-first boot order will land back
|
||||
in the live ISO. Easiest workaround: kill QEMU and re-launch without
|
||||
the `-drive file=...iso` line. The qcow2 retains the install:
|
||||
|
||||
```bash
|
||||
pkill -f 'qemu-system.*veilor-os'
|
||||
cd ~/ai-lab/_github/veilor-os/test
|
||||
DISPLAY=:0 qemu-system-x86_64 \
|
||||
-enable-kvm -cpu host -smp 4 -m 4096 \
|
||||
-machine q35,smm=on \
|
||||
-global driver=cfi.pflash01,property=secure,value=on \
|
||||
-drive if=pflash,format=raw,readonly=on,file=/usr/share/edk2/ovmf/OVMF_CODE.fd \
|
||||
-drive if=pflash,format=raw,file=$PWD/veilor-vm.nvram \
|
||||
-drive file=$PWD/veilor-vm.qcow2,if=virtio,format=qcow2 \
|
||||
-monitor unix:$PWD/veilor-vm.monitor.sock,server,nowait \
|
||||
-netdev user,id=net0,hostfwd=tcp::2222-:22 \
|
||||
-device virtio-net-pci,netdev=net0 \
|
||||
-vga virtio -display gtk,gl=on
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Real-hardware test — USB → spare laptop
|
||||
|
||||
Required for every tagged release. The VM cannot reproduce KMS /
|
||||
fbcon / GPU-driver issues; only real silicon will.
|
||||
|
||||
### 1. Flash USB
|
||||
|
||||
```bash
|
||||
# 8GB+ USB stick, identified by lsblk (e.g. /dev/sda — confirm vendor)
|
||||
sudo umount /dev/sdX* 2>/dev/null
|
||||
sudo wipefs -a /dev/sdX
|
||||
sudo dd if=/path/to/veilor-os-*.iso of=/dev/sdX bs=4M status=progress conv=fsync
|
||||
sync
|
||||
sudo eject /dev/sdX
|
||||
```
|
||||
|
||||
Etcher / GNOME Disks also fine. Verify-after-flash is built into
|
||||
Etcher; for `dd`, run `cmp` on the first ISO_SIZE bytes if paranoid.
|
||||
|
||||
### 2. Boot test
|
||||
|
||||
- Disable Secure Boot in firmware (until we MOK-enroll our shim, which
|
||||
is v0.5+).
|
||||
- Boot from USB.
|
||||
- Walk the same numbered steps as the VM section, except:
|
||||
- On "TYPE NOW: passphrase" steps, you actually have a keyboard.
|
||||
- At step 8, the laptop will eject the USB and reboot to the
|
||||
installed system without intervention.
|
||||
- At step 11, do NOT use `veilortest1` for the post-install admin
|
||||
password change — pick something real if this is your daily-driver
|
||||
laptop, or a throwaway if it's a test machine. The kickstart's
|
||||
ChainOfTrust ends here; from this prompt forward you own the
|
||||
password.
|
||||
|
||||
### 3. Capture findings
|
||||
|
||||
Fill in a fresh `test/test-runs/YYYY-MM-DD-vX.Y.Z.md` from the
|
||||
template. **Always** capture: GRUB title, kernel cmdline (`cat
|
||||
/proc/cmdline`), `lsblk -f`, `getenforce`, `systemctl is-active fail2ban
|
||||
usbguard tuned auditd firewalld`, `journalctl -b -p err --no-pager`.
|
||||
|
||||
If anything regressed, that goes at the top of the report under
|
||||
**Regressions**, with a screenshot if possible.
|
||||
|
||||
---
|
||||
|
||||
## Per-run report template
|
||||
|
||||
Copy `test/test-runs/_TEMPLATE.md` (created when the first real
|
||||
test-run lands) and fill in section-by-section. Keep them brief —
|
||||
this is meant to be a 5-minute write-up, not a thesis.
|
||||
|
||||
---
|
||||
|
||||
## When to alter this procedure
|
||||
|
||||
If a step turns out to be wrong, redundant, or missing:
|
||||
|
||||
1. Edit this file.
|
||||
2. Append to `test/METHOD-CHANGELOG.md` with: date, version it first
|
||||
applied to, what changed, and why (cite a specific test-run report
|
||||
if the change is in response to a finding).
|
||||
3. Reference the changelog entry in your commit message.
|
||||
|
||||
The changelog is the audit trail. Don't skip it.
|
||||
|
|
@ -128,13 +128,16 @@ EOF
|
|||
fi
|
||||
fi
|
||||
|
||||
# ── QEMU monitor fallback (live ISO doesn't run cloud-init) ──
|
||||
# ── QEMU monitor unix socket ──
|
||||
# Always exposed so the host can drive the VM via `socat - UNIX-CONNECT:...`
|
||||
# (sendkey, screendump, etc.) for debugging. Independent of pubkey injection.
|
||||
rm -f "$MONITOR_SOCK"
|
||||
MONITOR_ARGS=(-monitor "unix:$MONITOR_SOCK,server,nowait")
|
||||
|
||||
# ── Auto-inject helper (live ISO doesn't run cloud-init) ──
|
||||
# Started in the background after a delay; sends keypresses through the
|
||||
# QEMU monitor unix socket to drop to a TTY and unblock SSH for liveuser.
|
||||
MONITOR_ARGS=()
|
||||
if [[ -n $HOST_PUBKEY ]]; then
|
||||
rm -f "$MONITOR_SOCK"
|
||||
MONITOR_ARGS=(-monitor "unix:$MONITOR_SOCK,server,nowait")
|
||||
|
||||
(
|
||||
# Wait for the VM to reach a usable login prompt (SDDM autologin →
|
||||
|
|
|
|||
80
test/test-runs/_TEMPLATE.md
Normal file
80
test/test-runs/_TEMPLATE.md
Normal file
|
|
@ -0,0 +1,80 @@
|
|||
# Test run — vX.Y.Z
|
||||
|
||||
- **Date:** YYYY-MM-DD
|
||||
- **ISO:** `veilor-os-43-YYYYMMDD-HHMMSS.iso` (sha256: `...`)
|
||||
- **Tester:** name / handle
|
||||
- **Environment:** VM (qemu/q35/ovmf, 4 vCPU, 4G RAM, virtio-vga) — OR — Real HW (model, CPU, GPU)
|
||||
|
||||
---
|
||||
|
||||
## Result
|
||||
|
||||
✅ Pass / ⚠️ Pass-with-issues / ❌ Fail
|
||||
|
||||
One-line summary.
|
||||
|
||||
---
|
||||
|
||||
## Regressions vs previous run
|
||||
|
||||
(Things that worked in the prior tagged release but failed here. Empty
|
||||
if none. Always check this section first when reading the report.)
|
||||
|
||||
---
|
||||
|
||||
## Per-step results
|
||||
|
||||
Walk `test/TESTING.md` step-by-step. Mark each pass/fail with a brief
|
||||
note when failed.
|
||||
|
||||
| # | Step | Result | Notes |
|
||||
|---|------|--------|-------|
|
||||
| 1 | Live boot to installer banner | ✅ | |
|
||||
| 2 | Installer menu render | ✅ | |
|
||||
| 3 | Disk picker | ✅ | |
|
||||
| 4 | LUKS + admin passwords | ✅ | |
|
||||
| 5 | Locale | ✅ | |
|
||||
| 6 | Confirm | ✅ | |
|
||||
| 7 | Anaconda transaction | ✅ | |
|
||||
| 8 | Reboot | ✅ | |
|
||||
| 9 | GRUB single veilor-os entry | ✅ | |
|
||||
| 10 | LUKS unlock prompt | ✅ | |
|
||||
| 11 | First boot → SDDM → KDE | ✅ | |
|
||||
| 12 | Hardening checks | ✅ | |
|
||||
|
||||
---
|
||||
|
||||
## Hardening verification
|
||||
|
||||
```
|
||||
$ getenforce
|
||||
Enforcing
|
||||
$ systemctl is-active fail2ban usbguard tuned auditd firewalld
|
||||
active
|
||||
active
|
||||
active
|
||||
active
|
||||
active
|
||||
$ cat /proc/cmdline
|
||||
... rd.luks.uuid=luks-... ...
|
||||
$ lsblk -f
|
||||
...
|
||||
```
|
||||
|
||||
Paste real output. If any service is inactive or any cmdline arg is
|
||||
missing, raise as a Regression above.
|
||||
|
||||
---
|
||||
|
||||
## Findings
|
||||
|
||||
Free-form notes. Cosmetic glitches, slow paths, surprising behaviour.
|
||||
|
||||
---
|
||||
|
||||
## Action items for next release
|
||||
|
||||
- [ ] ...
|
||||
- [ ] ...
|
||||
|
||||
(Linked PRs / commits if you opened any during the test.)
|
||||
Loading…
Reference in a new issue