Red Hat Bugzilla – Bug 978016
Anaconda cannot reset the storage back to the initial state after reclaiming space
Last modified: 2015-01-09 15:40:42 EST
Created attachment 765266 [details]
Video of problem
Description of problem:
When you are installing over a previously installed system and you reclaim disk space, you cannot undo the reclamation.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Click Installation Destination.
2. Select the hard drive(s) to install on.
3. Click Reclaim Space.
4. Delete the entire disk(s).
5. There is no way to view the original partition information and reuse it.
The "reset all" button should reset to the original information.
Created attachment 765267 [details]
Created attachment 765268 [details]
Proposing as a CommonBug. The only known workaround is to reboot.
There is a little button down by the + and - buttons that actually rescans storage from disk. You can use that.
Interesting. Yes, that does work. So the "Reset All" button is to undo temporary changes made? Will this be documented correctly in the install guide?
"So the "Reset All" button is to undo temporary changes made?"
Yes, that's what it does. Those two could probably stand to be a bit better explained.
dropping commonbugs as this isn't a bug; adding documentation keyword, docs team, can you check the install guide and see if the function of each of those buttons is clearly explained? "Reset All" just 'undoes' all your planned partitioning operations and reverts to the state when you first entered the custom partitioning screen; the "rescan" button actually goes out and re-scans all the storage devices on the system, so you can make some changes with fdisk or gparted or whatever on the ctrl-alt-f2 console and then use the 'rescan' button to pick them up (new in F19, IIRC).
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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.
I think it's best to resolve this as NOTABUG, and if someone has a clear UI improvement suggestion, that can be filed separately.