Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1158968 - AttributeError: 'DMRaidArrayDevice' object has no attribute 'formatClass'
Summary: AttributeError: 'DMRaidArrayDevice' object has no attribute 'formatClass'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-blivet
Version: 21
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: David Lehman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3de694caf443ae2f3e58fc7f651...
: 1159625 1161728 1167000 (view as bug list)
Depends On:
Blocks: F21FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2014-10-30 15:27 UTC by Richard S. Hendershot
Modified: 2014-12-08 20:51 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-18 15:04:26 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: anaconda-tb (139.38 KB, text/plain)
2014-10-30 15:27 UTC, Richard S. Hendershot 		no flags Details
File: anaconda.log (10.54 KB, text/plain)
2014-10-30 15:27 UTC, Richard S. Hendershot 		no flags Details
File: environ (459 bytes, text/plain)
2014-10-30 15:27 UTC, Richard S. Hendershot 		no flags Details
File: lsblk_output (5.69 KB, text/plain)
2014-10-30 15:27 UTC, Richard S. Hendershot 		no flags Details
File: nmcli_dev_list (1.10 KB, text/plain)
2014-10-30 15:27 UTC, Richard S. Hendershot 		no flags Details
File: os_info (377 bytes, text/plain)
2014-10-30 15:27 UTC, Richard S. Hendershot 		no flags Details
File: program.log (7.90 KB, text/plain)
2014-10-30 15:27 UTC, Richard S. Hendershot 		no flags Details
File: storage.log (7.14 KB, text/plain)
2014-10-30 15:27 UTC, Richard S. Hendershot 		no flags Details
File: syslog (98.52 KB, text/plain)
2014-10-30 15:27 UTC, Richard S. Hendershot 		no flags Details
File: ifcfg.log (1.76 KB, text/plain)
2014-10-30 15:27 UTC, Richard S. Hendershot 		no flags Details
File: packaging.log (1.29 KB, text/plain)
2014-10-30 15:27 UTC, Richard S. Hendershot 		no flags Details
anaconda.log (33.54 KB, text/plain)
2014-12-08 20:32 UTC, Jyrki Soini 		no flags Details
journalctl log (432.21 KB, text/x-vhdl)
2014-12-08 20:32 UTC, Jyrki Soini 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1164568 0 unspecified CLOSED DeviceTreeError: failed to scan disk pdc_bdabcifbfi 2022-05-16 11:32:56 UTC
Red Hat Bugzilla 1169229 1 None None None 2021-01-20 06:05:38 UTC

Internal Links: 1164568

Description Richard S. Hendershot 2014-10-30 15:27:42 UTC 
Description of problem:
burn images/boot.iso i686 to DVD
boot phenom II X6 with DVD
at language selection screen failure occurs

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

The following was filed automatically by anaconda:
anaconda 21.48.12-1 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 2362, in _verifyMemberFormat
    if not isinstance(member.format, self.formatClass):
  File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 2419, in _addParent
    error = self._verifyMemberFormat(member)
  File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 183, in append
    self.appendfunc(y)
  File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 325, in _setParentList
    self._parents.append(parent)
  File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 268, in __init__
    self.parents = parents
  File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 576, in __init__
    Device.__init__(self, name, parents=parents)
  File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 2083, in __init__
    parents=parents, sysfsPath=sysfsPath)
  File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 4277, in __init__
    sysfsPath=sysfsPath)
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1679, in handleUdevDMRaidMemberFormat
    parents=[device])
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1882, in handleUdevDeviceFormat
    self.handleUdevDMRaidMemberFormat(info, device)
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1233, in addUdevDevice
    self.handleUdevDeviceFormat(info, device)
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 2170, in _populate
    self.addUdevDevice(dev)
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 2105, in populate
    self._populate()
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 479, in reset
    self.devicetree.populate(cleanupOnly=cleanupOnly)
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 183, in storageInitialize
    storage.reset()
  File "/usr/lib/python2.7/threading.py", line 766, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib/python2.7/site-packages/pyanaconda/threads.py", line 227, in run
    threading.Thread.run(self, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/pyanaconda/threads.py", line 112, in wait
    self.raise_if_error(name)
  File "/usr/lib/python2.7/site-packages/pyanaconda/timezone.py", line 75, in time_initialize
    threadMgr.wait(THREAD_STORAGE)
  File "/usr/lib/python2.7/threading.py", line 766, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib/python2.7/site-packages/pyanaconda/threads.py", line 227, in run
    threading.Thread.run(self, *args, **kwargs)
AttributeError: 'DMRaidArrayDevice' object has no attribute 'formatClass'

Additional info:
addons:         com_redhat_kdump
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-21-i386 quiet
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.17.1-302.fc21.i686
product:        Fedora"
release:        Cannot get release name.
type:           anaconda
version:        Fedora
Comment 1 Richard S. Hendershot 2014-10-30 15:27:44 UTC 
Created attachment 952210 [details]
File: anaconda-tb
Comment 2 Richard S. Hendershot 2014-10-30 15:27:45 UTC 
Created attachment 952211 [details]
File: anaconda.log
Comment 3 Richard S. Hendershot 2014-10-30 15:27:46 UTC 
Created attachment 952212 [details]
File: environ
Comment 4 Richard S. Hendershot 2014-10-30 15:27:47 UTC 
Created attachment 952213 [details]
File: lsblk_output
Comment 5 Richard S. Hendershot 2014-10-30 15:27:47 UTC 
Created attachment 952214 [details]
File: nmcli_dev_list
Comment 6 Richard S. Hendershot 2014-10-30 15:27:48 UTC 
Created attachment 952215 [details]
File: os_info
Comment 7 Richard S. Hendershot 2014-10-30 15:27:49 UTC 
Created attachment 952216 [details]
File: program.log
Comment 8 Richard S. Hendershot 2014-10-30 15:27:49 UTC 
Created attachment 952217 [details]
File: storage.log
Comment 9 Richard S. Hendershot 2014-10-30 15:27:50 UTC 
Created attachment 952218 [details]
File: syslog
Comment 10 Richard S. Hendershot 2014-10-30 15:27:51 UTC 
Created attachment 952219 [details]
File: ifcfg.log
Comment 11 Richard S. Hendershot 2014-10-30 15:27:52 UTC 
Created attachment 952220 [details]
File: packaging.log
Comment 12 Richard S. Hendershot 2014-10-30 17:58:23 UTC 
fails with images/boot.iso x64 also
Comment 13 Richard S. Hendershot 2014-11-02 12:34:52 UTC 
*** Bug 1159625 has been marked as a duplicate of this bug. ***
Comment 14 David Lehman 2014-11-05 17:02:48 UTC 
Proposing on the basis that this will prevent any installation to dmraid storage.
Comment 15 David Lehman 2014-11-07 19:04:07 UTC 
*** Bug 1161728 has been marked as a duplicate of this bug. ***
Comment 16 Fedora Update System 2014-11-11 21:09:42 UTC 
anaconda-21.48.14-1.fc21, python-blivet-0.61.9-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/python-blivet-0.61.9-1.fc21,anaconda-21.48.14-1.fc21
Comment 17 Kamil Páral 2014-11-12 17:57:11 UTC 
Discussed at today's blocker review meeting [1]. Accepted as a blocker.  This bug is a violation of the Beta Criterion: "The installer must be able to detect and install to hardware or firmware RAID storage devices." [2] 

[1] http://meetbot.fedoraproject.org/fedora-blocker-review/2014-11-12/
[2] https://fedoraproject.org/wiki/Fedora_21_Beta_Release_Criteria#Hardware_and_firmware_RAID
Comment 18 Fedora Update System 2014-11-13 18:17:07 UTC 
Package anaconda-21.48.14-1.fc21, python-blivet-0.61.9-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-21.48.14-1.fc21 python-blivet-0.61.9-1.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-14928/python-blivet-0.61.9-1.fc21,anaconda-21.48.14-1.fc21
then log in and leave karma (feedback).
Comment 19 Fedora Update System 2014-11-15 09:16:14 UTC 
anaconda-21.48.14-1.fc21, python-blivet-0.61.9-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 20 Richard S. Hendershot 2014-11-16 16:14:52 UTC 
see bug id #1164568 :  http://bugzilla.redhat.com/show_bug.cgi?id=1164568

scenario fails for both 32 and 64 bit installs.  Also install seems noticably slower.  

I'll verify after disconnecting 2 drives as I had before. see my next comment.
Comment 21 Richard S. Hendershot 2014-11-16 16:36:36 UTC 
disconnecting drives allows progress beyond the point of this fail.  console does emit:

IGNORED:  error parsing blkid.tab


That file looks ok and if it's useful I can attach it.
Comment 22 Marian Csontos 2014-11-18 14:45:13 UTC 
I am not a dmraid expert but to me seems Bug 1164568 is completely different issue - looks like HW, dmraid or configuration error - the errors in syslog are present before anaconda takes over.

Jyrki, as your bug was marked a duplicate of this bug: is anaconda-21.48.14-1.fc21 still failing for you?
Comment 23 David Lehman 2014-11-18 15:04:26 UTC 
Bug 1164568 is not related to this one.

Mr. Hendershot, please do not reopen one bug because you have found a different one. It's fine to add a note here pointing to the other one, but reopening this one made little sense.
Comment 24 Richard S. Hendershot 2014-11-18 17:55:33 UTC 
The same test scenario failed in the same way after this was closed.  May I suggest the real fail is not involving the reporting agent and closing the bug without verification.

I linked the two hoping the important information would be available to stakeholders and only reopened b/c it was declared by you as a blocker and release date is imminent.

so sorry I offended your process
Comment 25 Marian Csontos 2014-11-19 13:16:10 UTC 
Your comments #c20 and #c21 suggest the original problem IS fixed but you run into different issue:

(In reply to Richard S. Hendershot from comment #20)
> see bug id #1164568 :  http://bugzilla.redhat.com/show_bug.cgi?id=1164568
> 
> scenario fails for both 32 and 64 bit installs.  Also install seems
> noticably slower.  
> 
> I'll verify after disconnecting 2 drives as I had before. see my next
> comment.

"Same scenario" is not the same as "the same way".

(In reply to Richard S. Hendershot from comment #21)
> disconnecting drives allows progress beyond the point of this fail.  console
> does emit:
> 
> IGNORED:  error parsing blkid.tab
> 
> That file looks ok and if it's useful I can attach it.

If there is a problem it is better to open a bug and do not be brief on details. Without data we are working with assumptions which leads to suboptimal results like here.

(In reply to Richard S. Hendershot from comment #24)
> The same test scenario failed in the same way after this was closed.

Attach logs please. What looks "the same way" in interface may be something completely different under the hood. And if Bug 1164568 is the "same way" you have seen it is definitely unrelated. Is that so please?

> May I
> suggest the real fail is not involving the reporting agent and closing the
> bug without verification.

Unfortunately that's how the "process" works - bodhi is where any test failures are supposed to be reported and package ius "blesses" once enough karma is collected. Comment 18 suggests what to do.

Have you tested the package fixes the issue?

In this case bodhi was likely wrong: as many bugs were bundled in single errata, it is likely people checked their bugs and just added karma.

May I suggest we may want to gather karma for each of the bugs separately?

> 
> I linked the two hoping the important information would be available to
> stakeholders and only reopened b/c it was declared by you as a blocker and
> release date is imminent.
> 
> so sorry I offended your process

It's not process who was offended. But no software would ever be delivered if upon fixing one bug another (unmasked by the former or linked to it) was used instead as a blocker without proper triage.
Comment 26 Richard S. Hendershot 2014-11-19 15:28:29 UTC 
thank you both for your comments. I'm gaining in how to work with your process.  I've also gained understanding of the trigger condition for the problem; just yesterday I was able to reproduce the problem with just one scratch drive (bugid# 1165292).

these all share the same origin:  line 2170, in _populate
    self.addUdevDevice(dev)

I marked it need info hoping David could clarify as to how to proceed.  Completely your folks' call as to whether it should be a new bug or continue on this one.  I was pretty sure they should be linked.  


>>And if Bug 1164568 is the "same way" you have seen it is definitely unrelated. Is that so please?

I'm not sure how to parse this.  When I first tried an installer build that had the updated blivet and anaconda it still broke at line 2170.  The 'current' log then is there.  

Likewise, when I discovered I could further simplify the test scenario I captured that 'current' log in bugid#1165292. 

Probably I should have put See Also from latest back to the earlier... and left this one alone.  Being a blocker, and in my experience still failing, I may have gotten over-excited.  

Anyway, your advice about how to proceed is most welcomed.
Comment 27 Marian Csontos 2014-11-20 10:18:08 UTC 
I am sure pretty ALL anaconda bugs share common origin:

  File "/usr/lib/python2.7/site-packages/pyanaconda/threads.py", line 227, in run
    threading.Thread.run(self, *args, **kwargs)

That does not mean they are all the same bug. It is better left out to anaconda developers to do triage otherwise it leads to more confusion and more work for everyone.
Comment 28 Richard S. Hendershot 2014-11-20 11:15:26 UTC 
one could say that all-bugs-everywhere have the same origin: that of turning on the power...

apologize again for over excited  :-)
Comment 29 David Lehman 2014-12-02 21:22:23 UTC 
*** Bug 1167000 has been marked as a duplicate of this bug. ***
Comment 30 Jyrki Soini 2014-12-08 20:32:05 UTC 
Created attachment 966005 [details]
anaconda.log
Comment 31 Jyrki Soini 2014-12-08 20:32:58 UTC 
Created attachment 966006 [details]
journalctl log
Comment 32 Jyrki Soini 2014-12-08 20:36:35 UTC 
I tried booting from USBflash and "yum update anaconda"
No longer blivet crash. Anaconda recognizes /boot partition and LVM physical volume, but I still was not able to add logical volumes within LVM and create mount points.
Note You need to log in before you can comment on or make changes to this bug.