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 570302
Summary: | Anaconda crashes on Intel BIOS RAID sets with pre-existing partitions | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Hans de Goede <hdegoede> |
Component: | anaconda | Assignee: | Hans de Goede <hdegoede> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 13 | CC: | awilliam, jonathan, rfujita, vanmeeuwen+fedora |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | anaconda-13.34-1 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 569462 | Environment: | |
Last Closed: | 2010-03-19 19:20:30 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: | 538274 |
Description
Hans de Goede
2010-03-03 19:58:34 UTC
Hans, I remember we added a parameter - 'noismwraid' or something like that - to F12 live because of the original incarnation of this bug. Should that stay or be removed for F13? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers (In reply to comment #1) > Hans, I remember we added a parameter - 'noismwraid' or something like that - > to F12 live because of the original incarnation of this bug. Should that stay > or be removed for F13? > We added that to the livecd default cmdline because of bug 537329, which unfortunately is still open. Perhaps we should make bug 537329 a F13Blocker ? Anyways this bug is completely unrelated, and the patch for it completely fixes it without requiring any workarounds. well, it's already f13target. I don't think it's quite a blocker - same as it wasn't for f12 - but it would certainly be great if you could fix it. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers The fix for this is in anaconda-13.34-1, setting status to modified. (In reply to comment #3) > well, it's already f13target. I don't think it's quite a blocker - same as it > wasn't for f12 - but it would certainly be great if you could fix it. > It is not up to me to fix it, either Notting needs to take my not very pretty but working patch, or some serious mdadm surgery is needed, see the bug for details, which is why I suggested making it a blocker, so that it hopefully will get some attention. Hans, for the purposes of the blocker review process, can you give us a bit more detail about what the actual bug is here, what's the scope of its impact, and who can test and confirm the fix? Thanks! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers (In reply to comment #6) > Hans, for the purposes of the blocker review process, can you give us a bit > more detail about what the actual bug is here, what's the scope of its impact, > and who can test and confirm the fix? Thanks! > Actually this is fixed now, see comment #4. Something has gone wrong with this bug not ending up in the bodhi ticket for the relevant update, and thus it not getting auto closed: https://admin.fedoraproject.org/updates/anaconda-13.35-1.fc13 Closing manually now. *** Bug 577637 has been marked as a duplicate of this bug. *** |