16:00:38 #startmeeting F30-blocker-review 16:00:38 Meeting started Mon Apr 1 16:00:38 2019 UTC. 16:00:38 This meeting is logged and archived in a public location. 16:00:38 The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:38 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:38 The meeting name has been set to 'f30-blocker-review' 16:00:38 #meetingname F30-blocker-review 16:00:38 #topic Roll Call 16:00:38 The meeting name has been set to 'f30-blocker-review' 16:00:45 morning folks, who's around for F30 blocker review fun? 16:00:54 .hello2 16:00:55 frantisekz: frantisekz 'František Zatloukal' 16:00:59 * coremodule is here, secretary-duty ready! 16:01:02 .hello2 16:01:03 lruzicka: lruzicka 'Lukáš Růžička' 16:02:20 * satellit afk will read later 16:05:03 nirik: kalev: halfline: ignatenkobrain: pwhalen: ahoys? 16:05:50 * nirik is fesco meeting 16:06:00 I'm around, but have to go in a few minutes, sorry 16:06:37 alright, well 16:06:39 let's see how it goes 16:06:48 I'm overcommitted today, but I'll try to follow along 16:06:51 #chair frantisekz lruzicka 16:06:51 Current chairs: adamw frantisekz lruzicka 16:06:57 #topic Introduction 16:06:57 Why are we here? 16:06:57 #info Our purpose in this meeting is to review proposed blocker and nice-to-have bugs and decide whether to accept them, and to monitor the progress of fixing existing accepted blocker and nice-to-have bugs. 16:06:58 #info We'll be following the process outlined at: 16:06:58 #link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting 16:06:59 #info The bugs up for review today are available at: 16:07:01 #link http://qa.fedoraproject.org/blockerbugs/current 16:07:03 #info The criteria for release blocking bugs can be found at: 16:07:05 #link https://fedoraproject.org/wiki/Basic_Release_Criteria 16:07:09 #link https://fedoraproject.org/wiki/Fedora_30_Beta_Release_Criteria 16:07:11 #link https://fedoraproject.org/wiki/Fedora_30_Final_Release_Criteria 16:09:44 we have: 16:09:44 #info 3 Proposed Blockers 16:09:44 #info 5 Accepted Blockers 16:09:52 for Final 16:09:58 #info we will start with proposed Final blockers 16:10:05 #topic (1691832) NFSISO test failed on f30 (20190320) 16:10:05 #link https://bugzilla.redhat.com/show_bug.cgi?id=1691832 16:10:05 #info Proposed Blocker, anaconda, ASSIGNED 16:10:52 that's new 16:10:59 so this affects installing from an ISO image accessed via NFS (which is a supported option) 16:11:06 installing from a *repo* accessed via NFS works 16:12:06 nothing to solve here, +1 blocker 16:12:12 Seems like an "out there" example, but seems clear given the cited criteria 16:12:24 +1 16:12:26 * sumantro is here 16:12:29 +1 16:12:32 +1 blocker 16:12:36 +1 16:13:40 offtopic: anyone know where `select all` went in F30 gnome terminal? it's MIA, I can't find it 16:13:56 i see it on the edit menu. 16:14:05 i don't have an edit menu 16:14:10 gone 16:14:26 proposed #agreed 1691832 - AcceptedBlocker (Final) - accepted as a violation of "The installer must be able to use all supported local and remote package and installer sources." 16:14:28 dunno, then. 16:14:37 ack 16:14:39 ack 16:14:41 ack 16:14:43 ack 16:14:44 ack 16:15:28 #agreed 1691832 - AcceptedBlocker (Final) - accepted as a violation of "The installer must be able to use all supported local and remote package and installer sources." 16:15:53 #topic (1683197) gdm Fails to load with "nomodeset" 16:15:53 #link https://bugzilla.redhat.com/show_bug.cgi?id=1683197 16:15:53 #info Proposed Blocker, gdm, ASSIGNED 16:16:09 so this is the bug we punted from beta by deciding we don't want the criterion there any more 16:16:20 given that we agreed at QA meeting just now to move the criterion to final, it seems we should accept this... 16:16:26 +1 blocker 16:16:33 it *is* GNOME-specific, but hey, that's our main desktop. 16:16:43 +1 16:16:44 yeah, +1 blocker 16:16:49 +1 16:19:34 proposed #agreed 1683197 - AcceptedBlocker (Final) - accepted as a violation of "The boot menu for all supported installer and live images should include an entry which causes both installation and the installed system to use a generic, highly compatible video driver (such as 'vesa'). This mechanism should work correctly, launching the installer or desktop and attempting to use the generic driver" (which is moving to Final) 16:19:43 ack 16:19:48 ack 16:20:00 ack 16:21:03 ack 16:21:11 #agreed 1683197 - AcceptedBlocker (Final) - accepted as a violation of "The boot menu for all supported installer and live images should include an entry which causes both installation and the installed system to use a generic, highly compatible video driver (such as 'vesa'). This mechanism should work correctly, launching the installer or desktop and attempting to use the generic driver" (which is moving to Final) 16:21:19 #topic (1691909) GDM fallback from Wayland to X11 no longer works because it takes too long to start gnome-shell (affects 'basic graphics mode' / nomodeset, maybe other cases) 16:21:20 #link https://bugzilla.redhat.com/show_bug.cgi?id=1691909 16:21:20 #info Proposed Blocker, gdm, NEW 16:21:38 this is another basic graphics issue I found in follow-on testing from the previous one 16:21:48 it affects GNOME on BIOS, probably most installs. 16:21:58 is this causing systems to fail to reach gdm? 16:22:07 it also affects some non-'basic mode' cases, most likely - it's possible any time the fallback from wayland to x11 is needed 16:22:10 it would do that, yes. 16:22:38 okay, I think wayland should work in basic video on uefi 16:22:47 but we're still blocking even on BIOS, so +1 16:22:54 I did not know how to reproduce it ... BIOS basic graphics mode did not work, but I was not sure if it was the previous bug or this one 16:23:24 but +1 blocker 16:23:43 +1 blocker 16:23:48 +1 blocker 16:23:58 lruzicka: to get around the previous bug, you build GDM with the patch that triggers it removed 16:24:04 i did that, expecting it to work...and ran into this instead 16:25:15 adamw, ok, I will let franta show me 16:25:29 proposed #agreed 1691909 - AcceptedBlocker (Final) - this is accepted as a violation of the 'basic' graphics requirement for Workstation on BIOS, it likely also affects other cases and is a showstopping bug whenever it happens 16:25:33 franta = frantisekz 16:25:37 ack 16:25:41 ack 16:26:09 lruzicka: i think https://koji.fedoraproject.org/koji/taskinfo?taskID=33677821 is the scratch build i did, it will get garbage-collected at some point though. 16:26:58 ack 16:27:04 #agreed 1691909 - AcceptedBlocker (Final) - this is accepted as a violation of the 'basic' graphics requirement for Workstation on BIOS, it likely also affects other cases and is a showstopping bug whenever it happens 16:27:20 #topic Accepted blockers 16:27:29 that's all the proposed blockers, let's have a quick check through the accepted blockers 16:27:50 #info 1690429 is clearly being worked on by workstation folks, fix should show up soon 16:28:15 #info 1688462 is with DNF and modularity folks, it's definitely on their radar, we will check in if a fix doesn't show up soon though 16:28:27 #info 1693397 is straightforward and fix is pending 16:28:38 #info 1666920 has been stale for some time... 16:28:43 #action adamw to poke anaconda team re 1666920 16:28:48 and systemd i guess. 16:28:53 #undo 16:28:53 Removing item from minutes: ACTION by adamw at 16:28:43 : adamw to poke anaconda team re 1666920 16:29:00 #action adamw to poke systemd team re 1666920 16:29:16 #info 1674045 is well known but again stale, adam will poke systemd 16:29:23 #action adamw to poke systemd team re 1674045 too 16:29:28 .bug 1692617 looks similar to 1674045 16:29:29 cmurf: HTTP Error 400: Bad Request - https://bugzilla.redhat.com/1692617 looks similar to 1674045 16:29:34 anyone have other thoughts / notes on those accepted blockers? 16:30:18 cmurf: yes, it looks like the same bug. just close it as a dupe, i guess. 16:31:48 1674045 is set to Rawhide does that matter? 16:32:03 it's not particularly important 16:32:14 is it still happening? 16:33:17 yes. 16:33:25 otherwise it would be closed. :P 16:33:32 i hadn't heard anything about dnf system-upgrade failures happening in the upgrade boot environment during testing, and then saw bug 1692617 which is reported just on friday 16:33:49 ok so it's a transient problem? 16:34:05 it happens over half the time in openqa tests. 16:34:15 wow 16:34:20 people report it quite frequently 16:34:23 the bug is full of comments 16:35:13 interesting - doesn't seem to affect gnome-software pk offline upgrades 16:35:47 well, because they don't involve a major systemd update as part of the transaction, presumably. 16:36:09 #topic Open floor 16:36:13 sounds like we're about done? 16:36:16 anyone got anything else? 16:37:22 nothing here! 16:37:35 no please 16:38:17 alrighty, thanks for coming everyone! 16:38:20 see you next time 16:38:21 #endmeeting