Bug 868834

Michal, please upload anaconda logs (from /tmp) and your kickstart file. I just finished successful kickstarted minimal installation using anaconda 18.19.

Created attachment 631447 [details]
working kickstart

Kamil, I can't upload anaconda logs because system is rebooted immediately. Your kickstart works for me, but when I used autopart, system is terminated.

Created attachment 632559 [details]
doesn't work

Created attachment 632560 [details]
works

The kickstart should be enough for developers to try to reproduce, but if you want to help them, Michal, then run this in a virtual machine and redirect system output to a serial console (using "console=ttyS0 graphical" boot arguments). That way you can gather some information and provide it here. Thanks.

I think there are also some anaconda arguments to use remote syslog, so that you can send your logs to a different machine. I never tried that, though.

Created attachment 632623 [details]
console.log

Created attachment 632680 [details]
console.log with nokill

Created attachment 632684 [details]
anaconda.log

Created attachment 632685 [details]
program.log

Created attachment 632686 [details]
storage.log

Created attachment 632687 [details]
syslog

Created attachment 632982 [details]
broken kickstart

Hmm, now I hit this too with the ks above.

Proposing as F18 Blocker, but we seem to miss appropriate criterion.

Oh, the kickstart I uploaded is the kickstart anaconda produces on default install (with just partitioning changes). So we have a criterion for it and it's Beta:
" The installer must be able to successfully complete a scripted installation, using the installer's preferred scripting system, which duplicates the default interactive installation as closely as possible "
https://fedoraproject.org/wiki/Fedora_18_Beta_Release_Criteria

I'm not able to reproduce using Beta TC6 and either:

%packages --nobase
%end

or

%packages --default
%end

In both cases I get just @core selected and the install progresses into actually installing packages.

Kamil's problem should be a new bug, I think it has to do some something else in the kickstart data, not something to do with the %packages selection.

Closing this one as fixed.

Hi Jesse, 
did you try 'broken kickstart' or "doesn't work" from attachments? As I mention in comment 3, there is problem with autopart and package section in kickstart.

I have tried autopart without package section - works
I have tried native partitioning and package section - works
I have tried autopart and package section - doesn't work

Figured out what was going on here.  Essentially it was a race condition that was triggered by the combos you listed.  A fix has been posted for review.

Discussed at 2012-10-29 QA meeting acting as a blocker review meeting: http://meetbot.fedoraproject.org/fedora-meeting/2012-10-29/fedora-qa.2012-10-29-15.00.html . Accepted as a blocker per criterion cited in comment #15.

Pushed into master, will be in the next build.

anaconda-18.22-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.22-1.fc18

Package anaconda-18.22-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.22-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-17432/anaconda-18.22-1.fc18
then log in and leave karma (feedback).

Michal, the fix should be in the smoke13 build: https://dl.fedoraproject.org/pub/alt/qa/18/20121031_f18b-smoke13/ . Can you re-test with that and mark this as VERIFIED if it works? Thanks!

anaconda-18.23-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.23-1.fc18

I've re-tested this issue with broken kickstarts from attachment on smoke14. Installation finished successfully.
Moving to VERIFIED

Package anaconda-18.23-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.23-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-17509/anaconda-18.23-1.fc18
then log in and leave karma (feedback).

anaconda-18.24-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.24-1.fc18

anaconda-18.25-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.25-1.fc18

Package anaconda-18.25-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.25-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-17691/anaconda-18.25-1.fc18
then log in and leave karma (feedback).

anaconda-18.26-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.26-1.fc18

This was verified back in comment #25. setting back.

18.26 went stable. Closing. (Bodhi closing of bugs when updates go stable is currently broken).