15:59:26 #startmeeting F21-blocker-review 15:59:26 Meeting started Wed Jul 16 15:59:26 2014 UTC. The chair is roshi. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:59:26 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:59:27 #meetingname F21-blocker-review 15:59:27 The meeting name has been set to 'f21-blocker-review' 15:59:29 #topic Roll Call 15:59:37 .hellomynameis jsmith 15:59:38 jsmith: jsmith 'Jared Smith' 15:59:47 * jsmith will be in and out 15:59:51 * nirik is lurking around. 15:59:55 * ignatenkobrain here 16:00:12 * kalev joins the lurkers club. 16:00:53 ahoyhoy 16:01:25 o/ 16:01:31 #topic Introduction 16:01:31 Why are we here? 16:01:31 #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:01:35 #info We'll be following the process outlined at: 16:01:37 #link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting 16:01:40 #info The bugs up for review today are available at: 16:01:42 #link http://qa.fedoraproject.org/blockerbugs/current 16:01:45 #info The criteria for release blocking bugs can be found at: 16:01:47 #link https://fedoraproject.org/wiki/Fedora_21_Alpha_Release_Criteria 16:01:48 * jreznik is here, just blocked on other meeting 16:01:50 #link https://fedoraproject.org/wiki/Fedora_21_Beta_Release_Criteria 16:01:53 #link https://fedoraproject.org/wiki/Fedora_21_Final_Release_Criteria 16:02:03 sounds good jreznik 16:02:12 * pwhalen is here 16:02:28 onto the proposed blockers :) 16:02:29 #topic (1117965) Fedora needs per-Product Configuration files 16:02:29 #link https://bugzilla.redhat.com/show_bug.cgi?id=1117965 16:02:31 #info Proposed Blocker, distribution, NEW 16:03:54 I'm +1 for this, it makes sense to get this ironed out before a release 16:04:14 +1 16:04:56 The firewall criteria works for me, but I feel like there should be a process criteria of some sort 16:05:02 workstation has https://fedoraproject.org/wiki/Workstation/Technical_Specification#Firewall in its criteria 16:05:25 i can kinda see the point here, but it seems rather indirect to me. it'd be clearer if the bug was 'the Server firewall configuration is not as it should be'. 16:05:41 yeah 16:05:42 this is kind of a background issue that prevents that bug being fixed, there's a level of indirection 16:06:32 that's true 16:06:36 * dgilmore is not really here 16:06:57 * adamw waves a hand right through dgilmore 16:07:08 though, the bug is aimed at a more general fix for other things as well 16:07:32 if it was just a firewall bug, they could end up fixing *just* the firewall example and nothing else 16:07:44 aiui anyway 16:08:24 makes sense to sort this out before alpha, but maybe reclassify as a freeze exception, not a blocker? 16:08:49 I would see the firewall not being right in server as a blocker, and this as a FE 16:09:01 but we'd need a new bug created 16:09:08 oh 16:09:17 any volunteers for secretary duty today? 16:10:38 * jsmith can't 16:11:00 * adamw can 16:11:13 thanks adamw :) 16:11:24 i'd see the firewall bug being a blocker and depending on this bug 16:11:31 so, thoughts on reclassifying this as a FE? 16:11:35 (our blocker tools handle that as you'd expect) 16:12:39 so how do we want to handle this, +1 on this being a blocker and file another bug depending on this one? 16:15:13 * tflink needs to put the blocker review meetings on his calendar 16:15:22 er, the other way around - firewall bug created, as a blocker and depending on this bug 16:15:52 I should make sure they're in fedocal as well 16:17:05 +1/0/-1? 16:19:05 are there other configuration things which are different? it sounds like firewalld was just an example 16:19:29 the layout would work in general 16:19:32 yeah - that was the impression I got as well 16:19:38 have all actual blocker bugs that require variant configuration depend on this bug 16:19:38 he eludes to that, but only one given 16:20:00 if we vote +1 blocker on a theoretical bug for server firewall config, I'll create it as part of secretary duty 16:20:47 +1 on theoretical bug blocker 16:21:04 it makes sense at a high level that each product needs a conf for this kind of stuff 16:21:11 +1 on not-yet-created firewall config bug 16:21:29 but we don't really have a "The process we use needs fixed" criteria for this specific bug to be a blocker, per se 16:21:56 which could potentially be a good idea to have with the .next stuff going on 16:22:51 right now, I think firewall is the only practical example, but we definitely want it for more things in the future 16:24:09 so I'm seeing 3 +1 on theoretical blocker bug 16:24:15 any more? 16:24:23 roshi: i don't think so, i think bug deps handle it fine. 16:24:37 +1 on theoretical blocker bug 16:24:48 httpd might be one concrete (but not-actually-yet-really) example -- gnome-user-share pulls it in to use for local-network file sharing, and the configuration for that is obviously different from a web server httpd config 16:25:08 (just for example. carry on with actual non-sidetracked meeting....) 16:25:17 mattdm: sure, so if httpd functions are release blocking, that bug could be a blocker and depend on the config bug too. 16:25:19 it all works. ;) 16:25:42 adamw: hmm okay :) 16:26:55 adamw: got a proposed #agreed for this? Not sure how to word it for this usecase... 16:27:27 #chair adamw pwhalen tflink 16:27:27 Current chairs: adamw pwhalen roshi tflink 16:27:41 propose #agreed 1117965 is not a blocker in itself, but needs to be fixed for an actual as-yet-unreported blocker bug (server firewall configuration) to be resolved. we will report the server firewall bug, accept it as a blocker, and have it depend on this bug. 16:28:01 ack 16:28:11 ack 16:28:13 ack 16:28:26 ack 16:28:32 ack 16:28:34 do i have a chair? 16:28:38 yup 16:28:42 #agreed 1117965 is not a blocker in itself, but needs to be fixed for an actual as-yet-unreported blocker bug (server firewall configuration) to be resolved. we will report the server firewall bug, accept it as a blocker, and have it depend on this bug. 16:28:46 thanks :) 16:28:52 ok, next bug 16:28:55 #topic (1088933) update grubby to support device tree options for arm 16:28:58 #link https://bugzilla.redhat.com/show_bug.cgi?id=1088933 16:29:01 #info Proposed Blocker, grubby, POST 16:30:59 dgilmore, looks like your patch needs to be reworked, have you had a chance to look at it ? 16:33:15 this is a pretty big requirement for arm systems - with out the fdtdir the system wont boot. 16:33:24 +1 16:33:25 pwhalen: i already know yes 16:33:29 need time to do so 16:33:31 it's a clear blocker imo 16:33:32 +1 16:34:00 +1 16:34:02 +1 16:35:11 proposed #agreed - 1088933 - AcceptedBlocker - This clearly violates the Alpha criteria: "All release-blocking images must boot in their supported configurations." 16:35:29 ack 16:35:30 ack 16:35:43 фсл 16:35:44 ack 16:35:58 ack 16:35:59 #agreed - 1088933 - AcceptedBlocker - This clearly violates the Alpha criteria: "All release-blocking images must boot in their supported configurations." 16:36:11 #topic (1119380) AttributeError: 'Flags' object has no attribute 'targetarch' 16:36:14 #link https://bugzilla.redhat.com/show_bug.cgi?id=1119380 16:36:16 #info Proposed Blocker, kexec-tools, NEW 16:36:59 +1 from me 16:37:22 not sure I understand what's going on 16:37:45 tflink: crash when using anaconda I think 16:37:45 is this a crash on startup or a metacrash? 16:37:49 anaconda is crashing on a depreciated flag? 16:38:17 on backtrace seems after start 16:38:18 pwhalen? 16:39:10 this happens right after choosing text install 16:39:19 yes. I'm right 16:40:06 pwhalen: on ARM? 16:40:12 so, violates "Installation interfaces" or installer must run? 16:40:22 i'd say installation interfaces, since it only affects text 16:40:22 * roshi didn't see it in the bug 16:40:23 installer must run 16:40:34 on arm - but i think i saw someone else mention it 16:40:45 https://github.com/daveyoung/kdump-anaconda-addon/pull/2/files 16:40:54 seems only ppc64 16:40:58 the crash was on a wandboard, so I assume it's arm 16:41:38 affects an x86_64 VM too 16:41:42 i guess it's all arches, on a text install 16:41:45 +1 blocker 16:41:48 +1 16:41:48 adamw: I think we will get this error with gui installation 16:41:50 yeah was going to say -- this isn't just arm 16:41:51 +1 16:41:53 ignatenkobrain: no, only text. 16:41:55 +1 -violates several criteria 16:41:58 it prevents the cloud images from getting made 16:42:06 (i think) 16:42:08 right, only on text. vnc install is working 16:42:22 adamw: ok. 16:42:27 if it prevents could images from getting made, then it's a clear blocker -- +1 from me 16:42:32 +1 16:43:29 i guess we could make the cloud images build with the gui instead of in text mode; I didn't expect it would ever have a negative impact! 16:43:34 :P 16:43:39 * adamw pokes roshi 16:43:42 * randomuser notices he was pinged, starts paying attention 16:43:44 proposed #agreed - 1119380 - AcceptedBlocker - This bug violates several Alpha criteria, most notably "Installation interfaces," which interferes with installation and cloud image creation. 16:43:59 I was typing :p 16:44:03 ack 16:44:07 ack 16:44:09 ack 16:44:19 ack 16:44:20 roshi: you should type faster! 16:44:21 ack 16:44:22 #agreed - 1119380 - AcceptedBlocker - This bug violates several Alpha criteria, most notably "Installation interfaces," which interferes with installation and cloud image creation. 16:44:31 someone from brno hand me that whip 16:44:56 do we want to go over the accepted blockers, or move to the FE? 16:45:08 delayed ack 16:45:09 I think we can move to FEs 16:45:25 it's early enough that we don't really need to do the FEs 16:45:31 yep 16:45:54 accepted blockers probably more significant 16:45:56 that's kinda what I was thinking - but didn't know if people didn't feel fulfilled with a blocker meeting that was *only* an hour 16:46:19 onto accepted blockers then :) 16:46:42 #topic (1111417) anaconda should depend on NetworkManager-wifi 16:46:42 #link https://bugzilla.redhat.com/show_bug.cgi?id=1111417 16:46:42 #info Accepted Blocker, anaconda, MODIFIED 16:47:05 oh. 16:47:31 I don't see why anaconda should depend on a wifi support package 16:47:35 looks like it's on track 16:47:44 it should probably just be added to relevant products / spins in comps? 16:48:41 but when I want to install server from wifi? :P 16:49:05 cloud yes. but that's only for gui package, so I think it's correct fix 16:50:17 in the GUI subpackage seems like the right place 16:50:34 kalev: no, anaconda dep is the correct thing here. 16:50:47 kalev: it's to ensure you can use a wifi connection during installation. 16:50:47 ignatenkobrain, you gest, but I've had to do some interesting things... 16:51:02 as have I :) 16:51:12 and yeah, this is on track (at last) 16:51:20 for in home local stuff? wireless is more and more common for servers I would guess 16:51:35 for those people who have servers in their house doing things :P 16:51:51 well, things are on track - nothing to do for this one 16:51:55 like my r-pi on wifi 16:51:58 moving onto the next! 16:52:02 go go go ! 16:52:12 #topic (1109603) dracut unable to boot 3.16 most of the time 16:52:12 #link https://bugzilla.redhat.com/show_bug.cgi?id=1109603 16:52:13 #info Accepted Blocker, cloud-initramfs-tools, NEW 16:52:35 this one seems to be sitting around a bit 16:53:12 yeah 16:53:14 Yeah 16:53:25 A bit ol' +1 from me 16:53:28 it does, we're going to test images that do not use 'dracut-modules-growroot' to make sure that is the cause 16:53:58 so it is being worked on pwhalen? 16:54:50 we're trying to narrow it down, i'llping pbrobinson to see if he had time to push the change to the ks 16:55:01 sgtm 16:55:11 anyone got anything else on this one? 16:55:56 * roshi moves on then 16:55:59 #topic (1116478) [abrt] gnome-initial-setup: gdk_window_hide(): gnome-initial-setup killed by SIGSEGV 16:56:02 #link https://bugzilla.redhat.com/show_bug.cgi?id=1116478 16:56:05 #info Accepted Blocker, gnome-initial-setup, NEW 16:56:23 i'll give the desktop team a poke on this one 16:56:48 that works 16:57:53 next bug then - unless someone else has something 16:58:17 #topic (1115120) cryptsetup-1.6.5-1.fc21 breaks booting when using luks partitions 16:58:20 #link https://bugzilla.redhat.com/show_bug.cgi?id=1115120 16:58:22 #info Accepted Blocker, kernel, ASSIGNED 16:58:58 looks like things are moving along 16:59:02 should be fixed soon 16:59:49 anyone have any comments here? 17:00:01 interesting bug, but go next 17:00:04 two more accepted to look at 17:00:08 #topic (1116450) Can't login to fresh rawhide installation (2014-07-04) if SELinux is enforcing 17:00:11 #link https://bugzilla.redhat.com/show_bug.cgi?id=1116450 17:00:14 #info Accepted Blocker, lorax, MODIFIED 17:01:07 will fixed soonish 17:01:11 things are moving along 17:01:12 yeah 17:01:22 next ? 17:01:32 that's what I'm thinking 17:01:40 #topic (1044778) wandboard uboot missing serial line speed in console environment variable 17:01:43 #link https://bugzilla.redhat.com/show_bug.cgi?id=1044778 17:01:45 #info Accepted Blocker, uboot-tools, NEW 17:02:32 seems easyfix, but not fixed 17:02:51 I think we want ping maintainer 17:02:54 pwhalen: any movement on this one? 17:03:06 ah. Dennis 17:03:31 in the works and expected soon 17:03:49 https://bugzilla.redhat.com/show_bug.cgi?id=1116450 should be fixed already, btw 17:04:06 if anyone's seeing it in images dated, oh, 07-14 or later, that might be a problem (the fixed lorax landed 07-12) 17:04:39 good to know 17:05:10 well, that's it for accepted blockers 17:05:26 since this one is in the works 17:06:36 #topic Open Floor 17:06:47 anyone have anything for open floor? 17:07:05 PANIC 17:07:13 adamw: KERNEL ? 17:07:20 ;) 17:07:21 COLONEL 17:07:52 adamw: COLONEL KERNEL PANIC... okay. 17:09:08 well, if no one has anything I suppose I'll light the fuse... 17:09:12 roshi: when we will move to FEs ? 17:09:21 ignatenkobrain: bit closer to freeze time 17:09:25 too soon for FE's really 17:09:35 adamw: roshi: ah. ok. 17:09:44 I would imagine this gets fixed before we ever get to it anyway 17:10:55 * roshi sets the Olde Timey powder fuse 17:12:22 booooo 17:12:27 quantum fuses are where it's at, man. 17:12:33 i finished this meeting before it even *started*. 17:13:04 we just have a bunch of them laying around, they never get used 17:13:54 the thing with the quantum fuse is you never know if it really ended or just ended up in a super position of ended as well as not ended 17:14:21 physicists call that 'open floor phase' 17:14:31 ah 17:15:07 well, thanks for coming folks! 17:15:13 #endmeeting