Bug 772878 - RuntimeError: maximum recursion depth exceeded
Summary: RuntimeError: maximum recursion depth exceeded
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: x86_64
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: David Lehman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:fd3d93beee42393fb6b66a40146...
Depends On:
Blocks: F17Alpha, F17AlphaBlocker
TreeView+ depends on / blocked
 
Reported: 2012-01-10 08:21 UTC by Frantisek Dvorak
Modified: 2012-02-08 21:30 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-08 21:30:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: anaconda-tb-QdzudB (543.21 KB, text/plain)
2012-01-10 08:21 UTC, Frantisek Dvorak
no flags Details
File: description (61.04 KB, text/plain)
2012-01-10 08:21 UTC, Frantisek Dvorak
no flags Details
traceback of the crash in 17.4 liveinst (130.56 KB, text/plain)
2012-02-01 00:55 UTC, Adam Williamson
no flags Details

Description Frantisek Dvorak 2012-01-10 08:21:25 UTC
libreport version: 2.0.6
executable:     /usr/bin/python
hashmarkername: anaconda
kernel:         3.1.0-7.fc16.x86_64
product:        Fedora
reason:         RuntimeError: maximum recursion depth exceeded
time:           Tue Jan 10 08:20:44 2012
version:        16

anaconda-tb-QdzudB: Binary file, 556249 bytes
description:    Text file, 62510 bytes

Comment 1 Frantisek Dvorak 2012-01-10 08:21:30 UTC
Created attachment 551788 [details]
File: anaconda-tb-QdzudB

Comment 2 Frantisek Dvorak 2012-01-10 08:21:32 UTC
Created attachment 551789 [details]
File: description

Comment 3 David Lehman 2012-01-10 14:03:59 UTC
Unusual setup revealed a bug in our handling of udev data. Your vg01-clustershare LV is reported by blkid as being a PV itself, but lvm doesn't find any info about the VG it belongs to. We erroneously refer to the DM_VG_NAME key, but that names an LV's parent VG -- not the VG a PV belongs to.

Comment 4 Frantisek Dvorak 2012-01-18 20:30:49 UTC
It was because i had in lvm PV of iscsi target. I reinstaled system clearly. But i thinh it will happen again. 
Thank you four your opinion.

Comment 5 Adam Williamson 2012-02-01 00:54:15 UTC
bcl says that a patch was applied for this bug in 17.4, and that's caused a fatal crash I'm seeing early in liveinst with 17.4 - right after I agree to proceed with installing a pre-release, IIRC. Attaching that traceback.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 6 Adam Williamson 2012-02-01 00:55:00 UTC
Created attachment 558735 [details]
traceback of the crash in 17.4 liveinst

Comment 7 Adam Williamson 2012-02-01 00:55:36 UTC
Proposing as Alpha blocker, this breaks live install (possibly only on a system with LVM volumes?)

Comment 8 David Lehman 2012-02-01 17:32:08 UTC
Adam, try this:

  http://dlehman.fedorapeople.org/updates/updates-772878-adamw.img

Comment 9 Adam Williamson 2012-02-01 17:50:38 UTC
Looks good: with that on top of 17.4, I get a successful install.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 10 Adam Williamson 2012-02-01 18:06:54 UTC
Also confirmed that I can do a successful install from an image with the /usr move packages, if I use anaconda 17.4 plus that updates.img. Can we get a 17.5 with the fix included? Thanks!

Comment 11 Adam Williamson 2012-02-03 17:14:22 UTC
Discussed at the 2012-01-03 blocker review meeting. Accepted as a blocker per criterion "The installer must boot (if appropriate) and run on all primary architectures, with all system firmware types that are common on those architectures, from default live image, DVD, and boot.iso install media". Note this is likely resolved in TC1, just needs me to confirm.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 12 Adam Williamson 2012-02-08 21:30:42 UTC
TC1 didn't get live images due to dependency issues, but I tested with the latest nightly (0206) and confirmed this is gone, completed a full install successfully. (The nightly has 17.5).



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers


Note You need to log in before you can comment on or make changes to this bug.