5c4ad6aecd
--pxe-boot boots the installed system with a kernel and initrd from the
network, so it needs a root= for that machine. It used to hardcode our
Fedora LVM layout, which is wrong for anything else -- including both
DGX Sparks.
Where the root device comes from, in order of preference:
- already recorded on the machine (provision recheck now collects it)
- probed over SSH when --pxe-boot is requested and the machine answers
- reported from the rescue shell by debug-setup.sh, which mounts each
candidate read-only and picks the one with /etc/fstab and /usr
The rescue image cannot report it unprompted -- %pre/%post do not run in
rescue mode -- so the probe lives in the script the operator curls, which
already existed for the nc listener.
/api/discover now preserves fields a report omits. The probe posts only a
root device, and blanking a machine's inventory as a side effect of that
would be silent data loss.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015nRFZXpKwUVE4SRSHw6GjF