Fedora 32 Beta blocker status
Go/No is Thursday, with a targeted release date of 17 March. Action summary Accepted blockers - 1. dnf-plugins-extras — Cannot upgrade to Fedora 32: Modules blocking the upgrade path — NEW ACTION: QA to test FEDORA-2020-02ee4b1a1c, FEDORA-2020-717d521d35 2. PackageKit — Cannot upgrade to Fedora 32: Modules blocking the upgrade path — ASSIGNED ACTION: PackageKit maintainers to implement module reset call NEEDINFO: rhughes 3. python-blivet — blivet.errors.DeviceTreeError: failed to add slave root00p2 of device root00 — POST ACTION: Maintainers to create release containing upstream fix 4. anaconda — pyanaconda.modules.common.errors.storage.UnknownDeviceError: home — VERIFIED ACTION: none (fix is in Fedora-Workstation-Live-x86_64-32-20200226.n.0.iso) 5. python-blivet — anaconda unable to finish installation with software raid partition — NEW ACTION: Maintainers to diagnose and fix crash 6. distribution — Fedora 32 backgrounds not included — ASSIGNED ACTION: KDE team to update kde-settings package https://bugzilla.redhat.com/show_bug.cgi?id=1811160 Proposed blockers - 1. anaconda — bootloader entry missing after installation on armhfp — POST ACTION: anaconda maintainers to include rawhide fix in F32 2. freeipa — Support OpenDNSSEC 2.1 in FreeIPA — ASSIGNED ACTION: FreeIPA maintianers to clarify the scope of the problem and if FEDORA-2020-62c54952b9 addresses it 3. kernel — Display corruption on aarch64 virtual machines — NEW ACTION: someone(!) to diagnose virtualization text issue 4. mdadm — mdadm udev rules are installed in a wrong folder — MODIFIED ACTION: QA to verify update EDORA-2020-0274f17e66 fixes this 5. plymouth — LUKS password prompt is not shown with more displays connected — NEW ACTION: plymouth maintainers to create an update that includes fix 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 and libdnf updates (FEDORA-2020-02ee4b1a1c for F30, FEDORA-2020-717d521d35 for F31) have been submitted to fix this. 2. PackageKit — https://bugzilla.redhat.com/show_bug.cgi?id=1804564 — ASSIGNED Cannot upgrade to Fedora 32: Modules blocking the upgrade path libdnf has implemented an API to reset all modules. PackageKit needs to be updated to call that on upgrade. 3. python-blivet — https://bugzilla.redhat.com/show_bug.cgi?id=1798792 — POST 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. Partially fixed in upstream PR (https://github.com/storaged-project/blivet/pull/827). Full fix is blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1809117 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. python-blivet — https://bugzilla.redhat.com/show_bug.cgi?id=1804080 — ASSIGNED 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. 6. distribution — https://bugzilla.redhat.com/show_bug.cgi?id=1807342 — ASSIGNED Fedora 32 backgrounds not included New background package pushed. kde-settings needs an update to reflect it: https://bugzilla.redhat.com/show_bug.cgi?id=1807342 Proposed blockers - 1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=1807252 — POST bootloader entry missing after installation on armhfp The only boot entry is the rescue boot. Fixed in Rawhide (as anaconda-33.2-1). 2. freeipa — https://bugzilla.redhat.com/show_bug.cgi?id=1810963 — ASSIGNED Support OpenDNSSEC 2.1 in FreeIPA FreeIPA needs additional work to support OpenDNSSEC 2.1. However, the openQA tests pass and update FEDORA-2020-62c54952b9 contains a new FreeIPA build. It's not clear if this is still an issue. 3. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=1807661 — NEW Display corruption on aarch64 virtual machines Text on aarch64 VMs appears garbled and unreadable, breaking openQA tests. This behavior does not exist on bare metal. 4. mdadm — https://bugzilla.redhat.com/show_bug.cgi?id=1809117 — MODIFIED mdadm udev rules are installed in a wrong folder udev rules get placed into /usr/lib/udev/rules.d/rules.d/. FEDORA-2020-0274f17e66 fixes this. 5. plymouth — https://bugzilla.redhat.com/show_bug.cgi?id=1810070 — NEW LUKS password prompt is not shown with more displays connected LUKS password prompt is not displayed when
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 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32 Beta blocker status
On Fri, Feb 21, 2020, 23:54 Kevin Kofler wrote: > Ben Cotton wrote: > > 1. dnf-plugins-extras — Cannot upgrade to Fedora 32: Modules blocking > > the upgrade path — NEW > > ACTION: dnf team to implement module reset workaround > > > > 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 > > Yet again! > > Can we please finally make it release-blocking to have a permanent, > non-hack > fix for this issue (ideally, eliminating all default streams and providing > a > default upgrade path from modular to non-modular packages, requiring an > explicit opt-out if the user wishes to remain on modules)? We already > punted > that for F31 and here we are again having the exact same issue for F32! > FESCo is aware of this issue and there is a current proposal to "ban" default streams, at least for now. See: https://pagure.io/fesco/issue/2341#comment-627466 Fabio > Kevin Kofler > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32 Beta blocker status
Ben Cotton wrote: > 1. dnf-plugins-extras — Cannot upgrade to Fedora 32: Modules blocking > the upgrade path — NEW > ACTION: dnf team to implement module reset workaround > > 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 Yet again! Can we please finally make it release-blocking to have a permanent, non-hack fix for this issue (ideally, eliminating all default streams and providing a default upgrade path from modular to non-modular packages, requiring an explicit opt-out if the user wishes to remain on modules)? We already punted that for F31 and here we are again having the exact same issue for F32! Kevin Kofler ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 32 Beta blocker status
A week later than I intended, here's the start of the weekly Fedora 32
blocker status mails!
Action summary
=
Accepted blockers
-
1. dnf-plugins-extras — Cannot upgrade to Fedora 32: Modules blocking
the upgrade path — NEW
ACTION: dnf team to implement module reset workaround
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
3. python-blivet — blivet.errors.DeviceTreeError: failed to add slave
root00p2 of device root00 — ASSIGNED
ACTION: Maintainers to diagnose and fix crash
Proposed blockers
-
1. 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.
2. kbd — systemd-vconsole-setup having problem to start in the
installation environment — MODIFIED
ACTION: reporter to verify that systemd-245~rc1-3.fc32, which should
be in the next F32 compose, fixes the issue
NEEDINFO: jkone...@redhat.com
3. kernel — UEFI installs from live images fail since around
Fedora-Rawhide-20200214.n.1 (boot loader entry creation fails) — NEW
ACTION: QA to continue trying to determine the cause
4. maven — installation of slf4j is broken unless maven module is
disabled — ASSIGNED
ACTION: maven maintainer to update slf4j in the maven 3.5 module stream
5. python-blivet — anaconda unable to finish installation with
software raid partition — NEW
ACTION: Maintainers to diagnose and fix crash
6. selinux-policy — denied { search } for pid=XXX comm="certmonger"
name="opencryptoki" (breaks FreeIPA) — POST
ACTION: maintainer to package upstream commit that may fix this
Bug-by-bug detail
=
Accepted blockers
-
1. dnf-plugins-extras —
https://bugzilla.redhat.com/show_bug.cgi?id=1767351 — NEW
Cannot upgrade to Fedora 32: Modules blocking the upgrade path
Follows from F31 blockers that had a workaround of resetting the
module on upgrade. FESCo declared this as an F32 blocker. It may
require a workaround again since a longer-term fix may take too long
to implement.
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
Proposed blockers
-
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/).
2. kbd — https://bugzilla.redhat.com/show_bug.cgi?id=1801272 — MODIFIED
systemd-vconsole-setup having problem to start in the installation environment
Text-based installation does not accept input all of the time. May
have the same cause as BZ 1803293, which is fixed by
systemd-245~rc1-3.fc32.
3. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=1804953 — NEW
UEFI installs from live images fail since around
Fedora-Rawhide-20200214.n.1 (boot loader entry creation fails)
Live UEFI installs of Wostkation and KDE fail to create the bootloader
entry. Non-live installs work as expected.
4. maven — https://bugzilla.redhat.com/show_bug.cgi?id=1801882 — ASSIGNED
installation of slf4j is broken unless maven module is disabled
The problem described in this bug is a broken dependency of
slf4j-jdk14 ursine package - it requires virtual package that is not
available in Fedora repos enabled by default - the virtual package
with required version is provided by package that is shadowed by
modular package with the same name, which is expected behaviour of
modularity. This is a short-term fix.
5. python-blivet — https://bugzilla.redhat.com/show_bug.cgi?id=1804080 — NEW
anaconda unable to finish installation with software raid partition
Unlike BZ 1798792, this is a failure to create new software RAID
devices in the installer.
6. selinux-policy — https://bugzilla.redhat.com/show_bug.cgi?id=1804958 — POST
denied { search } for pid=XXX comm="certmonger" name="opencryptoki"
(breaks FreeIPA)
Yet to be confirmed in F32 composes or with fresh deployments. May be
fixed in commit f7a21a9f173e1c8071718b1dea40eed2271c284d
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
Re: Fedora 32 Beta blocker status
On Fri, 2020-02-21 at 14:09 -0500, Ben Cotton wrote: > > 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 This isn't quite correct. The issue is that if you boot *the F32 installer* with an existing software RAID set, it crashes. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
