Bug#1031643: some tests …

[Oliver Freyermuth <freyermuth@physik.uni-bonn.de>]

Hi Andi,

On Sat, 8 Apr 2023 17:38:10 +0200 "Andreas B. Mundt" <andi@debian.org> wrote:
>  • However, I also ran an installation with the original, unpatched
>    initrd and the boot parameters:
>    'auto=true priority=critical hostname=somename url=tftp://192.168.122.1 playbook=minimal.yml ---'
>    That works fine too.  The pressed file is [1] with minor, unrelated
>    changes.  So that's kind of confusing to me right now.   

FWIW, I've never used "priority=critical" on the kernel commandline. Maybe that is making the difference here?

The full commandline I used is:

initrd=boot/debian-initrd.gz interface=auto url=http://foreman.example.com/unattended/provision ramdisk_size=10800 root=/dev/rd/0 rw auto auto=true locale=en_US.UTF-8 netcfg/disable_dhcp=false ethdetect/prompt_missing_firmware=false hw-detect/load_firmware=false locale=en_US.UTF-8 hostname=laptop.example.com domain=example.com

This commandline does not show any questions in Buster / Bullseye, but raises the hostname question in Bookworm alpha2 and rc1,
and it's gone again in the patched version (while the preseed file in my case always specifies d-i netcfg/get_hostname and d-i netcfg/get_domain, but that's parsed too late in the game).

Cheers,
	Oliver