Red Hat Bugzilla – Bug 1296495
Rawhide Minimal ARM image from 20160106 is missing initial-setup package
Last modified: 2016-01-14 12:46:52 EST
Description of problem:
Rawhide Minimal image from 20160106 for ARM is missing initial-setup package, so user is unable to set root password (and create user) on the first boot. Fedora is booting directly to login screen (instead of initial-setup, as it should have).
Version-Release number of selected component (if applicable):
Fedora 24 Rawhide 20160106, minimal disk raw image
Steps to Reproduce:
1. Download image (from https://kojipkgs.fedoraproject.org/work/tasks/3983/12433983/Fedora-Minimal-armhfp-rawhide-20160106-sda.raw.xz)
2. Unxzip it
3. Extract kernel with "virt-builder --get-kernel Fedora-Minimal-armhfp-rawhide-20160106-sda.raw"
4. Run image using QEMU with
"qemu-system-arm -machine virt -m 1024 -device VGA -kernel vmlinuz-4.4.0-0.rc8.git0.1.fc24.armv7hl -initrd initramfs-4.4.0-0.rc8.git0.1.fc24.armv7hl.img -append 'rw root=LABEL=_/ rootwait' -device virtio-blk-device,drive=hd1 -drive file=Fedora-Minimal-armhfp-rawhide-20160106-sda.raw,cache=unsafe,id=hd1,if=none,format=raw -device usb-ehci -device usb-tablet -device usb-kbd -serial stdio"
3. Mount image locally
Although symlink "initial-setup-text.service" exists in "/etc/systemd/system/multi-user.target.wants/", it leads nowhere and there is no "initial-setup" binary in "/usr/bin". When booting using QEMU, initial-setup doesn't start.
initial-setup should start after first boot before login screen is shown.
Proposed as a Blocker for 24-beta by Fedora user jsedlak using the blocker tracking app because:
Violates Alpha criterion: Release-blocking ARM disk images must boot to the initial-setup utility.
initial-setup-text is enabled in the kickstarts on the minimal and server disk images. for some reason it is not running correctly.
(In reply to Dennis Gilmore from comment #2)
> initial-setup-text is enabled in the kickstarts on the minimal and server
> disk images. for some reason it is not running correctly.
The Initial Setup services (initial-setup-text.service and initial-setup-graphical.service) have been merged to a single service, called just initial-setup.service.
The single service handles both GUI and TUI, based on which packages are installed. If you install both the base initial-setup package and initial-setup-gui the GUI would run. Inf only the base initial-setup package is installed, then the TUI would run. Also if the GUI fails to start Initial setup should safely fall back to TUI.
So basically only installing the initial-setup package and making sure the initial-setup.service is enabled should be enough to fix this issue.
symlink just needs to be updated in spins kickstarts.
oops, as Martin said, just enabling the service in the ks should be fine now, no more hacks needed.
should be fixed in tomorrows rawhide compose
Confirmed i-s runs on todays Xfce and Minimal images. Thanks!