Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Anaconda doesn't remember user choice of where to put the partitions. Version-Release number of selected component (if applicable): anaconda-18-24.1.fc18 Fedora-18-Beta-TC7 How reproducible: always Steps to Reproduce: 1. On system with 3 disks (10G, 15G, 15G), start Fedora-Beta-TC7 installation 2. Proceed to main hub, choose partitioning 3. Choose all disks 4. Click on let me customize disks instead and select "plain" for partitioning scheme 5. Delete all the partitions 6. Create 500MB /boot partition 7. Click on 2 wheels to select where to put the /boot partition, select only first 10GB disk, click on "Apply changes" 8. Click again on 2 wheels to select where to put the /boot partition Actual results: Anaconda doesn't remember where user previously selected the partition to be placed Expected results: Anaconda should show correct partition after user selects one. Additional info:
Created attachment 639901 [details] anaconda.log
Created attachment 639902 [details] program.log
Created attachment 639903 [details] step6.png
Created attachment 639904 [details] step7.png
Created attachment 639905 [details] step8.png
Created attachment 639906 [details] step9.png
Created attachment 639907 [details] storage.log
Created attachment 639908 [details] storage.state
Created attachment 639909 [details] syslog
anaconda-18.28-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2012-17823/anaconda-18.28-1.fc18
Package anaconda-18.28-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.28-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-17823/anaconda-18.28-1.fc18 then log in and leave karma (feedback).
Martin: can you re-test with Beta RC1 and confirm? Thanks!
Verified on anaconda-18.29.2-1, this error no longer occurs and anaconda remembers correctly where the partitions should be.