Fedora 32 Beta blocker status
Action summary
====================
Accepted blockers
-----------------
1. dnf-plugins-extras — Cannot upgrade to Fedora 32: Modules blocking
the upgrade path — NEW
ACTION: QA to test dnf-plugins-extras-4.0.9-3.fc32
2. PackageKit — Cannot upgrade to Fedora 32: Modules blocking the
upgrade path — NEW
ACTION: PackageKit maintainers to work with dnf team to implement
module reset workaround
NEEDINFO: rhughes
3. python-blivet — blivet.errors.DeviceTreeError: failed to add slave
root00p2 of device root00 — ASSIGNED
ACTION: Maintainers to diagnose and fix crash
4. anaconda — pyanaconda.modules.common.errors.storage.UnknownDeviceError:
home — VERIFIED
ACTION: releng to include anaconda-32.24.2-1 in next compose
5. gnome-shell — [abrt] gnome-shell:
js::gc::TenuredCell::writeBarrierPre(js::gc::TenuredCell*)():
gnome-shell killed by SIGSEGV — ASSIGNED
ACTION: QA to test upstream fix in COPR.
6. python-blivet — anaconda unable to finish installation with
software raid partition — NEW
ACTION: Maintainers to diagnose and fix crash
7. distribution — Fedora 32 backgrounds not included — NEW
ACTION: Design team to package backgrounds
Proposed blockers
-----------------
1. virt-manager — NAT (Inactive) by default, cannot create a VM — NEW
ACTION: Maintainers to diagnose and fix issue
Bug-by-bug detail
=============
Accepted blockers
-----------------
1. dnf-plugins-extras —
https://bugzilla.redhat.com/show_bug.cgi?id=1767351 — ON_QA
Cannot upgrade to Fedora 32: Modules blocking the upgrade path
dnf-plugins-extras-4.0.9-3.fc32 has been submitted to fix this.
2. PackageKit — https://bugzilla.redhat.com/show_bug.cgi?id=1804564 — NEW
Cannot upgrade to Fedora 32: Modules blocking the upgrade path
See also BZ 1767351 from which it was cloned. This may require an
additional API in libdnf
3. python-blivet — https://bugzilla.redhat.com/show_bug.cgi?id=1798792
— ASSIGNED
blivet.errors.DeviceTreeError: failed to add slave root00p2 of device root00
Using SCSI, IDE, or SATA software RAID created by the installer in a
virtualized environment crashes on the post-install boot. Behavior is
not seen with virtio disk bus. May be related to open upstream PR
https://github.com/storaged-project/blivet/pull/796
4. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=1806233 — VERIFIED
pyanaconda.modules.common.errors.storage.UnknownDeviceError: home
Deleting mount points from a previous custom-partitioned failed
installation causes a crash in the installer.
5. 1. gnome-shell —
https://bugzilla.redhat.com/show_bug.cgi?id=1801820 — ASSIGNED
[abrt] gnome-shell:
js::gc::TenuredCell::writeBarrierPre(js::gc::TenuredCell*)():
gnome-shell killed by SIGSEGV
Original fix did not fix it. Another upstream fix
(https://gitlab.gnome.org/GNOME/gjs/merge_requests/396) is available
in COPR (https://copr.fedorainfracloud.org/coprs/frantisekz/gjs-mr396/).
6. python-blivet — https://bugzilla.redhat.com/show_bug.cgi?id=1804080 — NEW
anaconda unable to finish installation with software raid partition
We create the md array such that mdadm should auto-activate it after
creation. Something a little weird happens with that, then blivet
thinks the array is inactive right afterward, so it tries to activate
it and mdadm complains that the devices are busy.
7. distribution — https://bugzilla.redhat.com/show_bug.cgi?id=1807342 — NEW
Fedora 32 backgrounds not included
It seems we don't have backgrounds for Fedora 32 yet. Fedora 32 KDE
installs are currently using a generic upstream background, but Fedora
32 GNOME/Workstation installs are using the Fedora 31 background.
Proposed blockers
-----------------
1. virt-manager — https://bugzilla.redhat.com/show_bug.cgi?id=1807768 — NEW
NAT (Inactive) by default, cannot create a VM
Default configuration of virtualization group on a clean install
results in "dnsmasq: unknown user or group: dnsmasq" error when
attempting to starting the network.
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis