16:01:04 #startmeeting F23-blocker-review 16:01:04 Meeting started Mon Jul 20 16:01:04 2015 UTC. The chair is roshi. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:04 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:01:04 #meetingname F23-blocker-review 16:01:05 The meeting name has been set to 'f23-blocker-review' 16:01:06 #topic Roll Call 16:01:13 who's around for some blockery goodness? 16:01:21 * lbrabec is lurking 16:01:24 * satellit listening 16:01:41 * garretraziel is lurking 16:01:44 * pschindl is here 16:01:53 * pwhalen is here 16:02:23 #chair lbrabec satellit_e adamw garretraziel pschindl pwhalen 16:02:23 Current chairs: adamw garretraziel lbrabec pschindl pwhalen roshi satellit_e 16:02:33 #topic Introduction 16:02:33 Why are we here? 16:02:33 #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:02:45 * kparal is somewhat here 16:02:47 oh, we started? 16:02:58 * danofsatx isn't paying attention to clocks 16:03:02 #info We'll be following the process outlined at: 16:03:02 #link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting 16:03:02 #info The bugs up for review today are available at: 16:03:03 #link http://qa.fedoraproject.org/blockerbugs/current 16:03:03 #info The criteria for release blocking bugs can be found at: 16:03:03 #link https://fedoraproject.org/wiki/Fedora_23_Alpha_Release_Criteria 16:03:03 #link https://fedoraproject.org/wiki/Fedora_23_Beta_Release_Criteria 16:03:03 #link https://fedoraproject.org/wiki/Fedora_23_Final_Release_Criteria 16:03:04 shouldn't be too long a meeting today, we have 5/1/1 proposals to go over 16:03:04 (for alpha/beta/final resp) 16:03:15 clocks are for the meek and timid 16:03:43 let's get started then :) 16:03:44 #topic (1243543) __init__.py:102:require_version:ValueError: Namespace OSTree not available 16:03:44 eggzackerly 16:03:47 #link https://bugzilla.redhat.com/show_bug.cgi?id=1243543 16:03:49 #info Proposed Blocker, anaconda, MODIFIED 16:04:12 i think we can actually close this. 16:04:34 * adamw does so 16:04:44 sweet 16:04:46 agreed. next! 16:04:52 #topic (1244431) anaconda 23.16-1 liveinst "failed to save storage destination" reverts to Automatic partition selected 16:04:55 #link https://bugzilla.redhat.com/show_bug.cgi?id=1244431 16:04:57 #info Proposed Blocker, anaconda, NEW 16:05:44 i've just reproduced this with an empty disk, looks like autopart is just broken for UEFI 16:05:49 (probably some problem with /boot/efi) 16:06:06 so i'd be +1 16:06:14 +1 16:06:18 * satellit there is a workarround in custom 16:06:20 seems like a clear +1 for me 16:06:24 +1 16:06:32 +1 16:06:33 agreed, +1 16:06:44 satellit: sure, for alpha we require autopart to work though 16:07:05 k 16:07:05 +1 16:07:20 proposed #agreed - 1244431 - AcceptedBlocker Alpha - This bug is a clear violation of the following Alpha criterion: "The installer must be able to complete an installation using any supported locally connected storage interface." 16:07:30 eh, i think we have a better criterion 16:07:31 gimme a sec 16:07:52 kk 16:07:55 i'd say it's a violation of "The installer must be able to complete an installation to a single disk using automatic partitioning. " in the case of a UEFI system 16:08:01 ack 16:08:33 ack 16:08:34 proposed #agreed - 1244431 - AcceptedBlocker Alpha - This bug is a clear violation of the following Alpha criterion: "The installer must be able to complete an installation to a single disk using automatic partitioning." 16:08:43 ack 16:08:48 #agreed - 1244431 - AcceptedBlocker Alpha - This bug is a clear violation of the following Alpha criterion: "The installer must be able to complete an installation to a single disk using automatic partitioning." 16:09:01 who wants to secretarialize? 16:09:23 I can do that 16:09:32 thanks pschindl :) 16:09:40 #topic (1244023) [abrt] gnome-initial-setup: _g_log_abort(): gnome-initial-setup killed by SIGTRAP 16:09:43 #link https://bugzilla.redhat.com/show_bug.cgi?id=1244023 16:09:46 #info Proposed Blocker, gnome-initial-setup, NEW 16:11:17 +1 16:11:29 do we still see this with the 0717 nightly? 16:11:31 sigh, i need to go ping systemd folks about this... 16:11:32 roshi: yes. 16:11:48 +1 16:11:49 well, actually i dunno if i tried explicitly, but i don't think anyone fixed systemd in the mean time. 16:11:55 +1 16:12:13 +1 16:12:31 proposed #agreed - 1244023 - AcceptedBlocker Alpha - This bug is a clear violation of the following Alpha criterion: "A system installed with a release-blocking desktop must boot to a log in screen where it is possible to log in to a working desktop using a user account created during installation or a 'first boot' utility." 16:12:44 Are both systemd-timedated and timedatex installed in at least one of the blocking media? (I'm guessing that is the case, but couldn't readily tell from the bug.) 16:13:49 brunowolff: yes, i think they're probably in all of them. 16:13:55 systemd-timedated is part of systemd 16:14:33 +1 blocker 16:14:47 ack, nack, patch? 16:15:05 hum, or maybe just workstation. but at least workstation 16:15:07 ack 16:15:08 ack 16:15:18 ack 16:15:20 timedatex is required by chrony, anything that has chrony will have it, and chrony is part of ws. 16:15:20 #agreed - 1244023 - AcceptedBlocker Alpha - This bug is a clear violation of the following Alpha criterion: "A system installed with a release-blocking desktop must boot to a log in screen where it is possible to log in to a working desktop using a user account created during installation or a 'first boot' utility." 16:15:21 ack 16:15:32 #topic (1244558) Switch initial-setup to use python3 16:15:32 #link https://bugzilla.redhat.com/show_bug.cgi?id=1244558 16:15:33 #info Proposed Blocker, initial-setup, ASSIGNED 16:16:11 +1, arm images cant be configured 16:16:18 Is this actually breaking things or just pulling in python 2.7? 16:16:27 yeah, with the info that this breaks arm images i'm +1. 16:16:33 the rational in comment 5 makes sense to me 16:16:37 +1 16:16:40 +1 16:16:40 brunowolff: it's actually breaking things. the initial bug report was 'i-s doesn't run', it was duped to this. 16:17:18 +1 16:17:23 i guess we could note that the blocker requirement is 'make i-s run', not necessarily 'port it to python3' 16:17:35 +1 to ^^ 16:18:12 proposed #agreed - 1244558 - AcceptedBlocker Alpha - This bug is a violation of the following Alpha criterion for ARM: "A working mechanism to create a user account must be clearly presented during installation and/or first boot of the installed system." Completing the port to Python3 will make i-s run and satisfy the criterion. 16:18:21 Are the arm releases in sync with the other arches now, or still being released somewhat later? 16:18:21 ack 16:18:33 brunowolff: they've been sycned ever since arm went primary. 16:18:42 ack 16:18:43 ack 16:18:45 Ack 16:18:48 ack 16:18:52 #agreed - 1244558 - AcceptedBlocker Alpha - This bug is a violation of the following Alpha criterion for ARM: "A working mechanism to create a user account must be clearly presented during installation and/or first boot of the installed system." Completing the port to Python3 will make i-s run and satisfy the criterion. 16:19:00 #topic (1243168) Entire system mislabelled on fresh Rawhide install 16:19:03 #link https://bugzilla.redhat.com/show_bug.cgi?id=1243168 16:19:05 #info Proposed Blocker, lorax, NEW 16:19:58 +1 16:20:16 +1 16:20:21 +1 16:20:42 Is this just rawhide, or F23 also? 16:20:56 +1 16:21:06 0720 boot iso branched 16:21:15 danofsatx: f23 too, i filed before branching 16:21:22 proposed #agreed - 1243168 - AcceptedBlocker Alpha - This bug is a clear violation of the following criteria: "A system installed without a graphical package set must boot to a state where it is possible to log in through at least one of the default virtual consoles." 16:21:22 +1 16:21:23 roger that 16:21:25 +1 16:21:32 ack 16:21:34 ack 16:21:38 this is the one that stops you logging in after install 16:21:39 ack 16:21:39 ack 16:21:44 ack 16:21:52 #agreed - 1243168 - AcceptedBlocker Alpha - This bug is a clear violation of the following criteria: "A system installed without a graphical package set must boot to a state where it is possible to log in through at least one of the default virtual consoles." 16:21:52 ack 16:22:02 #topic (1240802) Can't unlock an encrypted root partition using caps lock key 16:22:05 #link https://bugzilla.redhat.com/show_bug.cgi?id=1240802 16:22:08 #info Proposed Blocker, systemd, NEW 16:22:31 as this behaviour is same as f22 and it involves fiddling with caps lock i'm inclined to not be +1 16:22:37 i'd at least want to investigate a bit further 16:22:58 This seems more a common bugs thing. 16:23:11 meh...usability. if it doesn't get fixed, it's a common bug. 16:23:36 the caps lock indicator might be off when playing with it during early boot 16:23:41 Not many people are going to use caps lock to do shifts when booting. And this is only alpha. 16:24:09 brunowolff: we vote for other milestones as well 16:24:34 I hadn't considered other keyboard layouts, but the capslock key on any keyboard of mine has only ever been hit on accident 16:24:45 as far as I'm concerned, it's a waste of a key 16:24:48 I'd like to have this confirmed on bare metal first 16:24:55 kparal, agreed 16:24:55 punt? 16:25:22 yeah, let's punt and do a bit of testing with different layouts and things 16:25:33 Well even for final there is normally (unless your shift keys are broken) an easy work around and it should be fixable after release. 16:25:39 I'd say repropose to Final and ask for bare metal verification 16:25:54 kparal: if you can get folks to fiddle around with it a bit that'd be great. and yeah, it seems clearly no more serious than Final 16:26:20 adamw: ok, bookmarking it 16:26:30 proposed #agreed - 1240802 - Punt - This bug could use some more testing of different keyboard layouts on bare metal. 16:27:25 ack 16:27:25 ack 16:27:28 I think you want to add reprose for final in the proposed. 16:27:32 ack 16:27:34 ack 16:27:45 ack 16:28:06 proposed #agreed - 1240802 - Punt - This bug could use some more testing of different keyboard layouts on bare metal. If confirmed, please move this Blocker to Final. 16:28:19 ack 16:28:43 switch to Final right away, I think 16:28:51 as part of the secretary process 16:28:56 that works 16:29:06 ack to the first draft, pschindl to move bug 16:29:06 ack 16:29:07 good? 16:29:13 sure 16:29:19 #agreed - 1240802 - Punt - This bug could use some more testing of different keyboard layouts on bare metal. 16:29:37 onto the beta proposal 16:29:37 #topic (1242610) TypeError: __init__() got an unexpected keyword argument 'model' 16:29:40 #link https://bugzilla.redhat.com/show_bug.cgi?id=1242610 16:29:43 #info Proposed Blocker, anaconda, NEW 16:30:37 +1 16:30:50 firmware raid is bios raid, right? 16:30:56 +1 16:30:57 we have one machine to verify this with 16:31:24 kparal: yep 16:31:27 +1 in general, unless other people can't reproduce it 16:31:35 kparal: it'd be good if you can see if it happens there too, indeed 16:31:44 roger 16:31:47 reads rather like a coding error 16:31:53 proposed #agreed - 1242610 - AcceptedBlocker Beta - This bug is a clear violation of the following Beta criterion: "The installer must be able to detect and install to hardware or firmware RAID storage devices." 16:32:00 ack 16:32:26 ack 16:32:37 ack 16:32:44 #agreed - 1242610 - AcceptedBlocker Beta - This bug is a clear violation of the following Beta criterion: "The installer must be able to detect and install to hardware or firmware RAID storage devices." 16:33:00 #topic (1241704) systemd no longer able to run checkisomd5 in initramfs 16:33:03 #link https://bugzilla.redhat.com/show_bug.cgi?id=1241704 16:33:05 #info Proposed Blocker, systemd, NEW 16:33:48 i think this should be Final 16:33:50 is it? 16:33:51 +1 16:33:51 This might be something to put on common bugs for the alpha release even if it only blocks beta. 16:33:54 it is 16:33:57 then +1 16:34:05 final, i mean 16:34:20 I was a bit slow typing, that comment was for the raid bug. 16:34:32 +1 16:34:32 +1 16:34:55 +1 16:35:10 +1 16:35:27 proposed #agreed - 124704 - AcceptedBlocker Final - This bug is a violation of the following Final criterion: "Validation of install media must work correctly for all release-blocking images." 16:35:40 ack 16:35:41 ack 16:35:53 ack 16:36:02 #agreed - 124704 - AcceptedBlocker Final - This bug is a violation of the following Final criterion: "Validation of install media must work correctly for all release-blocking images." 16:36:06 well, that's it 16:36:09 #topic Open Floor 16:36:15 that was super quick 16:36:58 yup 16:37:26 * roshi sets fuse 16:37:29 3... 16:37:39 BOOM! 16:37:49 lol 16:37:53 2... 16:37:55 I will update bugs right now. 16:38:07 thanks for coming folks 16:38:09 1... 16:38:27 #endmeeting