Bug 1306745

Summary: blivet.errors.DeviceTreeError: no slaves found for device fedora-swap
Product: [Fedora] Fedora Reporter: Gabriel Magalhaes <gabrielgmsm>
Component: python-blivetAssignee: Blivet Maintenance Team <blivet-maint-list>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: anaconda-maint-list, blivet-maint-list, gabrielgmsm, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:e5ae223f5b50c9676a676dfc20a4799fe143a3f4edf01574e7150c90e46c7cb0;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 18:38:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: anaconda-tb
none
File: anaconda.log
none
File: environ
none
File: journalctl
none
File: lsblk_output
none
File: nmcli_dev_list
none
File: os_info
none
File: program.log
none
File: storage.log
none
File: ifcfg.log none

Description Gabriel Magalhaes 2016-02-11 17:26:19 UTC
Description of problem:
When clicking on "Install to Hard Drive" with fedora 23 live running on usb.

Version-Release number of selected component:
anaconda-core-23.19.10-1.fc23.x86_64

The following was filed automatically by anaconda:
anaconda 23.19.10-1 exception report
Traceback (most recent call first):
  File "/usr/lib/python3.4/site-packages/blivet/populator.py", line 246, in _addSlaveDevices
    raise DeviceTreeError("no slaves found for device %s" % name)
  File "/usr/lib/python3.4/site-packages/blivet/populator.py", line 290, in addUdevLVDevice
    self._addSlaveDevices(info)
  File "/usr/lib/python3.4/site-packages/blivet/populator.py", line 712, in addUdevDevice
    device = self.addUdevLVDevice(info)
  File "/usr/lib/python3.4/site-packages/blivet/populator.py", line 1692, in _populate
    self.addUdevDevice(dev)
  File "/usr/lib/python3.4/site-packages/blivet/populator.py", line 1623, in populate
    self._populate()
  File "/usr/lib/python3.4/site-packages/blivet/devicetree.py", line 554, in populate
    self._populator.populate(cleanupOnly=cleanupOnly)
  File "/usr/lib/python3.4/site-packages/blivet/blivet.py", line 279, in reset
    self.devicetree.populate(cleanupOnly=cleanupOnly)
  File "/usr/lib/python3.4/site-packages/blivet/osinstall.py", line 1157, in storageInitialize
    storage.reset()
  File "/usr/lib64/python3.4/threading.py", line 868, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib64/python3.4/site-packages/pyanaconda/threads.py", line 253, in run
    threading.Thread.run(self, *args, **kwargs)
  File "/usr/lib64/python3.4/site-packages/pyanaconda/threads.py", line 171, in raise_if_error
    raise exc_info[0](exc_info[1]).with_traceback(exc_info[2])
  File "/usr/lib64/python3.4/site-packages/pyanaconda/threads.py", line 116, in wait
    self.raise_if_error(name)
  File "/usr/lib64/python3.4/site-packages/pyanaconda/timezone.py", line 76, in time_initialize
    threadMgr.wait(THREAD_STORAGE)
  File "/usr/lib64/python3.4/threading.py", line 868, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib64/python3.4/site-packages/pyanaconda/threads.py", line 253, in run
    threading.Thread.run(self, *args, **kwargs)
blivet.errors.DeviceTreeError: no slaves found for device fedora-swap

Additional info:
cmdline:        /usr/bin/python3  /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base
cmdline_file:   BOOT_IMAGE=/isolinux/vmlinuz0 root=live:LABEL=Fedora-Live-WS-x86_64-23-10 ro rd.live.image quiet rhgb
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         4.2.3-300.fc23.x86_64
other involved packages: python3-blivet-1.12.8-1.fc23.noarch, python3-libs-3.4.3-5.fc23.x86_64
product:        Fedora
release:        Fedora release 23 (Twenty Three)
type:           anaconda
version:        23

Comment 1 Gabriel Magalhaes 2016-02-11 17:26:26 UTC
Created attachment 1123223 [details]
File: anaconda-tb

Comment 2 Gabriel Magalhaes 2016-02-11 17:26:27 UTC
Created attachment 1123224 [details]
File: anaconda.log

Comment 3 Gabriel Magalhaes 2016-02-11 17:26:32 UTC
Created attachment 1123225 [details]
File: environ

Comment 4 Gabriel Magalhaes 2016-02-11 17:26:35 UTC
Created attachment 1123226 [details]
File: journalctl

Comment 5 Gabriel Magalhaes 2016-02-11 17:26:37 UTC
Created attachment 1123227 [details]
File: lsblk_output

Comment 6 Gabriel Magalhaes 2016-02-11 17:26:38 UTC
Created attachment 1123228 [details]
File: nmcli_dev_list

Comment 7 Gabriel Magalhaes 2016-02-11 17:26:40 UTC
Created attachment 1123229 [details]
File: os_info

Comment 8 Gabriel Magalhaes 2016-02-11 17:26:42 UTC
Created attachment 1123230 [details]
File: program.log

Comment 9 Gabriel Magalhaes 2016-02-11 17:26:44 UTC
Created attachment 1123231 [details]
File: storage.log

Comment 10 Gabriel Magalhaes 2016-02-11 17:26:46 UTC
Created attachment 1123232 [details]
File: ifcfg.log

Comment 11 Gabriel Magalhaes 2016-03-09 21:06:52 UTC
I already used fedora 20 on this PC. At the time, I had no other OS. This time, I first removed the fedora 20 I had, then installed Windows, partioning memory with their installer application. When I try to install fedora it does not even pass the first phase, raising this error. I already tried to reinstall fedora 20 but it doesn't pass this step either.

Comment 12 Gabriel Magalhaes 2016-04-11 18:11:00 UTC
(In reply to Gabriel Magalhaes from comment #11)
> I already used fedora 20 on this PC. At the time, I had no other OS. This
> time, I first removed the fedora 20 I had, then installed Windows,
> partioning memory with their installer application. When I try to install
> fedora it does not even pass the first phase, raising this error. I already
> tried to reinstall fedora 20 but it doesn't pass this step either.

Please help! I need to find a way to install Fedora... I am available to provide more information if necessary. Thank you for your help.

Comment 13 David Lehman 2016-04-11 18:43:35 UTC
It looks like you have some old, probably corrupted data on Volume0, which is a bios/firmware RAID array. I think there is some LVM metadata on there that is confusing the system. If you don't want to preserve any of the existing data on Volume0 (your local drives), I can help you to properly clear the old data from it. If you do want to preserve your existing data I am less sure of how to proceed. So, do you want to keep any of your existing data?

Comment 14 Gabriel Magalhaes 2016-04-11 19:41:11 UTC
(In reply to David Lehman from comment #13)
> It looks like you have some old, probably corrupted data on Volume0, which
> is a bios/firmware RAID array. I think there is some LVM metadata on there
> that is confusing the system. If you don't want to preserve any of the
> existing data on Volume0 (your local drives), I can help you to properly
> clear the old data from it. If you do want to preserve your existing data I
> am less sure of how to proceed. So, do you want to keep any of your existing
> data?

I can clear the data, I will backup my files and try dualbooting with Windows later. 

What is the best way to do it?

Comment 15 David Lehman 2016-04-11 19:48:57 UTC
I think you could move forward after just removing the LVM metadata, which you can do with these commands (as root):

  vgremove fedora
  wipefs -a /dev/md126p3

Comment 16 Fedora End Of Life 2016-11-24 15:30:54 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 17 Fedora End Of Life 2016-12-20 18:38:33 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.