Bug 1382528 - installer can't tell me how it intends to partition
Summary: installer can't tell me how it intends to partition
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 24
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-07 00:09 UTC by skierpage
Modified: 2017-08-08 19:20 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 19:20:47 UTC
Type: Bug


Attachments (Terms of Use)

Description skierpage 2016-10-07 00:09:36 UTC
Description of problem:
I installed a live F24 KDE spin on my Windows laptop, my first time installing Fedora in years (but I've installed Ubuntu/Kubuntu many times).

The installer is generally great until it came to partitioning. My choice was to let it do it or partition myself. I have my preferences as how to install (separate swap, use volume manager) but I'm not sure how to relate that to Fedora's features.

The problem is there is no easy way to find out how Fedora intends to partition your computer. 


Version-Release number of selected component (if applicable): anaconda 24.13.7.1


How reproducible:
Every time, I assume.

Steps to Reproduce:
1. From live USB run Fedora installer.
2. Get to Install Destination.
3. Let Fedora choose "Automatically configure partitioning"
4. Try to find out what it's going to do

Actual results:
You can't. The link _Full disk summary and boot loader_ just gives the disk description of the boot device. After completion all the summary screen says is "Automatic partitioning selected"

Expected results:
The Installation Summary should display or link to a summary of how it intends to partition.
When choosing to partition myself, there should be a way to get the installer to suggest or fill in how it would partition if I let it.


Additional info:
This was with the F24-x86_64-KDE-20160823 live spin.
There are some hints as to how anaconda intends to partition in /tmp/storage.log, lines like "blivet: Adding fedora-swap;2 GiB to fedora"... "create lvmlv fedora-swap", but it's hard to interpret.

Comment 1 Fedora End Of Life 2017-07-25 23:23:05 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 EOL if it remains open with a Fedora  'version'
of '24'.

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.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 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 this bug is closed as described in the policy above.

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 2 Fedora End Of Life 2017-08-08 19:20:47 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.