Bug 1062909 - DeviceTreeError: could not find parent for subvol
Summary: DeviceTreeError: could not find parent for subvol
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1a7c7e087bc5817abb40a840b72...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-08 14:05 UTC by tomz
Modified: 2015-06-29 15:05 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 15:05:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: anaconda-tb (226.43 KB, text/plain)
2014-02-08 14:05 UTC, tomz
no flags Details
File: anaconda.log (14.84 KB, text/plain)
2014-02-08 14:05 UTC, tomz
no flags Details
File: environ (394 bytes, text/plain)
2014-02-08 14:05 UTC, tomz
no flags Details
File: lsblk_output (7.19 KB, text/plain)
2014-02-08 14:05 UTC, tomz
no flags Details
File: nmcli_dev_list (8.02 KB, text/plain)
2014-02-08 14:05 UTC, tomz
no flags Details
File: os_info (375 bytes, text/plain)
2014-02-08 14:05 UTC, tomz
no flags Details
File: program.log (22.47 KB, text/plain)
2014-02-08 14:05 UTC, tomz
no flags Details
File: storage.log (28.09 KB, text/plain)
2014-02-08 14:05 UTC, tomz
no flags Details
File: syslog (129.55 KB, text/plain)
2014-02-08 14:05 UTC, tomz
no flags Details
File: ifcfg.log (3.71 KB, text/plain)
2014-02-08 14:06 UTC, tomz
no flags Details
output from btrfs (4.34 KB, text/plain)
2014-02-08 14:23 UTC, tomz
no flags Details

Description tomz 2014-02-08 14:05:38 UTC
Description of problem:


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

The following was filed automatically by anaconda:
anaconda 20.25.15-1 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1610, in handleBTRFSFormat
    raise DeviceTreeError("could not find parent for subvol")
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1735, in handleUdevDeviceFormat
    self.handleBTRFSFormat(info, device)
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1075, in addUdevDevice
    self.handleUdevDeviceFormat(info, device)
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1962, in _populate
    self.addUdevDevice(dev)
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1906, in populate
    self._populate()
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 416, in reset
    self.devicetree.populate(cleanupOnly=cleanupOnly)
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 142, in storageInitialize
    storage.reset()
  File "/usr/lib64/python2.7/threading.py", line 764, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 192, in run
    threading.Thread.run(self, *args, **kwargs)
DeviceTreeError: could not find parent for subvol

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2020\x20x86_64 quiet BOOT_IMAGE=vmlinuz text net.ifnames=0
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.11.10-301.fc20.x86_64
product:        Fedora
release:        Cannot get release name.
type:           anaconda
version:        20

Comment 1 tomz 2014-02-08 14:05:42 UTC
Created attachment 860884 [details]
File: anaconda-tb

Comment 2 tomz 2014-02-08 14:05:44 UTC
Created attachment 860885 [details]
File: anaconda.log

Comment 3 tomz 2014-02-08 14:05:46 UTC
Created attachment 860886 [details]
File: environ

Comment 4 tomz 2014-02-08 14:05:48 UTC
Created attachment 860887 [details]
File: lsblk_output

Comment 5 tomz 2014-02-08 14:05:50 UTC
Created attachment 860888 [details]
File: nmcli_dev_list

Comment 6 tomz 2014-02-08 14:05:52 UTC
Created attachment 860889 [details]
File: os_info

Comment 7 tomz 2014-02-08 14:05:54 UTC
Created attachment 860890 [details]
File: program.log

Comment 8 tomz 2014-02-08 14:05:57 UTC
Created attachment 860891 [details]
File: storage.log

Comment 9 tomz 2014-02-08 14:05:59 UTC
Created attachment 860892 [details]
File: syslog

Comment 10 tomz 2014-02-08 14:06:01 UTC
Created attachment 860893 [details]
File: ifcfg.log

Comment 11 tomz 2014-02-08 14:22:57 UTC
On the system already exists subvolumes used/created by openSUSE installer.
See the attached file (btrfs_output.txt)

Comment 12 tomz 2014-02-08 14:23:56 UTC
Created attachment 860895 [details]
output from btrfs

Comment 13 Fedora End Of Life 2015-05-29 10:51:17 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 14 Fedora End Of Life 2015-06-29 15:05:13 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.