Description of problem: Start installation in qemu-kvm with one disk. After anaconda starts, insert additional disk. In "MANUAL PARTITIONING" spoke click on "Reload storage configuration from disk." and then click on "Rescan Disks". After these steps there isn't new disk in "INSTALLATION DESTINATION" spoke. Version-Release number of selected component (if applicable): F19-Alpha-TC3 anaconda-19.14 How reproducible: always Steps to Reproduce: 1. Start installation in qemu-kvm with one disk. Use command: "qemu-kvm -vga std -monitor stdio -m 1024 -drive if=scsi,file=/tmp/disk1 -cdrom ~/iso_images/fedora/Fedora-19-Alpha-TC3-x86_64-DVD.iso -boot once=d -net nic,model=virtio -net tap" 2. Proceed to the "MANUAL PARTITIONING" spoke. 3. Click on "Reload storage configuration from disk." Now you can see message: "You can remove or insert additional disks at this time and press 'Rescan Disks' below for changes to take effect". 4. Put following command into qemu monitor: "(qemu) pci_add auto storage file=/tmp/disk2,if=scsi" 5. Click on "Rescan Disks" and then click on "OK". Actual results: After clicking on "OK", you are redirected to "INSTALLATION DESTINATION" spoke. In this spoke you can see only one disk, newly inserted disk isn't here. When you switch to shell, command "ls /dev/sd*" prints: "/dev/sda /dev/sdb". You can also see that kernel recognized new inserted disk from output of dmesg. Expected results: Anaconda should recognize additionally inserted disk and show this disk in "INSTALLATION DESTINATION" spoke. Additional info:
Created attachment 718124 [details] output of dmesg
Created attachment 718125 [details] anaconda.log
Created attachment 718126 [details] program.log
Created attachment 718127 [details] storage.log
Created attachment 718128 [details] packaging.log
anaconda-19.24-1.fc19, python-blivet-0.12-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/python-blivet-0.12-1.fc19,anaconda-19.24-1.fc19
Package anaconda-19.24-1.fc19, python-blivet-0.12-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.24-1.fc19 python-blivet-0.12-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-7403/python-blivet-0.12-1.fc19,anaconda-19.24-1.fc19 then log in and leave karma (feedback).
I retested this issue on anaconda 19.24-1 and the problem described in this bug is still present, moving to assigned.
I'll take this back. It looks like there's a lot of stuff going wrong here, but the bulk of it appears to be in anaconda.
anaconda-19.30-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/anaconda-19.30-1.fc19
Package anaconda-19.30-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.30-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-8871/anaconda-19.30-1.fc19 then log in and leave karma (feedback).
anaconda-19.30-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.