Description of problem: Currently, in manual partitioning, anaconda let's the user start the installation process by just creating 1mb / partition. This leads to a freeze of the whole installation environment. By 'complete' i mean that not even switching to another vt works, either xorg or the kernel are frozen. Version-Release number of selected component (if applicable): F18b TC6 How reproducible: always Steps to Reproduce: 1. go to storage, select one disk, remove all partitions 2. create a 0mb / partition, it will be rounded to 1mb :-) 3. press finish partitioning and return to the main hub 4. start installation. 5. the environment will freeze, switching to another VT will not work, complete freeze. Actual results: frozen installation environment (complete) (anaconda/xorg/kernel) Expected results: an error message, since the intended action does not make sense. the / partition is so small than not even the kernel would fit in it. :-) Additional info: when doing this with multiple selected disk, the 1mb partition might be created on the second or other disk.
tested with: 20121205_f18-smoke4 (netinstall) 1. Go to STORAGE: INSTALLATION DESTINATION, select one disk. 2. Select 'I don't need...' for AUTOMATIC PARTITIONING. 3. Remove all partitions shown in manual partitioning. 4. Create a 0mb / partition, it will be rounded to 1mb :-) 5. Press 'Finish Partitioning' and return to the main hub. It is no longer possible to start installing. That is OK!. "Error checking storage configuration" message is shown, which is ok. I tried 2 different guest without this issue. So, it appears that the bug-report can be closed.
Created attachment 672404 [details] screenshot that shows that STORAGE: INSTALLATION DESTINATION is not "alarmed" With F18 TC4 (18.37.8) anaconda no longer appears to reject the storage configuration, because STORAGE: INSTALLATION DESTINATION is not alarmed. Good: * It is still not possible to start installing * A yellow banner in the main hub print an error that suggest an incorrect partitioning choice done by the user. Bad: * STORAGE: INSTALLATION DESTINATION is not alarmed. (no exclamation mark)
Created attachment 672405 [details] storage.log
(In reply to comment #2) > Good: > * It is still not possible to start installing > * A yellow banner in the main hub print an error that suggest an incorrect > partitioning choice done by the user. > > Bad: > * STORAGE: INSTALLATION DESTINATION is not alarmed. (no exclamation mark) This is intentional. It could be considered a storage error or a software selection error. Treating it as one or both becomes very complicated, so we decided to use only an error notification on the main hub.
This is clearly resolved now, closing.