Fedora 17 release status: blockers, builds and karma requirements

Adam Williamson awilliam at redhat.com
Fri May 11 06:20:37 UTC 2012

Hi, folks. It seems about time to send out an overview of the Fedora 17
release status, and what's needed to get us there.

We're a long way behind on rolling a release candidate, because there
are several unaddressed blockers (accepted and proposed). See the
https://fedoraproject.org/wiki/Current_Release_Blockers . Here's a
summary of the action needed, to be followed by a bug-by-bug account:

The following updates need testing and karma:

* https://admin.fedoraproject.org/updates/mesa-8.0.2-7.fc17
* https://admin.fedoraproject.org/updates/FEDORA-2012-7614/mutter-3.4.1-3.fc17
(these two together, especially by users of NVIDIA cards with <=64MB VRAM)
* https://admin.fedoraproject.org/updates/FEDORA-2012-7398/mysql-connector-java-5.1.17-5.fc17
* https://admin.fedoraproject.org/updates/FEDORA-2012-7648/abrt-2.0.10-3.fc17
* https://admin.fedoraproject.org/updates/glibc-2.15-37.fc17
* https://admin.fedoraproject.org/updates/os-prober-1.52-3.fc17
* https://admin.fedoraproject.org/updates/pam-1.1.5-6.fc17

The following bugs require further information from anyone who can

* http://bugzilla.redhat.com/show_bug.cgi?id=817037
* http://bugzilla.redhat.com/show_bug.cgi?id=820366

The following bugs require developer attention:

* http://bugzilla.redhat.com/show_bug.cgi?id=811242 (NFS experience required)
* http://bugzilla.redhat.com/show_bug.cgi?id=819138 (releng only)
* http://bugzilla.redhat.com/show_bug.cgi?id=819492 (desktop team, if accepted)

Accepted blockers

1. http://bugzilla.redhat.com/show_bug.cgi?id=809647 - "sourcing
updates.img from installation repository does not work" - this is
verified to be fixed in TC4, and the update has appropriate karma to be
pushed stable. No action needed

2. http://bugzilla.redhat.com/show_bug.cgi?id=811242 - "PXE and repo=nfs
or repo=nfsiso freezes installer" - this is a very mysterious bug that
breaks PXE installs via NFS. It doesn't seem to be a straightforward bug
in anaconda; it seems to be to do with NFS. The latest information we
have is that it only affects NFSv4; a test with NFSv3 seems to succeed.
Any input from developers with experience with NFS would help.

3. http://bugzilla.redhat.com/show_bug.cgi?id=770197 - "Gnome Shell
corrupted on nVidia cards with low VRAM" - an update to fix this has
been submitted,
https://admin.fedoraproject.org/updates/mesa-8.0.2-7.fc17 . Note that
you also will need
https://admin.fedoraproject.org/updates/FEDORA-2012-7614/mutter-3.4.1-3.fc17 for a full test. We need people with NVIDIA adapters with 64MB or less of VRAM to test if they can use Shell successfully with those two updates installed, and provide positive karma on the updates if so.

4. http://bugzilla.redhat.com/show_bug.cgi?id=755335 - "Shutting down
while auto-updating breaks the system" - we have an update that works
around this,
https://admin.fedoraproject.org/updates/gnome-settings-daemon-3.4.1-4.fc17 . It is verified to fix the bug and has appropriate karma to be pushed stable. No action is needed.

5. http://bugzilla.redhat.com/show_bug.cgi?id=809111 - "grub2-probe
fails during install" - the TC4 anaconda update,
https://admin.fedoraproject.org/updates/FEDORA-2012-7623/anaconda-17.26-1.fc17 , is reported to fix this and has appropriate karma to be pushed stable. No action is needed.

6. http://bugzilla.redhat.com/show_bug.cgi?id=818378 - "grub2 can't
install because /proc/device-tree exists" - an update to fix this,
https://admin.fedoraproject.org/updates/FEDORA-2012-7531/kernel-3.3.4-5.fc17 , was pulled into TC4 and confirmed to fix it. It has appropriate karma to go stable. No action is needed.

7. https://bugzilla.redhat.com/show_bug.cgi?id=819139 - "repoclosure
failure on 17.TC4 DVDs (mysql-connector-java)" - we have an update that
should fix this once it's pushed stable (just pulling it via a side repo
isn't enough, for dull reasons that aren't worth explaining). The
https://admin.fedoraproject.org/updates/FEDORA-2012-7398/mysql-connector-java-5.1.17-5.fc17 , needs one more karma point. Obviously it'd be best if someone who actually connects MySQL with Java can test and see if it still works, but two of us have +1ed it on the basis that it at least resolves the dependency problem, and it'd be fine to have one more +1 on this basis.

8. http://bugzilla.redhat.com/show_bug.cgi?id=819138 - "repoclosure
failure on 17.TC4 DVDs (eclipse)" - this is an annoying problem with
Java dependencies, which dgilmore thought he could fix in TC4 but his
idea didn't work. It's purely a compose issue, really, so we need
dgilmore to figure this one out for the TC5/RC1 compose.

Proposed blockers

All of these will be reviewed at the blocker meeting tomorrow. Please
attend if you have any interest.

1. http://bugzilla.redhat.com/show_bug.cgi?id=819113 - "abrt-ccpp
service not enabled by default on F17" - there is a fix for this which I
have verified to work. It needs karma:

2. http://bugzilla.redhat.com/show_bug.cgi?id=817037 - "Installer damage
Disks" - this is a rather vague report which neither I nor the anaconda
team could reproduce. If anyone else can reproduce it, we badly need
precise reproduction steps and logs. Hard to proceed with this one
without better details.

3. http://bugzilla.redhat.com/show_bug.cgi?id=820366 - "Cannot boot 17
Beta installer: /dev/root does not exist" - the anaconda team is fairly
sure this should be fixed in the Final TCs (the reporter was using
Beta), and we need the reporter - Andrew McNabb - to re-test.

4. http://bugzilla.redhat.com/show_bug.cgi?id=813648 - "gnome-shell
shows blank windows on hardware lacking NPOT textures" - this is more or
less of a piece with #770197, discussed in Accepted Blockers, as many
adapters with low VRAM also cannot handle NPOT textures. As explained
above, we need people with low VRAM NVIDIA adapters to test the two
updates, https://admin.fedoraproject.org/updates/mesa-8.0.2-7.fc17 and
https://admin.fedoraproject.org/updates/FEDORA-2012-7614/mutter-3.4.1-3.fc17 , and provide karma.

5. http://bugzilla.redhat.com/show_bug.cgi?id=801650 - "Fedora PV guest
17 fails to boot under Xen (with SandyBridge or newer hardware that do
xsave)" - we have a proposed fix for this, but it's a glibc change.
Obviously, we need as many people as possible to install the updated
glibc and make sure nothing explodes. Of course, testing of Xen and Ivy
Bridge hardware is doubly important. The update,
https://admin.fedoraproject.org/updates/glibc-2.15-37.fc17 , needs

6. http://bugzilla.redhat.com/show_bug.cgi?id=819492 - "GVfs apps should
convey when eject/unmount takes a long time" - this is a very
contentious bug so far as blocker status goes. It would not be
straightforward to 'fix'; if it's accepted as a blocker we likely will
wind up browbeating the desktop team into some kind of hideous
workaround. Desktop team, stand by to be browbeaten.

7. http://bugzilla.redhat.com/show_bug.cgi?id=811412 - "F17 Final TC3
has bogus OS X entries in grub2 when installed from dd-written images" -
there is a fix for this which I have tested to resolve the bug,
https://admin.fedoraproject.org/updates/os-prober-1.52-3.fc17 . The
update needs karma.

8. http://bugzilla.redhat.com/show_bug.cgi?id=813548 - "pulseaudio
occasionally terminates" - we don't really have much development effort
on this yet. It seems to be more or less agreed that it's likely to be
rejected as a blocker.

9. http://bugzilla.redhat.com/show_bug.cgi?id=740280 - "/dev/live no
longer exists" - we have fixed this in spin-kickstarts git, and verified
the fix. No action should be required. The fix is in TC4, so obviously,
check nothing is broken in the live images, and you can use /home

10. http://bugzilla.redhat.com/show_bug.cgi?id=815413 - "Preupgrade from
F16 to F17 Beta does not regenerate pam.d/system-auth*, causing
systemd-loginctl not to know about user sessions, breaking PulseAudio" -
we are not entirely sure what went wrong for the two reporters here, but
it seems definitely to be associated with very old installs which have
been continually upgraded. It is likely to be rejected as a blocker, but
there is an update which may mitigate the problem which requires karma:

Any help with the action items listed above would be greatly
appreciated! Thanks.

The plan from here is to have the blocker meeting tomorrow, and do a new
compose soon after that meeting, either a TC or RC depending on the
results of the meeting and overnight development.
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora

More information about the devel mailing list