The Go/No-Go meeting is Thursday! Action summary ====================
Accepted blockers ----------------- 1. libreport — abrt-server errors when processing zstd compressed core dumps produced by systemd-246~rc1-1.fc33 — POST ACTION: msuchy to get retrace server back in service 2. sddm — login stuck when changing users repeatedly (log out, log in a different one) — NEW ACTION: sddm maintainers to diagnose issue and fix or pass the buck as appropriate NEEDINFO: mbriza, rdieter 3. distribution — Everything boot x86_64 image exceeds maximum size — ASSIGNED ACTION: none. Fixing Server boot should fix this, too 4. distribution — Server boot x86_64 image exceeds maximum size — NEW ACTION: Server WG to determine whether or not to remove packages or increase size limit. 5. distribution — Release-blocking Fedora 33 images have Fedora 32 backgrounds — NEW ACTION: kde-settings maintainers to update package to use new backgrounds (BZ 1872054) 6. pki-core — FreeIPA server upgrade from Fedora 32 or Fedora 31 fails with java.lang.UnsupportedClassVersionError — ASSIGNED ACTION: pki-core maintainers to package an update which includes the upstream PR 7. libpreport — bugs can't be reported: "No matching actions found for this event" — NEW ACTION: abrt maintainers to diagnose and fix issue 8. NetworkManager-openconnect — systemd-resolved.service not work with DNS server placed behind VPN (openconnect) — ASSIGNED ACTION: NetworkManager-openconnect maintainers to add integration for systemd-resolved. 9. anaconda — Booting Server DVD then selecting a mirrorlist repository does not work — MODIFIED ACTION: anaconda maintainers to package anaconda-33.25.3 update 10. kernel — 5.8.3-300.fc33.aarch64 kernel panic on boot (X-Gene PMU) — VERIFIED ACTION: none! Proposed blockers ----------------- 1. gnome-initial-setup — g-i-s fails to completely launch following clean install, opens in a tiny non-resizeable window instead — NEW ACTION: QA to test on bare metal to see if scope is limited to VMs while upstream hopefully gets us a fix 2. kernel — dasbus.error.DBusError: cannot initialize a disk that has partitions — NEW ACTION: kernel maintainers to diagnose issue, QA to try to find a reliable reproducer Bug-by-bug detail ============= Accepted blockers ----------------- 1. libreport — https://bugzilla.redhat.com/show_bug.cgi?id=1860616 — POST abrt-server errors when processing zstd compressed core dumps produced by systemd-246~rc1-1.fc33 FEDORA-2020-59e144acee contains a potential fix, but appears to introduce a new blocker (BZ 1873029). It may be moot until the retrace server is brought back online. The infra team has provisioned a basic instance, which msuchy is working to get ready for use. 2. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=1861700 — NEW login stuck when changing users repeatedly (log out, log in a different one) User processes linger after logout which blocks logging in when another user has logged in between the two sessions. Or when the second user logs back in. Or when a single user logs in repeatedly. Using KillUserProcesses=Yes helps the first problem, but raises on of its own. It appears to be a race condition of some kind as the behavior is not fully consistent. 3. distribtution — https://bugzilla.redhat.com/show_bug.cgi?id=1849430 — ASSIGNED Everything boot x86_64 image exceeds maximum size Latest compose does not significantly shrink the image size. Given the similar nature of the overages, I believe fixing the Server image size, which sgallagh is working on, will fix this as well. 4. distribtution — https://bugzilla.redhat.com/show_bug.cgi?id=1849431 — ASSIGNED Server boot x86_64 image exceeds maximum size We need to slim it down by ~14 MB. 5. distribution — https://bugzilla.redhat.com/show_bug.cgi?id=1869892 — ASSIGNED Release-blocking Fedora 33 images have Fedora 32 backgrounds Backgrounds package has been created, but KDE Plasma needs to be explicitly updated to use it. BZ 1872054 open for this. 6. pki-core — https://bugzilla.redhat.com/show_bug.cgi?id=1871990 — ASSIGNED FreeIPA server upgrade from Fedora 32 or Fedora 31 fails with java.lang.UnsupportedClassVersionError /etc/sysconfig/tomcat.conf needs to be changed to point to JDK 11 on upgrade. Upstream PR contains a potential fix: https://github.com/dogtagpki/pki/pull/532 7. libreport — https://bugzilla.redhat.com/show_bug.cgi?id=1873029 — NEW bugs can't be reported: "No matching actions found for this event" No crashes can be reported. abrt shows "no matching event" error message. This appears to be introduced by the fix for 1860616. 8. NetworkManager-openconnect — https://bugzilla.redhat.com/show_bug.cgi?id=1863041 — NEW systemd-resolved.service not work with DNS server placed behind VPN (openconnect) When connected to an OpenConnect VPN, host name resolution fails. Openconnect needs to push server information to systemd-resolved. Upstream vpnc-script added support for systemd-resolved in 2016, so it's not clear what is missing. This may need to be reassigned to the vpnc-script component. 9. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=1872056 — MODIFIED Booting Server DVD then selecting a mirrorlist repository does not work The Server DVD openQA installation tests fail when using a mirrorlist URL. They do not fail with a direct repository URL. An upstream fix has been merged and will be in anaconda-33.25.3. 10. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=1874117) — VERIFIED 5.8.3-300.fc33.aarch64 kernel panic on boot (X-Gene PMU) Uninitialized variable existed xgene PMU driver. This bug has been squashed (and patch sent upstream). Proposed blockers ----------------- 1. gnome-initial-setup — https://bugzilla.redhat.com/show_bug.cgi?id=1875140 — NEW g-i-s fails to completely launch following clean install, opens in a tiny non-resizeable window instead Some fraction of installs end up with gnome-initial-setup in a tiny window. So far, this has only been observed in vritual machines and is functional when resized to a usable size. Issue filed upstream: https://gitlab.gnome.org/GNOME/gnome-initial-setup/-/issues/110 2. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=1828188 — NEW dasbus.error.DBusError: cannot initialize a disk that has partitions It is possible that partitions are not discovered by kernel after boot (meaning no nodes in /dev and no records in sysfs) so anaconda doesn't add partitions to devicetree during reset. But after running some parted checks the partitions magically appears, that's why device.format.partitions works. Reproducibility currently unclear. It may be related to mdraid. -- 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
