Bug 1661712

Summary: gi.overrides.BlockDev.DMError: Failed to activate the RAID set 'pdc_bbddhheifc-0'
Product: [Fedora] Fedora Reporter: James <james>
Component: libblockdevAssignee: Vojtech Trefny <vtrefny>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: anaconda-maint-list, atl.jd.williams, jonathan, kellin, sbueno, vanmeeuwen+fedora, v.podzimek+fedora, vponcova, vtrefny, wwoods
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:2d1c36b945af1a14824cb7bef5b56576a07d46f838cea2b84452ff14ed4a7009;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-15 14:24: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:
Embargoed:
Attachments:
Description Flags
File: anaconda-tb
none
File: anaconda.log
none
File: dbus.log
none
File: dnf.librepo.log
none
File: environ
none
File: lorax-packages.log
none
File: lsblk_output
none
File: nmcli_dev_list
none
File: os_info
none
File: program.log
none
File: storage.log
none
File: syslog
none
File: ifcfg.log
none
File: packaging.log none

Description James 2018-12-22 14:46:23 UTC
Description of problem:
Attempted to install F29 Server netinstall on machine with existing RAIDed discs.

Version-Release number of selected component:
anaconda-29.24.7

The following was filed automatically by anaconda:
anaconda 29.24.7 exception report
Traceback (most recent call first):
  File "/usr/lib64/python3.7/site-packages/gi/overrides/BlockDev.py", line 993, in wrapped
    raise transform[1](msg)
  File "/usr/lib/python3.7/site-packages/blivet/populator/helpers/dmraid.py", line 69, in run
    blockdev.dm.activate_raid_set(rs_name)
  File "/usr/lib/python3.7/site-packages/blivet/populator/populator.py", line 304, in handle_format
    helper_class(self, info, device).run()
  File "/usr/lib/python3.7/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.7/site-packages/blivet/populator/populator.py", line 276, in handle_device
    self.handle_format(info, device)
  File "/usr/lib/python3.7/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.7/site-packages/blivet/populator/populator.py", line 461, in _populate
    self.handle_device(dev)
  File "/usr/lib/python3.7/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.7/site-packages/blivet/populator/populator.py", line 413, in populate
    self._populate()
  File "/usr/lib/python3.7/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.7/site-packages/blivet/blivet.py", line 161, in reset
    self.devicetree.populate(cleanup_only=cleanup_only)
  File "/usr/lib/python3.7/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib64/python3.7/site-packages/pyanaconda/storage/osinstall.py", line 1738, in reset
    super().reset(cleanup_only=cleanup_only)
  File "/usr/lib/python3.7/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib64/python3.7/site-packages/pyanaconda/storage/osinstall.py", line 2298, in storage_initialize
    storage.reset()
  File "/usr/lib64/python3.7/threading.py", line 865, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib64/python3.7/site-packages/pyanaconda/threading.py", line 286, in run
    threading.Thread.run(self)
gi.overrides.BlockDev.DMError: Failed to activate the RAID set 'pdc_bbddhheifc-0'

Additional info:
addons:         com_redhat_docker, com_redhat_kdump
cmdline:        /usr/bin/python3  /sbin/anaconda
cmdline_file:   BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-29 quiet
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         4.18.16-300.fc29.x86_64
product:        Fedora
release:        Cannot get release name.
type:           anaconda
version:        29

Potential duplicate: bug 1631228

Comment 1 James 2018-12-22 14:46:33 UTC
Created attachment 1516243 [details]
File: anaconda-tb

Comment 2 James 2018-12-22 14:46:35 UTC
Created attachment 1516244 [details]
File: anaconda.log

Comment 3 James 2018-12-22 14:46:37 UTC
Created attachment 1516245 [details]
File: dbus.log

Comment 4 James 2018-12-22 14:46:42 UTC
Created attachment 1516246 [details]
File: dnf.librepo.log

Comment 5 James 2018-12-22 14:46:43 UTC
Created attachment 1516247 [details]
File: environ

Comment 6 James 2018-12-22 14:46:45 UTC
Created attachment 1516248 [details]
File: lorax-packages.log

Comment 7 James 2018-12-22 14:46:46 UTC
Created attachment 1516249 [details]
File: lsblk_output

Comment 8 James 2018-12-22 14:46:47 UTC
Created attachment 1516250 [details]
File: nmcli_dev_list

Comment 9 James 2018-12-22 14:46:48 UTC
Created attachment 1516251 [details]
File: os_info

Comment 10 James 2018-12-22 14:46:50 UTC
Created attachment 1516252 [details]
File: program.log

Comment 11 James 2018-12-22 14:46:52 UTC
Created attachment 1516253 [details]
File: storage.log

Comment 12 James 2018-12-22 14:46:58 UTC
Created attachment 1516254 [details]
File: syslog

Comment 13 James 2018-12-22 14:46:59 UTC
Created attachment 1516255 [details]
File: ifcfg.log

Comment 14 James 2018-12-22 14:47:00 UTC
Created attachment 1516256 [details]
File: packaging.log

Comment 15 Vendula Poncova 2019-01-02 14:57:24 UTC
It seems to be an issue in the storage configuration library. Reassigning to libblockdev.

Comment 16 James 2019-01-02 16:20:27 UTC
I believe the drives concerned were in an invalid 'fake-RAID'-related state. Nonetheless, this shouldn't cause Anaconda to crash -- in fact I'd expect it to either say the drives are unavailable and not use them, or offer them up for a complete wiping.

Comment 17 Vratislav Podzimek 2019-01-04 08:23:03 UTC
*** Bug 1662568 has been marked as a duplicate of this bug. ***

Comment 18 Vojtech Trefny 2019-01-15 14:24:33 UTC

*** This bug has been marked as a duplicate of bug 1664634 ***