Bug 889093 - user selection in Configure Mount Point is ignored until more than one mount point is specified
Summary: user selection in Configure Mount Point is ignored until more than one mount ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Lehman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-20 08:16 UTC by Chris Murphy
Modified: 2014-02-05 14:04 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 14:04:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
anaconda.log (8.21 KB, text/plain)
2012-12-20 08:21 UTC, Chris Murphy
no flags Details
program.log (42.93 KB, text/plain)
2012-12-20 08:21 UTC, Chris Murphy
no flags Details
storage.log (108.02 KB, text/plain)
2012-12-20 08:22 UTC, Chris Murphy
no flags Details
storage.state (20.00 KB, text/plain)
2012-12-20 08:23 UTC, Chris Murphy
no flags Details

Description Chris Murphy 2012-12-20 08:16:49 UTC
Description of problem:
Manual Partitioning > Congiure Mount Point modal dialog selection is ignored/has no effect until a 2nd mount point is specified. (This is a UI feedback bug.)

Version-Release number of selected component (if applicable):
Fedora-18-TC3-x86_64-Live-Desktop.iso as base with
anaconda-18.37.4-1


How reproducible:
100% in qemu-kvm

Steps to Reproduce:
1. Two identically sized virtual disks.
2. Go directly to custom/Manual Partitioning.
3. Add a mount point (any) with a size smaller than single disk size.
4. Click on customize options, set device type to Standard Partition
5. Click on the configure icon (to the right of + - buttons for adding/removing partitions), to go to Configure Mount Point.

Cosmetic bug: Both disks in this dialog are selected in blue.

6. Click on the disk with the same capacity and free values, then click the select button.

  
Actual results:
The Name: field for this mount point is unchanged, it still says sda1 regardless of which disk I select in Configure Mount Point.

In Configure Mount Point, only the first disk has different capacity/free space, regardless of which disk is selected.


Expected results:
The disk I choose is the one that the partition should be created on. And the Name: field should reflect this. And the Configure Mount Point dialog capacity vs free space should reflect usage changes on the selected disk.


Additional info:

Once one more mount point is specified (at least two specified), Configure Mount Point appears to function mostly as expected. The

Comment 1 Chris Murphy 2012-12-20 08:21:00 UTC
Created attachment 666536 [details]
anaconda.log

Comment 2 Chris Murphy 2012-12-20 08:21:47 UTC
Created attachment 666537 [details]
program.log

Comment 3 Chris Murphy 2012-12-20 08:22:54 UTC
Created attachment 666539 [details]
storage.log

Comment 4 Chris Murphy 2012-12-20 08:23:24 UTC
Created attachment 666540 [details]
storage.state

Comment 5 Chris Lumens 2013-02-07 21:49:07 UTC
Both disks are specified in blue on the configure dialog because both disks are available for the mountpoint to reside on.  If you selected both of your disks on the initial storage spoke, you've not given anaconda any constraints as to where the mountpoint may live.  Thus, both are available and both are in blue.

Then the rest of the bug report looks like we just need to make sure to update the name field when that dialog exits.  It will also be updated if you click "Apply Changes", just like other widgets on this screen though.

Comment 6 Fedora End Of Life 2013-12-21 10:00:30 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Fedora End Of Life 2014-02-05 14:04:17 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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