Description of problem: Currently initial-setup does not provide any valuable debugging informations in case that it does not start. Version-Release number of selected component (if applicable): f19 How reproducible: Steps to Reproduce: 1. Create incorrect kickstart (or use one from Fedora N +1) 2. RUn initial-setup 3. Actual results: initial-setups fails silently, returning 1 Expected results: initial-setups fails with an error messsage (i.e. the ks parsing error), returning 1 Additional info:
Proposed as a Freeze Exception for 21-beta by Fedora user m4rtink using the blocker tracking app because: Detailed logging messages massively improve debugging of Initial Setup issues.
Patch that adds comprehensive syslog-based logging to Initial Setup has been posted for review.
Discussed in 2014-10-20 Blocker Review meeting [1]. It was decided to punt mkolman can prepare a scratch build and pwhalen can test it. Then we'll proceed to vote in the bug. [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2014-10-20/
So this is the scratchbuild with the syslog logging patch added: http://koji.fedoraproject.org/koji/taskinfo?taskID=7917128
Discussed at 2014-10-22 freeze exception review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2014-10-22/f21-blocker-review.2014-10-22-16.03.log.txt . As pwhalen tested the scratch build and it seems fine on ARM (the key place where i-s really matters) we agreed to accept this, though it likely will not be pulled in if we try to do a hero RC1 today or tomorrow. If we wind up slipping, it'll get pulled in (if an update is submitted).
Tested on Minimal, KDE armhfp Beta TC4, ran without error.
initial-setup-0.3.25-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/initial-setup-0.3.25-1.fc21
(In reply to Adam Williamson (Red Hat) from comment #5) > Discussed at 2014-10-22 freeze exception review meeting: > http://meetbot.fedoraproject.org/fedora-blocker-review/2014-10-22/f21- > blocker-review.2014-10-22-16.03.log.txt . As pwhalen tested the scratch > build and it seems fine on ARM (the key place where i-s really matters) we > agreed to accept this, though it likely will not be pulled in if we try to > do a hero RC1 today or tomorrow. If we wind up slipping, it'll get pulled in > (if an update is submitted). So just in case, here is the update (I hope I managed to set it up right): https://admin.fedoraproject.org/updates/initial-setup-0.3.25-1.fc21
Package initial-setup-0.3.25-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing initial-setup-0.3.25-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-13580/initial-setup-0.3.25-1.fc21 then log in and leave karma (feedback).
Beta got shipped, so there's no need for FE status for Beta any more. The update should get shipped during the unfrozen period between Beta and Final, but re-nominate as Final FE if not.
initial-setup-0.3.25-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.