[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-test-list
Subject:    Re: anaconda crash, obviously invalid disk config
From:       Chris Murphy <lists () colorremedies ! com>
Date:       2013-06-27 18:02:06
Message-ID: 80CCB820-B329-4EC7-98BB-6FE4611B9D8B () colorremedies ! com
[Download RAW message or body]


On Jun 27, 2013, at 10:43 AM, Adam Williamson <awilliam@redhat.com> wrote:

> On Thu, 2013-06-27 at 10:28 -0600, Chris Murphy wrote:
> > https://bugzilla.redhat.com/show_bug.cgi?id=969684
> > 
> > 
> > This bug is sortof a mess in terms of comments because the crash can
> > be triggered with multiple boot loader install failure causes. But the
> > consistently triggerable ones are LDM partition scheme (which grub2
> > doesn't support at all apparently) and a disk without an MBR gap.
> > 
> > 
> > So technically it's a release blocking bug because it's an obviously
> > invalid layout, and anaconda crashes. But at the same time: a.) both
> > are rare cases, with LDM being more common; b.) we're an inch from
> > release so a fix would add more risk than benefit; c.) no prior
> > anaconda could make such a system bootable, although F17's anaconda
> > doesn't crash. The crash itself is a regression.
> 
> Thanks. I think the best way to avoid needless criterion ju-jitsu with
> this one is just not to propose it. ;) I agree with your assessment.

Yeah that's why I didn't propose. It's really an edge case. Although that bug ID is \
getting hit by other libreport caught crashes that are neither LDM or MBR gap \
induced, so it's acting like a catch all right now.



Chris Murphy
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test


[prev in list] [next in list] [prev in thread] [next in thread]