Bug 874562 - Anaconda doesn't tell what is wrong on partitioning
Summary: Anaconda doesn't tell what is wrong on partitioning
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F18Blocker, F18FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2012-11-08 13:06 UTC by Pavel Holica
Modified: 2013-03-12 14:27 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-08 16:15:10 UTC


Attachments (Terms of Use)
Error checking storage configuration screenshot (65.41 KB, image/png)
2012-11-08 13:06 UTC, Pavel Holica
no flags Details
anaconda.log (13.90 KB, text/plain)
2012-11-08 13:22 UTC, Pavel Holica
no flags Details
program.log (31.85 KB, text/plain)
2012-11-08 13:23 UTC, Pavel Holica
no flags Details
storage.log (105.62 KB, text/plain)
2012-11-08 13:23 UTC, Pavel Holica
no flags Details

Description Pavel Holica 2012-11-08 13:06:25 UTC
Created attachment 640794 [details]
Error checking storage configuration screenshot

Description of problem:
When incorrect partitioning is specified, anaconda allows to click on "Finish partitioning" and doesn't complain about anything. Then, in hub, there is only information "Error checking storage configuration" which doesn't tell what is wrong and can be confusing.

Version-Release number of selected component (if applicable):
anaconda-18.24-1.fc18

How reproducible:
always

Steps to Reproduce:
1. Get to partitioning and do manual configuration
2. Set / to be "vfat" for example
3. click on "Finish partitioning"
  
Actual results:
see attachment

Expected results:
Anaconda should tell (like on Fedora 17 did) what is wrong with the partitioning layout.

Additional info:

Comment 1 Pavel Holica 2012-11-08 13:22:51 UTC
Created attachment 640806 [details]
anaconda.log

Comment 2 Pavel Holica 2012-11-08 13:23:14 UTC
Created attachment 640807 [details]
program.log

Comment 3 Pavel Holica 2012-11-08 13:23:37 UTC
Created attachment 640808 [details]
storage.log

Comment 4 Chris Lumens 2012-11-08 16:15:10 UTC
Yeah, this is just a difference in the new installer design.  You'll need to revisit the storage spoke and then it should be fairly obvious what the problem is.

We are trying to prevent people from getting locked into spokes, and to allow people to do other stuff while checks are running.  That's why you are sent back to the hub while storage sanity check runs, and why you have to go back into the spoke to see the detailed errors later.


Note You need to log in before you can comment on or make changes to this bug.