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
Created attachment 952210 [details] File: anaconda-tb
Created attachment 952211 [details] File: anaconda.log
Created attachment 952212 [details] File: environ
Created attachment 952213 [details] File: lsblk_output
Created attachment 952214 [details] File: nmcli_dev_list
Created attachment 952215 [details] File: os_info
Created attachment 952216 [details] File: program.log
Created attachment 952217 [details] File: storage.log
Created attachment 952218 [details] File: syslog
Created attachment 952219 [details] File: ifcfg.log
Created attachment 952220 [details] File: packaging.log
fails with images/boot.iso x64 also
*** Bug 1159625 has been marked as a duplicate of this bug. ***
Proposing on the basis that this will prevent any installation to dmraid storage.
*** Bug 1161728 has been marked as a duplicate of this bug. ***
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
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
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).
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.
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.
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.
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?
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.
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
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.
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.
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.
one could say that all-bugs-everywhere have the same origin: that of turning on the power... apologize again for over excited :-)
*** Bug 1167000 has been marked as a duplicate of this bug. ***
Created attachment 966005 [details] anaconda.log
Created attachment 966006 [details] journalctl log
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.