Created attachment 716080 [details] screenshot Description of problem: Kickstart install on vm with : install text url --url=http://fedora.cora.nwra.com/development/19/x86_64/os repo --name=rpmfusion-free-development-19-x86_64 --baseurl=http://rpmfusion.cora.nwra.com/free/fedora/development/19/x86_64/os repo --name=rpmfusion-nonfree-development-19-x86_64 --baseurl=http://rpmfusion.cora.nwra.com/nonfree/fedora/development/19/x86_64/os repo --name=cora-f19-x86_64 --baseurl=http://corpms.cora.nwra.com/fedora/19/x86_64 repo --name=adobe-linux-x86_64 --baseurl=http://adobe.cora.nwra.com/linux/x86_64/ repo --name=adobe-linux-i386 --baseurl=http://adobe.cora.nwra.com/linux/i386/ lang en_US.UTF-8 keyboard us rootpw --iscrypted xxxx firewall --disabled firstboot --disable selinux --enforcing timezone --utc America/Denver xconfig --startxonboot --defaultdesktop=KDE clearpart --all --initlabel part biosboot --fstype=biosboot --size=1 part / --size=3000 --grow part swap --recommended zerombr bootloader --location=mbr network --bootproto=dhcp --device=eth0 --onboot=on reboot Stops at Installation prompt with: 2) [!] Install Destination (No disks selected) Version-Release number of selected component (if applicable): 19.13
Created attachment 716082 [details] storage.log
Created attachment 716085 [details] anaconda.log
I can manually select vda for the install destination via the menu fine.
*** Bug 927621 has been marked as a duplicate of this bug. ***
The key here is that you have not specified an ignoredisk line, which is what the storage spokes are looking at to determine whether you've completed partitioning or not. Given that command is not required, we need to make the spokes smarter.
What is the workaround in this case? Using ignoredisk doesn't seem to help. I've tried ignoredisk --drives=vda and ignoredisk --only-use=vda.
Hi Chris, any update on this bug? This is currently blocking us from automated testing.
Interesting that this only appears to happen on "vd" disks, not "sd".
anaconda-19.21-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/anaconda-19.21-1.fc19
Package anaconda-19.21-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-19.21-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-6338/anaconda-19.21-1.fc19 then log in and leave karma (feedback).
Package anaconda-19.21-1.fc19, python-meh-0.23-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-19.21-1.fc19 python-meh-0.23-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-6338/python-meh-0.23-1.fc19,anaconda-19.21-1.fc19 then log in and leave karma (feedback).
There is a workaround for this issue: it will work in graphics mode. So, simply remove the line "text" from your kickstart temporarily.
anaconda-19.21-1.fc19, python-meh-0.23-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.