16:01:47 #startmeeting F22-blocker-review 16:01:47 Meeting started Mon Mar 16 16:01:47 2015 UTC. The chair is roshi. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:47 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:01:47 #meetingname F22-blocker-review 16:01:47 The meeting name has been set to 'f22-blocker-review' 16:01:48 #topic Roll Call 16:02:11 ahoy to the oy 16:02:23 or possibly an oy to the hoy? 16:02:23 * nirik is lurking around, ping if I can assist on anything. 16:02:27 who's around? 16:02:34 * pschindl is here 16:03:58 * jreznik is here 16:04:06 ahoj 16:04:10 * danofsatx is here, mostly. 16:04:30 * danofsatx really needs to kill plasmashell and wishes these meetings would hurry up and end 16:04:35 #chair adamw nirik pschindl jreznik danofsatx kparal 16:04:35 Current chairs: adamw danofsatx jreznik kparal nirik pschindl roshi 16:04:39 #topic Introduction 16:04:39 Why are we here? 16:04:39 #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:04:43 #info We'll be following the process outlined at: 16:04:45 #link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting 16:04:48 #info The bugs up for review today are available at: 16:04:50 #link http://qa.fedoraproject.org/blockerbugs/current 16:04:53 #info The criteria for release blocking bugs can be found at: 16:04:55 #link https://fedoraproject.org/wiki/Fedora_22_Alpha_Release_Criteria 16:04:58 #link https://fedoraproject.org/wiki/Fedora_22_Beta_Release_Criteria 16:05:01 #link https://fedoraproject.org/wiki/Fedora_22_Final_Release_Criteria 16:05:04 volunteer for secretarializing? 16:05:15 * kparal lurks 16:05:31 * danofsatx takes it for today 16:05:36 roshi: please note I just nominated https://bugzilla.redhat.com/show_bug.cgi?id=1202444 16:05:38 sweet, thanks :) 16:05:43 will do 16:06:05 alright, I'm showing 6/2 for Beta/Final 16:06:07 #topic (1191842) unable to continue the installation after type into a weak password 16:06:10 #link https://bugzilla.redhat.com/show_bug.cgi?id=1191842 16:06:13 #info Proposed Blocker, anaconda, NEW 16:06:19 I see 7 for beta 16:06:48 heh, guess I missed the update window 16:06:54 I see 7 now too 16:07:06 kparal's bug is in there 16:07:06 good 16:07:08 seems to be notabug 16:07:14 oh, wait 16:07:16 * adamw reads on 16:07:35 this is FESCo's automatic blocker, right? 16:08:11 yeah 16:08:15 invoked by fesco, ergo +1 16:08:23 yep 16:08:25 +1 16:08:26 +1 16:08:29 yes, sgallagh reopened based on FESCO's decision. 16:08:32 +1 for me. 16:08:32 +1 16:08:35 alpha criterion "All bugs deemed by FESCo to block the milestone release must be fixed. " 16:09:00 +1 16:09:38 proposed #agreed - 1191842 - AcceptedBlocker Beta - This bug was nominated by FESCo as a blocker, violating the criterion: "All bugs deemed by FESCo to block the milestone release must be fixed." 16:09:47 * nirik notes he's not sure how they can implement what was asked, but I'm sure we will sort something out. 16:09:55 ack 16:09:56 ack 16:10:00 ack 16:10:07 #agreed - 1191842 - AcceptedBlocker Beta - This bug was nominated by FESCo as a blocker, violating the criterion: "All bugs deemed by FESCo to block the milestone release must be fixed." 16:10:20 #topic (1200539) Boot fails because grub initrd entry isn't generated 16:10:23 #link https://bugzilla.redhat.com/show_bug.cgi?id=1200539 16:10:25 #info Proposed Blocker, anaconda, NEW 16:11:44 this is /boot-on-btrfs-subvol 16:11:53 seems like fix-it-or-disallow-it territory 16:13:14 +1 16:13:45 So what are we voting on? 16:13:57 +1 == It must be fixed? 16:13:58 seems to meet https://fedoraproject.org/wiki/Fedora_22_Beta_Release_Criteria#Custom_partitioning pretty well for me, as currently written 16:14:00 sgallagh: blocker, it's just implementation 16:14:12 yeah 16:14:13 sgallagh: no, +1 == blocker 16:14:14 or +1 == it must not be able to get into that situation? 16:14:25 +1 blocker for me 16:14:27 sgallagh: whether anaconda team choose to fix it by fixing it or disallowing /boot-on-subvol again is up to them 16:14:29 blocker. 16:14:31 ok 16:14:55 +1 blocker 16:15:13 autopart shouldn't be generating an unbootable partition scheme 16:15:31 +1 16:16:08 sgallagh: it's not autopart i don't think 16:16:15 no, it isn't 16:16:17 it's not 16:16:25 but the criteria do cover manual part to an extent at beta 16:16:55 I misread 16:17:29 proposed #agreed - 1200539 - AcceptedBlocker Beta - This bug is a clear violation of the Beta criterion: "Create mount points backed by ext4 partitions, LVM volumes or btrfs volumes..." 16:17:56 patch 16:18:05 proposed #agreed - 1200539 - AcceptedBlocker Beta - This bug is a clear violation of the Beta criterion: "When using the custom partitioning flow, the installer must be able to: Create mount points backed by ext4 partitions, LVM volumes or btrfs volumes..." 16:18:42 patch 16:19:01 go for it, you have chair as well 16:19:14 proposed #agreed - 1200539 - AcceptedBlocker Beta - This bug is a clear violation of the Beta criterion: "When using the custom partitioning flow, the installer must be able to: Create mount points backed by ext4 partitions, LVM volumes or btrfs volumes AND Reject or disallow invalid disk and volume configurations without crashing." 16:19:18 ack 16:19:27 (well, maybe 'assign mount points' too, but close enough) 16:19:40 ack 16:19:44 ack 16:20:34 ack 16:21:01 #agreed - 1200539 - AcceptedBlocker Beta - This bug is a clear violation of the Beta criterion: "When using the custom partitioning flow, the installer must be able to: Create mount points backed by ext4 partitions, LVM volumes or btrfs volumes AND Reject or disallow invalid disk and volume configurations without crashing." 16:21:10 #topic (1201120) DeviceTreeError: could not find parent for subvol 16:21:13 #link https://bugzilla.redhat.com/show_bug.cgi?id=1201120 16:21:16 #info Proposed Blocker, anaconda, NEW 16:22:34 seems pretty cut and dry for me, but I'd like to see a reproducer 16:23:30 yeah, I'd like to see a confirmation myself. 16:23:44 this almost seems to be a one-off, including the comment from cmurf 16:23:57 s/including/considering 16:24:13 and maybe with pretty uncommon setup (I know it should work but) 16:24:22 +1 punt for more testing 16:24:36 well, with btrfs, this isn't all that an uncommon setup. 16:24:39 anyone have a box laying around with a bunch of btrfs volumes? 16:24:59 I did, until /dev/sdb decided to start corrupting sectors. 16:26:25 no, but shouldn't be crazy hard to invent one 16:26:38 votes? 16:26:40 looking at the code though i'm not entirely sure it's actually to do with having a 'bunch of' subvols 16:26:50 probably punt for more details... 16:27:21 +1 punt. 16:27:45 +1 punt 16:27:47 proposed #agreed - 1201120 - Punt - The QA team would like some more details on reproducing this bug to get more testing before voting on it's blocker status. 16:27:54 ack 16:29:55 ack 16:30:03 ack 16:30:08 also more details from anaconda devs on what's actually going on here 16:30:28 ack 16:30:37 #agreed - 1201120 - Punt - The QA team would like some more details on reproducing this bug to get more testing before voting on it's blocker status. 16:30:40 #topic (1201411) TypeError: execve() arg 3 contains a non-string value 16:30:43 #link https://bugzilla.redhat.com/show_bug.cgi?id=1201411 16:30:46 #info Proposed Blocker, anaconda, ON_QA 16:31:23 this makes anaconda to crash on all hidpi displays, I'd say it's becoming common these days and fix is simple 16:31:46 looks like it's fixed already 16:31:56 yep it should be 16:31:59 +1 blocker with the increasing prevalence of hidpi laptops 16:31:59 https://bugzilla.redhat.com/show_bug.cgi?id=1201411#c11 16:32:32 the fix should be in tc2 16:32:40 i'll add a note for people to test and confirm 16:32:40 adamw: I'll try it 16:32:54 so, is it still a blocker then? 16:32:57 +1 16:33:03 +1 blocker 16:33:18 danofsatx: yes. 16:33:21 +1 16:33:32 ok, +1 then. 16:33:44 danofsatx: the update hasn't been tested or pushed stable yet; plenty of things could turn out to be an issue. unless it's already fixed *in a package already pushed stable*, we vote on it 16:33:49 proposed #agreed - 1201411 - AcceptedBlocker Beta - With the rise of hdipi setups, this bug is a conditional blocker of the criterion: "" 16:34:00 arg 16:34:03 paste fail 16:34:15 proposed #agreed - 1201411 - AcceptedBlocker Beta - With the rise of hdipi setups, this bug is a conditional blocker of the criterion: "When using a dedicated installer image, the installer must be able to complete an installation using the text, graphical and VNC installation interfaces." 16:34:27 ack 16:34:34 ack 16:34:49 ack 16:34:54 #agreed - 1201411 - AcceptedBlocker Beta - With the rise of hdipi setups, this bug is a conditional blocker of the criterion: "When using a dedicated installer image, the installer must be able to complete an installation using the text, graphical and VNC installation interfaces." 16:35:03 #topic (1202444) OverflowError: long too big to convert 16:35:03 #link https://bugzilla.redhat.com/show_bug.cgi?id=1202444 16:35:04 #info Proposed Blocker, anaconda, NEW 16:35:07 * jreznik would say QA now can ask for budget for HiDPI displays :) 16:35:20 put me on that list :p 16:36:02 * adamw planning to buy a couple for his desktop sometime soon... 16:36:16 so many kparal's in the bug... another user and it's still kparal 16:36:25 looks like kparal tested thouroughly enough. +1 blocker. 16:36:27 dupe 16:36:35 https://bugzilla.redhat.com/show_bug.cgi?id=1200812 16:36:40 dupe? damn.... 16:36:41 yo dawg, i heard you liked kparal 16:37:42 that's what you get when I need to test something completely different, and everything just breaks apart under my hands 16:38:07 so there's a good old developer dingdong going here and they haven't answered the question of what actually triggers this 16:38:31 reading between the lines, though, i'm gonna bet it's something like 'requesting maximum possible size for an xfs partition' 16:38:35 I'd say we block on 1200812 16:38:41 I couldn't get through the installation, it always broke 16:38:44 agreed 16:38:53 (i.e. in the kickstart that causes #1200812 it's logvol / --fstype=xfs --size=256 --name=lv_root --vgname=vg --grow 16:39:21 I have a default F22 installation on one of the VMs 16:39:27 that triggered this 16:39:34 maybe F21 16:40:18 kparal: with the server netinst? 16:40:26 (or dvd - a server offline install image?) 16:40:53 netinst 16:41:07 TC2 16:41:08 right, so on server, default fs is xfs 16:41:15 ah 16:41:18 haven't realized 16:41:25 and default partitioning will do a 'make / as big as possible', i think 16:41:37 so, yeah, i'm +1, anyway, seems like this'll happen a lot 16:41:51 +1 16:41:55 seems like, +1 blocker 16:42:38 oh, to be clear, i'm +1 for 1200812 , the parent of all these. 16:42:43 block on 1200812 16:42:45 kk 16:43:03 yep, I thought I vote on it 16:43:17 #info this bug is a dupe of 1200812, so we're voting against it's parent bug 16:43:18 +1 for 1200812 16:44:06 which criteria, though? 16:44:52 proposed #agreed - 1200812 - AcceptedBlocker Beta - As proposed on RHBZ#1202444, this bug is a clear violation of the Beta criterion: "Cleanly install to a disk with a valid ms-dos or gpt disk label and partition table which contains existing data and sufficient unpartitioned space for a Fedora installation." 16:45:03 that one if the reproducer has existing data 16:45:09 or the alpha one if it reproduces on an empty disk 16:45:21 not super important either way 16:45:56 * roshi just wanted to use "Violates the usual "work with common disk contents" criteria" 16:46:11 handwavy hand wave 16:46:25 it's broke, dawg 16:46:45 danofsatx: i vote +100 on adding that as an alpha criterion 16:46:49 "the system is down, yo" 16:47:02 ack 16:47:12 oh yeah, ack 16:48:17 * danofsatx highly recommends the BBC show The IT Crowd 16:48:18 ack 16:48:23 #agreed - 1200812 - AcceptedBlocker Beta - As proposed on RHBZ#1202444, this bug is a clear violation of the Beta criterion: "Cleanly install to a disk with a valid ms-dos or gpt disk label and partition table which contains existing data and sufficient unpartitioned space for a Fedora installation." 16:48:27 i'm guessing we've all seen it. 16:48:41 for sure :) 16:48:44 just making sure ;) 16:48:50 #topic (1201229) cloud-init does not do the resize 16:48:51 #link https://bugzilla.redhat.com/show_bug.cgi?id=1201229 16:48:51 #info Proposed Blocker, cloud-init, NEW 16:49:47 this is a manifestation of https://bugzilla.redhat.com/show_bug.cgi?id=1197894 16:50:08 I'm almost 100% sure that's it - since there is *no* resize right now anywhere 16:50:43 -1, mark it as a dupe 16:50:45 yep, dupe 16:51:50 oh, so on that last bug, i just did an openQA run against tc2 and every single test failed i think because of that bug. soo, definitely a blocker. :P 16:52:12 which last bug? 16:52:13 heh 16:52:18 the one before this one 16:52:18 1200812 16:52:25 * roshi ducks 16:53:51 proposed #agreed - RejectedBlocker Beta - This bug is a duplicate of an existing blocker - RHBZ#1197894. 16:54:08 ack 16:55:19 ack 16:55:30 ack 16:55:32 #agreed - RejectedBlocker Beta - This bug is a duplicate of an existing blocker - RHBZ#1197894. 16:55:44 #topic (1202113) initial-setup graphical service isn't enabled after installation of mate live spin f22 16:55:47 #link https://bugzilla.redhat.com/show_bug.cgi?id=1202113 16:55:49 #info Proposed Blocker, initial-setup, NEW 16:56:05 so we seem to have issues affecting lxde and mate here, but unless someone can reproduce on kde it shouldn't be a blocker 16:56:50 yeah 16:57:04 -1 w/ that logic 16:58:08 agreed": -1, only non-blocking DE's affected at the moment. 16:59:02 I'd like to try TC2 for that HiDPI issue, so I'll check this too 16:59:11 proposed #agreed - 1202113 - RejectedBlocker - This bug only seems to apply to non-blocking DE's and therefore isn't considered a blocker. 16:59:42 ack 16:59:47 ack 17:02:22 #agreed - 1202113 - RejectedBlocker - This bug only seems to apply to non-blocking DE's and therefore isn't considered a blocker. 17:02:29 onto the two final proposals 17:02:39 #topic (1202247) firefox 36 broke langpack detection for new profiles 17:02:42 #link https://bugzilla.redhat.com/show_bug.cgi?id=1202247 17:02:45 #info Proposed Blocker, firefox, NEW 17:05:12 hmmm....the fix hasn't been tested on F22 yet, so until confirmation of fix I'm +1 blocker 17:05:38 this doesn't look like a beta blocker to me. 17:05:42 all i18n stuff is final, isn't it? 17:05:57 oh yeah, proposed as final 17:06:01 this is a final 17:06:10 +1 final 17:06:34 the closest criterion is "All critical path actions on release-blocking desktops must correctly display all sufficiently complete translations available for use. " 17:06:50 I'm +1 final, since it's a nice logical extension of the installer translation criteria 17:07:06 and I'd propose we add translations to the workstation guidelines: http://fedoraproject.org/wiki/Workstation/Guidelines/Applications_and_Launchers 17:07:09 well. we have the critpath criterion as an *explicit* extension. 17:07:11 is FF installed by default with Workstation, or just epiphany? 17:07:18 firefox, always has been 17:07:23 ok 17:07:25 browser use isn't technically critpath though, i don't think 17:07:28 * danofsatx doesn't test workstation ;) 17:07:36 I didn't think it was, adamw 17:07:41 strictly speaking i'd have to be -1 to this as the criteria stand, i think. 17:07:53 yeah 17:08:12 arguably we left other things out of the criteria as 'they could be fixed with an update', while perhaps this can't 17:08:12 but I think this was an oversight in criteria, not a planned "we don't want to block on this" 17:08:24 (because by the time you get the update your profile is probably locked to english) 17:09:00 firefox is in the critical-path-apps group 17:10:10 danofsatx: That's actually because of its engine, not the browser itself. 17:10:14 (subtle but important) 17:10:17 right 17:10:40 the critical path actions are those defined on the policy page, not 'anything you can do with the packages that wind up in the critpath group' 17:10:45 ok. I was only trying to make the point that FF is critical path. 17:10:56 i think for now i'd vote -1 and suggest we discuss a criterion change on-list... 17:10:57 I think this could fall under the Default functionality criterion 17:11:02 obviously this ought to get fixed anyway 17:11:09 under the 'basic functionality' 17:11:18 I'd consider loading translations part of that 17:11:44 For the record, I'd say that loading translations might reasonably be a Final criterion 17:11:51 It's not *strictly* basic functionality. 17:12:35 I think it ought to be, but we haven't run into this so didn't think about it or thought it was already covered (probably) 17:13:25 stictly following the criteria, I'm -1 17:13:28 but +1 FE 17:13:47 and +1 adding a criteria for this, or putting it in the WS guidelines for default apps 17:13:51 Yeah, I'm fine with +1 FE 17:15:05 proposed #agreed - 1202247 - RejectedBlocker AcceptedFreezeException Final - This bug doesn't directly violate any criteria, but if a fix presents itself during freeze it would be accepted. 17:15:22 I'm hesitant for FE due to what adamw said above - "because by the time you get the update your profile is probably locked to english" 17:16:04 but, I'm obvioulsy outvoted, so ack. 17:16:22 I'd like it as a blocker - but we don't have a criteria for it 17:16:57 ack. Better FE than nothing. 17:17:01 ack 17:17:07 i suspect it'll go away and we won't have to worry 17:17:19 we can consider some kind of criterion revision on the list 17:17:43 #agreed - 1202247 - RejectedBlocker AcceptedFreezeException Final - This bug doesn't directly violate any criteria, but if a fix presents itself during freeze it would be accepted. 17:17:55 last one 17:17:56 #topic (1200161) Non-Fatal SELINUX Faults exist during bootup of 22_Alpha_RC3 17:17:59 #link https://bugzilla.redhat.com/show_bug.cgi?id=1200161 17:18:02 #info Proposed Blocker, rng-tools, NEW 17:20:38 +1 17:20:40 "There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop. " 17:20:45 +1 17:20:47 +1 17:21:12 proposed #agreed - 1200161 - AcceptedBlocker - This bug is a clear violation of the Final criterion: "There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop." 17:21:45 assuming it's still happening, +1 final, yep 17:21:46 ack 17:21:51 ack 17:21:56 #agreed - 1200161 - AcceptedBlocker - This bug is a clear violation of the Final criterion: "There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop." 17:22:01 #topic Open Floor 17:22:08 anything for open floor? 17:22:11 * roshi has nothing 17:22:25 one question: 17:23:18 bug 1191842 violates alpha crieteria. Should it be annotated as alpha, or beta as discussed? 17:23:40 beta - since alpha is out already 17:23:41 that was the FESCO/anaconda password bug 17:23:45 oh, dug 17:23:45 can't really block it 17:23:48 duh, even 17:24:03 :) 17:24:15 * roshi sets the fuse... 17:24:19 3... 17:24:24 * danofsatx runs fer da hilz 17:24:33 thanks for secretarializing danofsatx! 17:24:44 thanks dan! 17:24:54 once you get that time machine fixed up we can do retroactive blockers :P 17:25:22 2... 17:25:46 my son is working on it. His Lego model is almost working, but we lost the cat. 17:26:19 hehe 17:26:25 we think it's in 1892, but we're not sure. 17:26:33 1... 17:26:58 it's probably chilling with schrodingers cat somewhere in the ether 17:27:14 thanks for coming folks! 17:27:17 #endmeeting