Many fewer blockers than last week. Hooray! Go/No-Go for target date #1 is Thursday. Action summary ==================== Accepted blockers ----------------- 1. geoclue2 — time is transiently incorrect when Automatic Time Zone is enabled — MODIFIED ACTION: QA to verify FEDORA-2021-14f2ed62fd 2. selinux-policy — The switch for Fedora Third Party repositories does not switch them on. — MODIFIED ACTION: QA to verify FEDORA-2021-d3cb1609c8 3. plasma-discover — Discover shows a misleading state of Flatpak repos, can't delete disabled repos — NEW ACTION: Maintainers to fix issue 4. plasma-discover — Discover doesn't seem to find any RPM packages, neither locally installed nor in RPM repos — NEW ACTION: Maintainers to fix issue 5. plasma-discover — Toggling repo in Discover doesn't redraw the checkbox, confusing users — NEW ACTION: Maintainers to fix issue 6. uboot-tools — RK3399 - SPL: failed to boot from all boot devices — POST ACTION: Maintainers to submit an update with problematic patch reverted Proposed blockers ----------------- 1. kernel — Fedora 35 aarch64 cloud image based openstack VM hangs — NEW ACTION: Maintainers to diagnose and fix issue 2. clevis-pin-tpm2 — clevis - thread 'main' panicked at 'called `Option::unwrap() — ASSIGNED ACTION: Maintainers to fix issue NEEDINFO: pbrobinson 3. dracut — 5.14.9-200.fc34 kernel will not boot on AWS EC2 t2.small instance — NEW ACTION: Maintainers to submit an update that includes upstream fix 4. gnome-initial-setup — Online Accounts setup does not appear when wifi is configured through Gnome Initial Setup — MODIFIED ACTION: QA to verify FEDORA-2021-14f2ed62fd 5. kscreenlocker — KScreenLocker segfaults when screen dims — NEW ACTION: Maintainers to fix issue 6. spin-kickstarts — resolv.conf on Cloud images are not empty, causing cloud-init automatic network configuration to fail — NEW ACTION: QA to verify kickstarts commit 32b03e0 Bug-by-bug detail ============= Accepted blockers ----------------- 1. geoclue2 — https://bugzilla.redhat.com/show_bug.cgi?id=1991075 — MODIFIED time is transiently incorrect when Automatic Time Zone is enabled The displayed time is incorrect in some cases when Automatic Time Zone is enabled. Both `timedatectl` and the GNOME display show the wrong time. Update FEDORA-2021-532f05d2e3 contained a partial fix. Subsequent investigation discovered a change in NetworkManager 1.32 broke glib's network connectivity detection code, which broke geoclue. Update FEDORA-2021-14f2ed62fd contains a candidate fix. 2. selinux-policy — https://bugzilla.redhat.com/show_bug.cgi?id=2001837 — POST The switch for Fedora Third Party repositories does not switch them on. Enabling third party repos failed, which was sort of fixed in gnome-initial-setup-41~rc-3.fc35. However, when running SELinux in enforcing mode, it still fails. Several updates to the policy configuration have been added. Update FEDORA-2021-d3cb1609c8 for fedora-third-party removes an unneeded chcon call. 3. plasma-discover — https://bugzilla.redhat.com/show_bug.cgi?id=2011291 — NEW Discover shows a misleading state of Flatpak repos, can't delete disabled repos 4. plasma-discover — https://bugzilla.redhat.com/show_bug.cgi?id=2011322 — NEW Discover doesn't seem to find any RPM packages, neither locally installed nor in RPM repos Discover shows updates in the "Installed" tab, but when no updates are available, only flatpaks are listed. This isn't universally reproducible. Updated installations from Beta media seem to work, but nightlies do not (as least as of 20211011.n.0.iso). 5. plasma-discover — https://bugzilla.redhat.com/show_bug.cgi?id=2011333 — NEW Toggling repo in Discover doesn't redraw the checkbox, confusing users When clicking on the checkbox, repo enablement is toggled, but that is not reflected in the UI. This could lead to users putting the repos in an undesired state. This is not fixed in Discover 5.23. 6. uboot-tools — https://bugzilla.redhat.com/show_bug.cgi?id=2014182 — POST RK3399 - SPL: failed to boot from all boot devices uboot-tools releases 2021.{07,10} do not boot on rk3399 devices. pbrobinson identified the responsible patch and is testing reversion on key devices. Proposed blockers ----------------- 1. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=2011928 — NEW Fedora 35 aarch64 cloud image based openstack VM hangs OpenStack aarch64 VMs hang on boot. With the same kernel, this does not happen on F34 cloud images, so this may implicate the BTRFS change. 2. clevis-pin-tpm2 — https://bugzilla.redhat.com/show_bug.cgi?id=2012758 — ASSIGNED clevis - thread 'main' panicked at 'called `Option::unwrap() A crash in clevis presents unlocking TPM2 storage, which is part of the key IoT security functionality. QA tests are passing on F35 and failing on Rawhide, however the user report came from F35. 3. dracut — https://bugzilla.redhat.com/show_bug.cgi?id=2010058 — NEW 5.14.9-200.fc34 kernel will not boot on AWS EC2 t2.small instance xen-blkfront in kernel 5.14 stopped using blk_cleanup_queue. This seems to result in the necessary module not being added to the initramfs. Upstream commit https://github.com/dracutdevs/dracut/commit/b292ce72 contains a candidate fix. 4. gnome-initial-setup — https://bugzilla.redhat.com/show_bug.cgi?id=2013742 — MODIFIED Online Accounts setup does not appear when wifi is configured through Gnome Initial Setup Changes in network settings are not recognized by g-i-s, so adding a WiFi network when no other network connection previously exists causes g-i-s to act as if no networks are configured. Update FEDORA-2021-14f2ed62fd contains a candidate fix. 5. kscreenlocker — https://bugzilla.redhat.com/show_bug.cgi?id=2013626 — NEW KScreenLocker segfaults when screen dims After letting the screen lock due to inactivity, the screen goes black and is unresponsive, including to VT switching. This has not been reproduced on a variety of platforms. It appears to be limited to a narrow configuration. This appears to be on track for rejection as a blocker bug. 6. spin-kickstarts — https://bugzilla.redhat.com/show_bug.cgi?id=2014526 — NEW resolv.conf on Cloud images are not empty, causing cloud-init automatic network configuration to fail NetworkManager writes to `/etc/resolv.conf` which results in a delay of 15 seconds or more. This is fixed in kickstarts: https://pagure.io/fedora-kickstarts/c/32b03e0440a8717277ebfbb51606bd92f328b54c _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/test@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
