This clone bug is so that I don't forget to commit the patch for this once F-13 alpha is done. +++ This bug was initially created as a clone of Bug #569462 +++ Created an attachment (id=397080) Traceback from anaconda The summary says it all. --- Additional comment from pm-rhel on 2010-03-01 10:10:28 EST --- This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. --- Additional comment from hdegoede on 2010-03-03 05:13:26 EST --- A patch fixing this is here: https://www.redhat.com/archives/anaconda-devel-list/2010-March/msg00024.html I would like to get this into anaconda for beta1 if still possible. --- Additional comment from hdegoede on 2010-03-03 14:56:59 EST --- patch committed, changing status to modified. --- This clone bug is so that I don't forget to commit the patch for this once F-13 alpha is done.
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. ***