Description of problem:
Initial-setup fails to run on the BeagleBone Black, instead booting to login.
● initial-setup.service - Initial Setup configuration program
Loaded: loaded (/usr/lib/systemd/system/initial-setup.service; disabled; vendor preset: disabled)
Active: inactive (dead)
Apr 25 14:46:21 bbone-black org.fedoraproject.Anaconda.Boss: ERROR:anaconda.modules.boss.module_manager:Service /org/fedoraproject/Anaconda/Modules/Timezone fai>
Apr 25 14:46:21 bbone-black org.fedoraproject.Anaconda.Boss: ERROR:anaconda.modules.boss.module_manager:Service /org/fedoraproject/Anaconda/Modules/Services fai>
Apr 25 14:46:21 bbone-black org.fedoraproject.Anaconda.Boss: ERROR:anaconda.modules.boss.module_manager:Service /org/fedoraproject/Anaconda/Modules/Network fail>
Apr 25 14:46:22 bbone-black org.fedoraproject.Anaconda.Boss: ERROR:anaconda.modules.boss.module_manager:Service /org/fedoraproject/Anaconda/Addons/Baz failed to>
Apr 25 14:46:22 bbone-black org.fedoraproject.Anaconda.Boss: ERROR:anaconda.modules.boss.module_manager:Service /org/fedoraproject/Anaconda/Modules/Localization>
Apr 25 14:46:32 bbone-black initial-setup: Initial Setup finished successfully, disabling
Apr 25 14:46:33 bbone-black run-initial-setup: Removed /etc/systemd/system/graphical.target.wants/initial-setup.service.
Apr 25 14:46:33 bbone-black run-initial-setup: Removed /etc/systemd/system/multi-user.target.wants/initial-setup.service.
Apr 25 14:46:38 bbone-black initial-setup: Initial Setup has been disabled
Apr 25 14:46:39 bbone-black systemd: Started Initial Setup configuration program.
Every time on the beaglebone, other hardware initial-setup runs as expected.
Created attachment 1427319 [details]
journalctl -u initial-setup
Could you also attach the full journal from the run ? There might be some additional information there. Thanks in advance! :)
Created attachment 1427697 [details]
This also happens on x86_64 in qemu using both armhfp and aarch64 disk images.
Created attachment 1428903 [details]
journalctl armhfp disk image
Created attachment 1428904 [details]
journalctl aarch64 disk, x86_64 qemu
One possible cause could be that the DBUS modules take longer to start than the 30 seconds Initial Setup waits for them to start. So I've created an Initial Setup scratchbuild where the timeout has been bumped to 600 seconds:
If waiting 10 minutes doesn't help the issue is likely somewhere else. :)
(Still, the modules don't do much during startup, so it's weird at least one or two would not show up during the first 30 seconds.)
Created attachment 1430186 [details]
armhfp qemu scratch build
That works on the Beaglebone White, but fails on armhfp and aarch64 when the images are run in QEMU on x86, logs attached.
Created attachment 1430189 [details]
aarch64 qemu - initial-setup scratch build
(In reply to Paul Whalen from comment #10)
> Created attachment 1430189 [details]
> aarch64 qemu - initial-setup scratch build
Thanks - looks like the increased timeout helped, meaning 30 seconds is likely not enough for everything to start properly in this case.
I've just build a new version of Initial Setup for Rawhide (initial-setup-0.3.60) that does away with the 30 seconds timeout and uses the default value from Anaconda instead. Also in parallel I've build a new Rawhide Anaconda (anaconda-29.14) that bumps the default timeout to 600 seconds.
Other than that, looking at the logs something still seems to be wrong:
May 02 15:37:10 localhost.localdomain initial-setup: parsing input kickstart /root/anaconda-ks.cfg
May 02 15:37:10 localhost.localdomain initial-setup: kickstart parsing failed: The following problem occurred on line 0 of the kickstart file:
Unable to open input kickstart file: Error opening file: [Errno 2] No such file or directory: '/root/anaconda-ks.cfg'
May 02 15:37:10 localhost.localdomain initial-setup: Initial Setup startup failed due to invalid kickstart file
AFAIK there should be always an /root/anaconda-ks.cfg file it the ARM usecase or else Initial Setup will not know it should run in the reconfig mode.
We hit similar problems trying to install Fedora 28 s390x under QEMU TCG.
Without a ks.cfg, I can install it. With ks.cfg, I run into reported timeout.
Okay, looks like the starts aligned only once to allow me to install it. Now I keep getting the timeout also without ks.cfg.
Is there a way to override this timeout on the kernel cmdline?
i-s working in rawhide on both the Beaglebone black and qemu. Thanks Martin!