Bug 772878
| Summary: | RuntimeError: maximum recursion depth exceeded | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Frantisek Dvorak <vcela> | ||||||||
| Component: | anaconda | Assignee: | David Lehman <dlehman> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | urgent | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | rawhide | CC: | anaconda-maint-list, awilliam, g.kaviyarasu, jonathan, vanmeeuwen+fedora | ||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:fd3d93beee42393fb6b66a40146d9bd09aa8c2ccaa76c64ab3ef0d130455f354 AcceptedBlocker | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-02-08 21:30:42 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: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 752648 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Frantisek Dvorak
2012-01-10 08:21:25 UTC
Created attachment 551788 [details]
File: anaconda-tb-QdzudB
Created attachment 551789 [details]
File: description
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. 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. 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 Created attachment 558735 [details]
traceback of the crash in 17.4 liveinst
Proposing as Alpha blocker, this breaks live install (possibly only on a system with LVM volumes?) Adam, try this: http://dlehman.fedorapeople.org/updates/updates-772878-adamw.img Looks good: with that on top of 17.4, I get a successful install. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers 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! 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 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 |