Release Engineering

Tasklist

FS#35054 - [archiso] boot parameter no longer works

Attached to Project: Release Engineering
Opened by Sean (buckley310) - Wednesday, 01 May 2013, 20:16 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Friday, 27 September 2013, 22:29 GMT
Task Type Bug Report
Category ArchISO
Status Closed
Assigned To Gerardo Exequiel Pozzi (djgera)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

In the archlinux dual ISO images up to and including 2013-03 if you added a kernel parameter script=http://foo/bar.sh to the bootloader, the script would run on boot. This is broken in versions 2013-04 and 2013-05 because /root/.automated_script.sh no longer runs when the live system finishes booting. The script and everything still works if you manually run this script after you get root shell.

working:
archlinux-2013.03.01-dual.iso

not working:
archlinux-2013.04.01-dual.iso
archlinux-2013.05.01-dual.iso

grub2 config:
linux /arch/boot/x86_64/vmlinuz archisodevice=/dev/disk/by-uuid/XXXX-XXXX copytoram=y script=http://example.org/runscript.sh
initrd /arch/boot/x86_64/archiso.img
boot

Steps to reproduce:
install grub2 on a flash drive
save the included grub config as /boot/grub/grub.cfg on the flash drive and set valid values for "archisodevice" and "script"
extract the "arch" folder from the 2013-05 arch ISO and place it in the root of the flash drive
boot off the flash drive -- the script does not run
repeat with 2013-03 ISO -- the script runs
This task depends upon

Closed by  Gerardo Exequiel Pozzi (djgera)
Friday, 27 September 2013, 22:29 GMT
Reason for closing:  Fixed
Additional comments about closing:  Should work better with never versions of systemd. If not please reopen. Thanks.
Comment by Sean (buckley310) - Friday, 03 May 2013, 17:11 GMT
My mistake, I ran it a bunch of times with varying options and it seems that the script runs, but it does so before DNS is functional. So far every time I specify an IP address it works fine, but with a DNS name it does not work unless you get a root shell and run it manually which takes several seconds. The 2013-03 image is still working reliably with DNS.
Comment by Gerardo Exequiel Pozzi (djgera) - Friday, 03 May 2013, 17:30 GMT
So is a timming issue. We are using a dhcp service for all interfaces, also there is no way to guarantee interface names (sometimes you will get a fixed "eth0" others the predictable names).
Comment by Gerardo Exequiel Pozzi (djgera) - Saturday, 01 June 2013, 14:17 GMT
A bit better may work this with 2013.06, please test and report back. Thanks.
Comment by Sean (buckley310) - Tuesday, 04 June 2013, 12:51 GMT
The 2013.06 version works most of the time but will still fail occasionally.

Loading...