[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: One (more) week slip of Fedora 11 Release

> Not knowing if this had been formally done or not, I figured I'd look.
> I looked at all open rawhide anaconda bugs opened on March 1 or later.
> (126 bugs). The following list of 28 bugs are all crashers or things
> that render the system non-bootable.
> Some of these may be fixed already; some may not be fixable, some may
> have workarounds we can put on the common bug page. But if there are
> any other open bugs like 500808, they'd be in this list; if someone
> wants to do a sanity review to see if any of these are worth holding
> out for, go for it.

> https://bugzilla.redhat.com/show_bug.cgi?id=489991
> 	Anaconda crashes when disks with no partitions contain a filesystem

Still open, on dlehman's list of things to do in the future.  We deemed
it too low impact for F11.

> https://bugzilla.redhat.com/show_bug.cgi?id=491754
> 	 DeviceError: cannot commit to disk sda after 5 attempts

Still open, don't have a good handle on it.  jlaska can reproduce it but
not quite at will.

> https://bugzilla.redhat.com/show_bug.cgi?id=493058
> 	 Custom partitioning creation/edit causes traceback

Still open, I've never been able to reproduce.  This doesn't seem very
high impact either.

> https://bugzilla.redhat.com/show_bug.cgi?id=493699
> 	Traceback while installing with lvm/luks

Still open, no one's looked at this one to the best of my knowledge.
This could very well be a device-mapper bug judging from the
program.log.  I'll reassign.

> https://bugzilla.redhat.com/show_bug.cgi?id=494150
> 	anaconda exception when formatting drives

Still open, I've never been able to reproduce.  This also doesn't seem
very high impact.  Nobody's answered our call for a reproducer in
several weeks.

> https://bugzilla.redhat.com/show_bug.cgi?id=495139
> 	Anaconda traceback when installing with another LVM already existing

Still open, but only encountered when testing the Beta.  There have been
no duplicates.  I'd lean towards closing it INSUFFICIENT_DATA in another
day or two.

> https://bugzilla.redhat.com/show_bug.cgi?id=495356
> 	Unhandled exception at the end of partitioning

Still open, but I don't remember seeing it personally.  Hans was unable
to figure anything out.  Looks too low impact for F11.

> https://bugzilla.redhat.com/show_bug.cgi?id=495433
> 	Anaconda crash: Error opening /dev/sdb: No medium found

Still open, Ray encountered it yesterday while looking at UI stuff.  I
don't see how it's possible to run into but that doesn't stop people.
This could be potentially high impact for F11 and would probably be a
blocker if we had more time.

> https://bugzilla.redhat.com/show_bug.cgi?id=496440
> 	RAID1 volume create failed

Still open, still valid.  I don't know what the deal here is.

> https://bugzilla.redhat.com/show_bug.cgi?id=497183
> 	Installation fails with partition scheme

We had a bunch of these (2, None) bugs.  This should be resolved.  If
not, I might just lose it.  We were unable to find the original bug to
dupe this one to so I'll just close it.

> https://bugzilla.redhat.com/show_bug.cgi?id=497293
> 	allocatePartitions extended partition handling needs work

dlehman intends to look at allocatePartitions some more post-F11.
Reassigning.  I'm not sure about the impact of this bug.

> https://bugzilla.redhat.com/show_bug.cgi?id=498240
> 	Anaconda exception on upgrading from F10

Still open, seems important but not blocker material.  We should fix
this for F12.

> https://bugzilla.redhat.com/show_bug.cgi?id=498350
> 	Anaconda crashes in the partitioner screen

I've seen this but but have no reliable reproducer and my request for
more information has gone unanswered.

> https://bugzilla.redhat.com/show_bug.cgi?id=498408
> 	Anaconda crash during install: MDRaidError: mddeactivate failed for /dev/md1

Still open, looks important but not blocker material given that we've
only got one report.  From the looks of it, we've got /dev/md1 mounted
or otherwise occupied from when we were scanning devices.  Perhaps we
need to be more liberal in what states we accept as not-busy?

> https://bugzilla.redhat.com/show_bug.cgi?id=498486
> 	MDRaidError: mdactivate failed for /dev/md2  

For every mddeactivate bug, there is an equal and opposite mdactivate
bug?  I do not have a handle on this one at all and don't know its
impact but I wouldn't block F11 for it.  Someone needs to be tasked with
digging through the RAID bugs for the next release.

> https://bugzilla.redhat.com/show_bug.cgi?id=498553
> 	FSError: filesystem has not been created

Thanks to Ray's debugging, this sound be solved post-F11.  It was a
blocker and could be a blocker again if we really want given the simple
nature of the fix.  However, it's easy to work around and easy to fix
with a drop-in replacement file.

> https://bugzilla.redhat.com/show_bug.cgi?id=498751
> 	Failure at the start of Live install - device is already mapped

No one has looked at this one as far as I know, so its impact is unknown

> https://bugzilla.redhat.com/show_bug.cgi?id=495156
> 	FSError: mount failed: (2, None) 
> https://bugzilla.redhat.com/show_bug.cgi?id=499062
> 	SystemError: (2, None)  

These could be blockers, but I doubt their continued existence given the
number of times they were fixed this release.  I believe sandeen was
tracking them down as potential filesystem bugs, too.  I'll indicate as
such in the bugs and ask for testing the final release.

> https://bugzilla.redhat.com/show_bug.cgi?id=498820
> 	ValueError: Cannot remove extended partition sda4.  Logical partitions present.

This is a past dupe of 500808.  Closing.

> https://bugzilla.redhat.com/show_bug.cgi?id=499733
> 	Anaconda does not see Individual SATA11 drives -- linux nodmraid is ineffective

I do not know the impact of this bug but it could be significant.  I
still wouldn't hold F11 for it.  We haven't let dmraid problems block us
too much in the past.  Tradition!

> https://bugzilla.redhat.com/show_bug.cgi?id=500132
> 	swap format error - SwapSpaceError: format has not been created  

I've never seen this one but it might still be valid.  I asked for more
information.  Doesn't seem very high impact given the lack of dupes.

> https://bugzilla.redhat.com/show_bug.cgi?id=500995
> 	TypeError: float() argument must be a string or a number

jlaska seems to have a solid reproducer here.  No one has looked at this
bug, though.  No one else has hit it, though, so it's not a blocker to
me.  We should definitely fix for F12.

> https://bugzilla.redhat.com/show_bug.cgi?id=501297
> 	AttributeError: 'DeviceFormat' object has no attribute 'mount'  

Yet another bug we haven't at all looked at but does not seem to be a
blocker given the lack of duplicates.  I'd put it on the F12 list.

> https://bugzilla.redhat.com/show_bug.cgi?id=501340
> 	FormatSetupError: format has not been created  

Probably a dupe of 500132, but two instances of a bug does not make it a
freak out blocker in my opinion.

> https://bugzilla.redhat.com/show_bug.cgi?id=501584
> 	Initial initramfs created during installation has no keymap support

mkinitrd bug.  Seems really important to me, but I could live without it
because of my us keyboard layout.  I'll leave it to someone more familiar
with the bootup process than me to make the decision on this one.  I do
believe we have other bugs about this problem.

> https://bugzilla.redhat.com/show_bug.cgi?id=502092
> 	RuntimeError: Returning partitions to state prior to edit failed  

Solid reproducer from jlaska.  This could potentially be a bad one, but
we haven't gotten any other reports for now.  I'm fine with kicking this
one on over to F12 as well.  If it becomes too terrible, there's always

> https://bugzilla.redhat.com/show_bug.cgi?id=502663
> 	backtrace when setting up md raid.

This is a duplicate of 496440.  Oh joy.

So there you have it.

- Chris

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]