Description of problem: Kickstart installation using autopart doesn't work. Version-Release number of selected component (if applicable): F19-Alpha-TC4 anaconda 19.15 How reproducible: always Steps to Reproduce: 1. Start kickstart installation with attached kickstart. Actual results: Anaconda will stop in main hub and text under label "INSTALLATION DESTINATION" is switching from "No disk selected" to "Failed to save storage configuration" and back to "No disk selected" in loop again and again. Expected results: Succesful installation. Additional info:
Created attachment 731647 [details] kickstart
Created attachment 731648 [details] anaconda.log
Created attachment 731649 [details] packaging.log
Created attachment 731651 [details] programl.log
Created attachment 731652 [details] storage.log
python-blivet-0.10-1.fc19,anaconda-19.17-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/python-blivet-0.10-1.fc19,anaconda-19.17-1.fc19
Verified on anaconda-19.17-1 (Fedora 19 RC2).
*** Bug 948090 has been marked as a duplicate of this bug. ***
*** Bug 950169 has been marked as a duplicate of this bug. ***
This bug still exists in F19-Alpha-i386-RC4-DVD
Bug 948090 shows the ks with autopart directive being used and isntall stops at main menu and acts like no disk was chosen.
Turns out --all must be in clearpart directive for this not be a problem on previously populated disks.
Between F19 Alpha and F19 Beta RC4, this quit working even if clearpart --all is specified. The following quit working for me between those two versions ignoredisk --only-use=sda clearpart --all --initlabel --drives=sda autopart --encrypted --type=plain --passphrase=${DISK_PASSPHRASE}
What do you mean by 'quit working', exactly?
Sorry for the hasty report. Anaconda used to clear all of the partitions on sda and install F19 on that drive with the partitioning scheme chosen by 'autopart' Now, Anaconda waits at the main hub claimimg that it doesn't have anywhere to install to. When I select the disk spoke, everything is already selected properly, but I have to reclaim the space on sda. See the attached anaconda.log-ajsfedora-Beta The six minute break between lines 138 and 139 is just me reclaiming the disk space on sda and accepting all of the settings from the kickstart file. I'm going through the storage.log file for privacy and I'll upload it in a few minutes.
Created attachment 754966 [details] anaconda.log file after a kickstart install using F19 Beta
Created attachment 754977 [details] storage.log file after a kickstart install using F19 Beta
Ah, that sounds rather like another bug we've been looking at, currently under https://bugzilla.redhat.com/show_bug.cgi?id=967527 but probably going to be split out from it. I think we can close this one, but please follow up there.
I'm running an install from F19-Alpha to collect the logs. Should I post those logs there or here?