Bug 1572316 - initial-setup fails on the BeagleBone Black - Anaconda DBus modules failed to start on time.
Summary: initial-setup fails on the BeagleBone Black - Anaconda DBus modules failed t...
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: initial-setup
Version: 28
Hardware: armhfp
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Martin Kolman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
 
Reported: 2018-04-26 16:27 UTC by Paul Whalen
Modified: 2018-07-09 18:14 UTC (History)
5 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2018-07-09 18:14:50 UTC


Attachments (Terms of Use)
journalctl -u initial-setup (12.02 KB, text/plain)
2018-04-26 16:28 UTC, Paul Whalen
no flags Details
beaglebone journalctl (128.06 KB, text/plain)
2018-04-27 14:46 UTC, Paul Whalen
no flags Details
journalctl armhfp disk image (136.95 KB, text/plain)
2018-04-30 17:02 UTC, Paul Whalen
no flags Details
journalctl aarch64 disk, x86_64 qemu (148.67 KB, text/plain)
2018-04-30 17:04 UTC, Paul Whalen
no flags Details
armhfp qemu scratch build (471.91 KB, text/plain)
2018-05-02 16:24 UTC, Paul Whalen
no flags Details
aarch64 qemu - initial-setup scratch build (800.19 KB, text/plain)
2018-05-02 16:25 UTC, Paul Whalen
no flags Details

Description Paul Whalen 2018-04-26 16:27:31 UTC
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[916]: ERROR:anaconda.modules.boss.module_manager:Service /org/fedoraproject/Anaconda/Modules/Timezone fai>
Apr 25 14:46:21 bbone-black org.fedoraproject.Anaconda.Boss[916]: ERROR:anaconda.modules.boss.module_manager:Service /org/fedoraproject/Anaconda/Modules/Services fai>
Apr 25 14:46:21 bbone-black org.fedoraproject.Anaconda.Boss[916]: ERROR:anaconda.modules.boss.module_manager:Service /org/fedoraproject/Anaconda/Modules/Network fail>
Apr 25 14:46:22 bbone-black org.fedoraproject.Anaconda.Boss[916]: 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[916]: ERROR:anaconda.modules.boss.module_manager:Service /org/fedoraproject/Anaconda/Modules/Localization>
Apr 25 14:46:32 bbone-black initial-setup[965]: Initial Setup finished successfully, disabling
Apr 25 14:46:33 bbone-black run-initial-setup[587]: Removed /etc/systemd/system/graphical.target.wants/initial-setup.service.
Apr 25 14:46:33 bbone-black run-initial-setup[587]: Removed /etc/systemd/system/multi-user.target.wants/initial-setup.service.
Apr 25 14:46:38 bbone-black initial-setup[986]: Initial Setup has been disabled
Apr 25 14:46:39 bbone-black systemd[1]: Started Initial Setup configuration program.


How reproducible:
Every time on the beaglebone, other hardware initial-setup runs as expected.

Comment 1 Paul Whalen 2018-04-26 16:28 UTC
Created attachment 1427319 [details]
journalctl -u initial-setup

Comment 2 Martin Kolman 2018-04-27 08:58:46 UTC
Could you also attach the full journal from the run ? There might be some additional information there. Thanks in advance! :)

Comment 3 Paul Whalen 2018-04-27 14:46 UTC
Created attachment 1427697 [details]
beaglebone journalctl

Comment 4 Paul Whalen 2018-04-30 17:01:58 UTC
This also happens on x86_64 in qemu using both armhfp and aarch64 disk images.

Comment 5 Paul Whalen 2018-04-30 17:02 UTC
Created attachment 1428903 [details]
journalctl armhfp disk image

Comment 6 Paul Whalen 2018-04-30 17:04 UTC
Created attachment 1428904 [details]
journalctl aarch64 disk, x86_64 qemu

Comment 7 Martin Kolman 2018-05-02 15:04:36 UTC
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:
https://koji.fedoraproject.org/koji/taskinfo?taskID=26728316

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.)

Comment 8 Paul Whalen 2018-05-02 16:24 UTC
Created attachment 1430186 [details]
armhfp qemu scratch build

Comment 9 Paul Whalen 2018-05-02 16:24:42 UTC
That works on the Beaglebone White, but fails on armhfp and aarch64 when the images are run in QEMU on x86, logs attached.

Comment 10 Paul Whalen 2018-05-02 16:25 UTC
Created attachment 1430189 [details]
aarch64 qemu - initial-setup scratch build

Comment 11 Martin Kolman 2018-05-04 16:23:11 UTC
(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[630]: parsing input kickstart /root/anaconda-ks.cfg
May 02 15:37:10 localhost.localdomain initial-setup[630]: 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[630]: 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.

Comment 12 David Hildenbrand 2018-05-28 10:39:36 UTC
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.

Comment 13 David Hildenbrand 2018-05-28 10:44:21 UTC
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?

Comment 14 Paul Whalen 2018-07-09 18:14:50 UTC
i-s working in rawhide on both the Beaglebone black and qemu. Thanks Martin!


Note You need to log in before you can comment on or make changes to this bug.