Bug 965623 - Unable to create another new volume group when the first one is full
Summary: Unable to create another new volume group when the first one is full
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Lehman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: newui-container
: 965817 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-21 12:23 UTC by Lukas "krteknet" Novy
Modified: 2016-07-19 10:13 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 10:13:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Error message screenshot (103.41 KB, image/png)
2013-05-21 12:23 UTC, Lukas "krteknet" Novy
no flags Details
anaconda.log (29.29 KB, text/plain)
2013-05-22 01:19 UTC, Adam Williamson
no flags Details
program.log (28.05 KB, text/plain)
2013-05-22 01:19 UTC, Adam Williamson
no flags Details
storage.log (226.32 KB, text/plain)
2013-05-22 01:20 UTC, Adam Williamson
no flags Details
storage.state (20.00 KB, text/plain)
2013-05-22 01:20 UTC, Adam Williamson
no flags Details
storage.log from reproduction with 2015-01-05 Rawhide (227.88 KB, text/plain)
2015-01-09 20:05 UTC, Adam Williamson
no flags Details
program.log from reproduction with 2015-01-05 Rawhide (34.82 KB, text/plain)
2015-01-09 20:07 UTC, Adam Williamson
no flags Details
anaconda.log from reproduction with 2015-01-05 Rawhide (24.74 KB, text/plain)
2015-01-09 20:07 UTC, Adam Williamson
no flags Details

Description Lukas "krteknet" Novy 2013-05-21 12:23:43 UTC
Created attachment 751096 [details]
Error message screenshot

Description of problem:
Trying to create another volume group when every other is full fails with "failed to create device"

Version-Release number of selected component (if applicable):
Anaconda usability test day livedvd.

How reproducible:
Always

Steps to Reproduce:
1. Start graphical installation in virtual machine with four disks (8GB each)
2. Select all four disk for installation, manually edit partitions
3. Modify / mountpoint's Volume Group "fedora" and only select the first disk
3a. / mountpoint should now have 6.10 GB allocated
4. Try to add another mountpoint eg. /var

Actual results:
failed to create device

Expected results:
Anaconda ask to create another volume group on another disk

Additional info:
Workaround: move / mountpoint to another created volume group first and than create mountpoint

Comment 1 Adam Williamson 2013-05-21 19:49:36 UTC
*** Bug 965817 has been marked as a duplicate of this bug. ***

Comment 2 Adam Williamson 2013-05-21 19:50:24 UTC
I wrote a slightly more detailed explanation in the dupe, FWIW.

Comment 3 Brian Lane 2013-05-22 00:47:16 UTC
Please attach logs from /tmp/*log as individual text/plain files, especially storage.log

Comment 4 Adam Williamson 2013-05-22 01:13:34 UTC
yeesh, it's perfectly obvious what's going on. I explained it in the dupe. But sure, let me jump through some hoops for you, it's not like I have anything else going on.

Comment 5 Adam Williamson 2013-05-22 01:17:48 UTC
Note: if you try to create the new mount point with no specified size, there is no error, but the mount point is not created. If you specify any size at all, you get a red "Failed to add new device. Click for details." error bar, and clicking on pops up a dialog which simply says "failed to create device" with a Close button.

Comment 6 Adam Williamson 2013-05-22 01:19:07 UTC
Created attachment 751450 [details]
anaconda.log

Comment 7 Adam Williamson 2013-05-22 01:19:36 UTC
Created attachment 751451 [details]
program.log

Comment 8 Adam Williamson 2013-05-22 01:20:08 UTC
Created attachment 751452 [details]
storage.log

Comment 9 Adam Williamson 2013-05-22 01:20:36 UTC
Created attachment 751454 [details]
storage.state

Comment 11 Fedora End Of Life 2015-01-09 18:10:54 UTC
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.

Comment 12 Adam Williamson 2015-01-09 20:04:39 UTC
This is still valid, exactly as per my reproduction steps in the dupe - https://bugzilla.redhat.com/show_bug.cgi?id=965817#c0 - in current Rawhide (2015-01-05).

Comment 13 Adam Williamson 2015-01-09 20:05:59 UTC
Created attachment 978378 [details]
storage.log from reproduction with 2015-01-05 Rawhide

Comment 14 Adam Williamson 2015-01-09 20:07:23 UTC
Created attachment 978379 [details]
program.log from reproduction with 2015-01-05 Rawhide

Comment 15 Adam Williamson 2015-01-09 20:07:57 UTC
Created attachment 978380 [details]
anaconda.log from reproduction with 2015-01-05 Rawhide

Comment 16 Jaroslav Reznik 2015-03-03 14:57:00 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 17 Fedora End Of Life 2016-07-19 10:13:23 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.