Bug 951765 - DeviceFactoryError: Cannot remove non-leaf device 'sda4'
Summary: DeviceFactoryError: Cannot remove non-leaf device 'sda4'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Lehman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:873218d15c2700fb5ba9a17723e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-13 03:46 UTC by Victor Costan
Modified: 2013-05-22 03:21 UTC (History)
6 users (show)

Fixed In Version: anaconda-19.24-1.fc19
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-22 03:21:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: anaconda-tb (866.71 KB, text/plain)
2013-04-13 03:46 UTC, Victor Costan
no flags Details
File: anaconda.log (49.43 KB, text/plain)
2013-04-13 03:46 UTC, Victor Costan
no flags Details
File: backtrace (634 bytes, text/plain)
2013-04-13 03:46 UTC, Victor Costan
no flags Details
File: environ (780 bytes, text/plain)
2013-04-13 03:46 UTC, Victor Costan
no flags Details
File: ifcfg.log (492 bytes, text/plain)
2013-04-13 03:46 UTC, Victor Costan
no flags Details
File: lsblk_output (1.89 KB, text/plain)
2013-04-13 03:46 UTC, Victor Costan
no flags Details
File: nmcli_dev_list (5.94 KB, text/plain)
2013-04-13 03:46 UTC, Victor Costan
no flags Details
File: packaging.log (326.64 KB, text/plain)
2013-04-13 03:46 UTC, Victor Costan
no flags Details
File: program.log (28.45 KB, text/plain)
2013-04-13 03:46 UTC, Victor Costan
no flags Details
File: storage.log (283.94 KB, text/plain)
2013-04-13 03:46 UTC, Victor Costan
no flags Details
File: syslog (134.81 KB, text/plain)
2013-04-13 03:46 UTC, Victor Costan
no flags Details

Description Victor Costan 2013-04-13 03:46:36 UTC
Description of problem:
Tried to switch a proposed partition scheme that used LVM to one that's not based on LVM, by changing the "device type" from "LVM" to "Standard partition" on each partition, one by one.
The following was filed automatically by anaconda:
anaconda 19.17-1 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.7/site-packages/blivet/devicefactory.py", line 668, in configure
    raise(e)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1823, in _destroy_device
    factory.configure()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1094, in _save_right_side
    self._destroy_device(device)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2432, in on_apply_clicked
    self._save_right_side(self._current_selector)
DeviceFactoryError: Cannot remove non-leaf device 'sda4'

Version-Release number of selected component:
anaconda-19.17-1

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2019-Alpha\x20x86_64 quiet BOOT_IMAGE=vmlinuz 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.9.0-0.rc4.git0.1.fc19.x86_64
product:        Fedora
release:        Cannot get release name.
type:           anaconda
version:        19-Alpha

Truncated backtrace:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2432, in on_apply_clicked
    self._save_right_side(self._current_selector)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1094, in _save_right_side
    self._destroy_device(device)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1823, in _destroy_device
    factory.configure()
  File "/usr/lib/python2.7/site-packages/blivet/devicefactory.py", line 668, in configure
    raise(e)
DeviceFactoryError: Cannot remove non-leaf device 'sda4'

Comment 1 Victor Costan 2013-04-13 03:46:40 UTC
Created attachment 735129 [details]
File: anaconda-tb

Comment 2 Victor Costan 2013-04-13 03:46:43 UTC
Created attachment 735130 [details]
File: anaconda.log

Comment 3 Victor Costan 2013-04-13 03:46:45 UTC
Created attachment 735131 [details]
File: backtrace

Comment 4 Victor Costan 2013-04-13 03:46:47 UTC
Created attachment 735132 [details]
File: environ

Comment 5 Victor Costan 2013-04-13 03:46:48 UTC
Created attachment 735133 [details]
File: ifcfg.log

Comment 6 Victor Costan 2013-04-13 03:46:50 UTC
Created attachment 735134 [details]
File: lsblk_output

Comment 7 Victor Costan 2013-04-13 03:46:51 UTC
Created attachment 735135 [details]
File: nmcli_dev_list

Comment 8 Victor Costan 2013-04-13 03:46:53 UTC
Created attachment 735136 [details]
File: packaging.log

Comment 9 Victor Costan 2013-04-13 03:46:55 UTC
Created attachment 735137 [details]
File: program.log

Comment 10 Victor Costan 2013-04-13 03:46:57 UTC
Created attachment 735138 [details]
File: storage.log

Comment 11 Victor Costan 2013-04-13 03:46:59 UTC
Created attachment 735139 [details]
File: syslog

Comment 12 David Lehman 2013-04-15 15:18:09 UTC
I tried the same procedure and it worked correctly. I'll take a look through your log files.

Comment 13 Victor Costan 2013-04-15 18:42:51 UTC
Please let me know if there's anything I can do to help!

Comment 14 David Lehman 2013-04-18 20:17:38 UTC
I hit this today. I was switching from an lvm autopart layout to btrfs by first switching root, then home, to btrfs, then swap to partition.

Comment 15 Fedora Update System 2013-05-03 23:04:45 UTC
anaconda-19.24-1.fc19, python-blivet-0.12-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/python-blivet-0.12-1.fc19,anaconda-19.24-1.fc19

Comment 16 Fedora Update System 2013-05-04 18:51:04 UTC
Package anaconda-19.24-1.fc19, python-blivet-0.12-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-19.24-1.fc19 python-blivet-0.12-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-7403/python-blivet-0.12-1.fc19,anaconda-19.24-1.fc19
then log in and leave karma (feedback).

Comment 17 Mark Hamzy 2013-05-13 20:28:30 UTC
Description of problem:
Went to the custom partition screen. Then deleted the previous install. Then selected automatic partitioning. Then edited each partition and changed it to RAID5.

Version-Release number of selected component:
anaconda-19.25-1

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   ro  inst.vnc
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.9.1-301.fc19.ppc64
product:        Fedora
release:        Cannot get release name.
type:           anaconda
version:        19

Truncated backtrace:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2711, in on_apply_clicked
    self._save_right_side(self._current_selector)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1283, in _save_right_side
    self._destroy_device(device)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2036, in _destroy_device
    factory.configure()
  File "/usr/lib/python2.7/site-packages/blivet/devicefactory.py", line 704, in configure
    raise(e)
DeviceFactoryError: Too many primary partitions.

Comment 18 David Lehman 2013-05-13 20:32:13 UTC
(In reply to comment #17)
> Description of problem:
> Went to the custom partition screen. Then deleted the previous install. Then
> selected automatic partitioning. Then edited each partition and changed it
> to RAID5.
> 
...
> DeviceFactoryError: Too many primary partitions.

This is a new/different traceback. Please file a separate bug with log files. Thanks.

Comment 19 Fedora Update System 2013-05-22 03:21:53 UTC
anaconda-19.24-1.fc19, python-blivet-0.12-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.


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