In F19 Beta TC3, if you go through the Installation Destination spoke and select guided partitioning (either 'go ahead and use the free space I have' or 'reclaim space') and complete it successfully, then on subsequent visits to the spoke, you don't see Installation Options again; you pick disks and hit Done and you're sent straight back to the hub. I don't think this is intended, I think Installation Options is supposed to come up again to let you modify your choices if you want to.
I think this is working like it is supposed to. We are locking out autopart unless you change something (disks selected, bootloader location). If you use custom you can repeat it multiple times. That feels pretty kludgy though, you really should be able to re-enter the spoke and change the autopart filesystem type for example.
Created attachment 745463 [details] Attempt to allow multiple passes at autopart Here's my unsuccessful attempt at fixing this so that you can repeat autopart. This patch looks like it works, but generates odd autopart layouts after multiple passes, switching between autopart and custom and back again. I think dlehman will need to look at it and see what else needs to be done.
A change was made that prevented anaconda from re-executing code if no changes were made in the UI compared to previous visits. Because some critical decisions are made in the dialogs, it is not possible to skip them when the user has not made any changes in the main storage spoke itself. Surprise! Storage is an exception to an otherwise reasonable UI rule.
anaconda-19.27-1.fc19, pykickstart-1.99.31-1.fc19, python-blivet-0.14-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/python-blivet-0.14-1.fc19,pykickstart-1.99.31-1.fc19,anaconda-19.27-1.fc19
Package anaconda-19.27-1.fc19, pykickstart-1.99.31-1.fc19, python-blivet-0.14-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.27-1.fc19 pykickstart-1.99.31-1.fc19 python-blivet-0.14-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-8322/python-blivet-0.14-1.fc19,pykickstart-1.99.31-1.fc19,anaconda-19.27-1.fc19 then log in and leave karma (feedback).
Package pykickstart-1.99.31-1.fc19, anaconda-19.28-1.fc19, python-blivet-0.14-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 pykickstart-1.99.31-1.fc19 anaconda-19.28-1.fc19 python-blivet-0.14-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-8322/python-blivet-0.14-1.fc19,pykickstart-1.99.31-1.fc19,anaconda-19.28-1.fc19 then log in and leave karma (feedback).
pykickstart-1.99.31-1.fc19, anaconda-19.28-1.fc19, python-blivet-0.14-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.