Hi folks! Time for a first F24 Alpha blocker bug status mail. tl;dr work summary ------------------
QA folks: * help figure out what's going on in #1315541 * ensure all Alpha validation tests are covered with recent composes anaconda devs: * review/merge https://github.com/rhinstaller/anaconda/pull/542 for #1315434 * figure out what's going on in #1315541 * be part of the committee or whatever that decides what to do about #1313085 (bcl) systemd and NetworkManager devs: * be part of the committee or whatever that decides what to do about #1313085 (bcl) detailed per-bug info --------------------- 1. https://bugzilla.redhat.com/show_bug.cgi?id=1315434 - anaconda/pungi - POST Fedora 24 x86_64 network installs get i686 kernel and fail to boot I've posted a patch for this from the anaconda end that needs review and merge: https://github.com/rhinstaller/anaconda/pull/542 I think I also saw some discussion of what the issue is in Pungi, so it looks like we should be able to fix this from both ends. 2. https://bugzilla.redhat.com/show_bug.cgi?id=1313085 - systemd - NEW Name resolution fails (resolv.conf is a broken systemd symlink) on livemedia-creator live image This is the latest incarnation of an ongoing issue which involves something of a difference of opinion between systemd devs on the one hand and NetworkManager and anaconda folks on the other. Briefly put, if there is no /etc/resolv.conf when systemd-tmpfiles runs, it creates it as a symlink pointing to ../run/systemd/resolv/resolv.conf , which is the location where systemd-resolved would put a resolv.conf if it was in use. But we don't use systemd-resolved, we use NetworkManager. When NetworkManager starts up, if /etc/resolv.conf does not exist or exists as a regular file, it will replace it with a symlink to its own location (/var/run/NetworkManager/resolv.conf). But if /etc/resolv.conf exists as a symlink pointing anywhere else, NM will leave it alone. This is by design, and extensively commented in the code - https://cgit .freedesktop.org/NetworkManager/NetworkManager/tree/src/dns-manager/nm- dns-manager.c#n604 . The reason this changed now is the switchover from livecd-creator to livemedia-creator. livecd-creator creates an empty /etc/resolv.conf in the live images when producing them, which meant systemd-tmpfiles wouldn't touch the file and NetworkManager would replace it with a symlink to its resolv.conf and networking worked. livemedia-creator does not do this; a livemedia-creator-produced live image contains no /etc/resolv.conf at all. So when the live image is booted, systemd-tmpfiles creates /etc/resolv.conf as a symlink, systemd-resolved isn't used, NetworkManager refuses to replace the symlink, and the consequence is that /etc/resolv.conf is a dangling symlink pointing to a location managed by a daemon that isn't being used, and there's no name resolution. We've hit this issue in various circumstances and always had an acrimonious dispute about who's wrong about what and who ought to "fix it". I guess we get to do that again. I don't care who wins, but someone needs to change something. 3. https://bugzilla.redhat.com/show_bug.cgi?id=1315541 - anaconda - NEW (proposed) pyanaconda.packaging.PayloadInstallError: Failed to mount the install tree This is only a proposed blocker, but it looks pretty likely to be accepted. Recent KDE live images boot fine and can start anaconda, but crash when they reach the hub screen. This does not affect Workstation lives, it seems. We need to figure out what's going on here. -- Adam WilliamsonFedora QA Community MonkeyIRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . nethttp://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
