16:03:24 #startmeeting F23-blocker-review 16:03:24 Meeting started Mon Aug 24 16:03:24 2015 UTC. The chair is roshi. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:03:24 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:03:24 #meetingname F23-blocker-review 16:03:24 #topic Roll Call 16:03:24 The meeting name has been set to 'f23-blocker-review' 16:03:33 who's around? 16:05:14 hey, who you calling round? 16:05:33 * adamw 's asquare 16:06:22 * roshi is orthoganol 16:06:50 to what? 16:06:52 * Corey84 here 16:07:00 exactly 16:07:26 #chair adamw Corey84 danofsatx kparal pschindl 16:07:26 Current chairs: Corey84 adamw danofsatx kparal pschindl roshi 16:07:28 likely to be in and out tho finishing some blog posts for fosscon and other things 16:07:59 sounds good Corey84 16:08:03 #topic Introduction 16:08:03 Why are we here? 16:08:03 #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:08:07 #info We'll be following the process outlined at: 16:08:10 #link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting 16:08:12 #info The bugs up for review today are available at: 16:08:15 #link http://qa.fedoraproject.org/blockerbugs/current 16:08:17 #info The criteria for release blocking bugs can be found at: 16:08:20 #link https://fedoraproject.org/wiki/Fedora_23_Alpha_Release_Criteria 16:08:23 #link https://fedoraproject.org/wiki/Fedora_23_Beta_Release_Criteria 16:08:26 #link https://fedoraproject.org/wiki/Fedora_23_Final_Release_Criteria 16:09:12 we currently have 1/1 proposed blockers for beta/final 16:09:27 and 4 proposed FEs for Beta we'll knock out as well 16:09:29 * kparal lurks 16:09:35 yay short meetings 16:09:45 * pschindl is here too (I found out that saying this on #fedora-qa doesn't work well) 16:10:05 nah, we tend to ignore #fedora-qa on Mondays. 16:10:25 alright, first proposal 16:10:26 #topic (1249304) UnboundLocalError: local variable 'e' referenced before assignment 16:10:30 #link https://bugzilla.redhat.com/show_bug.cgi?id=1249304 16:10:32 #info Proposed Blocker, python-blivet, ON_QA 16:11:44 this is the one we deferred 16:11:54 the update's not gone stable yet what with all you slackers not karmaing it :P 16:12:16 * adamw tried to give it karma on friday but bodhi was apparently in a bad mood 16:13:04 still not really clear exactly when this happens, i don't mind kicking it down the road a bit more. 16:13:31 that's fine with me 16:13:33 +1 punt 16:13:43 +1 16:14:04 kick it 16:14:22 * danofsatx now has Beastie Boys tunes in his haid 16:14:41 proposed #agreed - 1249304 - Punt - We need some more time to look into this particular bug. 16:14:43 lol 16:14:48 ack 16:14:50 ack 16:14:55 ack 16:15:04 #agreed - 1249304 - Punt - We need some more time to look into this particular bug. 16:15:22 (in other news, did y'all see that Bloom County has been ressurected, complete with Bill the Cat?) 16:15:43 onto our final proposal 16:15:44 #topic (1170765) systemd: all processes in scopes (including user sessions) SIGKILLed immediately on shutdown with no opportunity to shut down cleanly 16:15:47 #link https://bugzilla.redhat.com/show_bug.cgi?id=1170765 16:15:49 #info Proposed Blocker, systemd, NEW 16:16:40 * adamw does not know what bloom county is but is broadly in favour of cats, whatever their names 16:16:48 oooh, this one. 16:17:47 everyone know about it, or should i give the summary? 16:18:11 summarize, por favor 16:18:23 new to me but not been as up to speed of late 16:18:45 so basically when you shut down any systemd scope, systemd just hard kills everything running in it. 16:18:57 the most obvious example is user sessions 16:19:20 so nothing saves essentially creating a stateless mode? 16:19:35 if you've noticed that f22 seems to shut down user sessions very quickly, that's because it does. it doesn't let everything in them shut down gracefully, what it does is send them a 'please shut down nicely' signal and then one tick later kills them. 16:19:41 Corey84: something close to that, yeah. 16:20:12 that can't be good 16:20:20 if you've noticed that firefox often comes up in 'something went wrong' mode, or your bash session history sometimes not being updated, this is the cause. there's obviously other things it can cause, it heavily depends on what you have running. 16:20:32 maybe for tinfoiler in a kiosk mode but not the avg joe/jane 16:20:52 this has been kind of lying around for months and honestly i'm very unhappy at how blase the systemd folks seem to be about it 16:21:37 +1 blocker on this 16:21:42 i'm inclined to +1 blocker this on the 'data loss' basis: there's documented case of it causing fairly minor 'data loss' (bash history being the obvious one), but it clearly has the potential to cause worse. 16:21:42 understandable 16:21:45 +! block 16:21:50 +1 16:21:50 +1 block 16:21:51 +1 * 16:22:23 oh, is anyone secretarying, btw? if not i'll do it 16:22:44 adamw volunteered - you saw it here, folks 16:23:15 =) 16:23:28 proposed #agreed - 1170765 - AcceptedBlocker Final - This bug violates the following Final criterion: "All known bugs that can cause corruption of user data must be fixed or documented at Common F23 bugs." 16:23:40 ack 16:23:55 this bug is the software equivilent of holding the power button down on your machine and hoping things don't get corrupted 16:24:03 every time 16:24:09 we're not sposta do that? 16:24:57 also, the best way to stop your car is to throw it into reverse right away, why bother with any other steps 16:24:58 it's been suggested it may be not good 16:25:20 * danofsatx has used trees to stop the car before 16:26:07 * adamw has stopped his snowboard with trees, large walls of snow, other snowboard(er)s, and occasionally small rivers. 16:26:20 nor is a runaway car adamw 16:26:47 we digress 16:27:00 * danofsatx has a digression planned.... 16:27:01 ack on 117075 16:27:41 I don't like the easy shortcut to resolving this bugs blocker status either 16:28:01 well, i dunno if it's a shortcut, it seems like probably the most appropriate criterion 16:28:23 i just mean I won't be happy if this doesn't get fixed and just gets documented 16:28:24 what other criterion would be *more* appropriate for a bug that involves shutting down processes unsafely? 16:28:29 oh, i see what you mean 16:28:33 that's all I meant 16:28:38 then yeah, i agree that just documenting it would be a bad call. 16:29:51 so all acked? 16:30:04 #agreed - 1170765 - AcceptedBlocker Final - This bug violates the following Final criterion: "All known bugs that can cause corruption of user data must be fixed or documented at Common F23 bugs." 16:30:13 adamw: https://img1.etsystatic.com/022/0/6252525/il_570xN.478145691_guj1.jpg 16:30:41 heh 16:31:02 lol 16:31:08 new QA mascot? 16:32:17 onto our proposed Beta FEs? 16:32:25 #topic (1255066) inst.sshd option doesn't work i. e. sshd fails to start during installation 16:32:28 #link https://bugzilla.redhat.com/show_bug.cgi?id=1255066 16:32:30 #info Proposed Freeze Exceptions, anaconda, POST 16:32:48 seems reasonable for an early beta fe 16:33:32 agreed.... 16:33:34 +1 16:33:43 +1 16:35:53 proposed #agreed - 1255066 - AcceptedFreezeException Beta - We'd consider a fix during freeze for this issue. 16:36:21 ack 16:36:24 ack 16:37:52 #agreed - 1255066 - AcceptedFreezeException Beta - We'd consider a fix during freeze for this issue. 16:37:59 #topic (1254299) f23 workstation x86_64 Alpha-2 live locks up with intel graphics 16:38:02 #link https://bugzilla.redhat.com/show_bug.cgi?id=1254299 16:38:05 #info Proposed Freeze Exceptions, kernel, NEW 16:39:04 so this is the one that's giving satellit gyp 16:39:11 bit hard to know about it without decent logs, though 16:39:36 yeah 16:41:02 has anyone heard similar reports or seen similar hangs? 16:41:05 * adamw is on nouveau 16:41:52 I'm on nouveau as well 16:42:18 I've just upgraded to F23 on Intel, but I'm using an F22 kernel still (due to some problems with multi-monitor support) 16:43:45 hmm 16:43:54 guess i could boot a live on my laptop or something and see how tha goes 16:45:11 I just installed two Dell Latitude D630 laptops with alpha-2 Cinnamon last night. no issues other than the reclaim space bug. 16:45:44 satellit says the hang happens on workstation but not cinnamon 16:45:44 Core2Duo with Intel graphics, Centrino and all that shtuph 16:46:28 hmmm...I didn't even try workstation. 16:46:41 * danofsatx can't subject his children to gnome3 16:47:17 do it after they're safely asleep. 16:47:54 so i guess i'm kinda punt-y on this one, hoping we'll get some better logs 16:48:02 punt for more testing on this one I think 16:48:04 yeah 16:48:45 * danofsatx will test tonight 16:49:59 proposed #agreed - 1254299 - Punt - We'd like some more information on this bug before we determine FE status. 16:50:50 ack 16:51:14 ack 16:51:24 #agreed - 1254299 - Punt - We'd like some more information on this bug before we determine FE status. 16:51:36 #topic (1255447) Auto-generated kickstart fails with "ValueError: No closing quotation" 16:51:39 #link https://bugzilla.redhat.com/show_bug.cgi?id=1255447 16:51:41 #info Proposed Freeze Exceptions, pykickstart, ON_QA 16:52:43 this'ns done it looks like 16:52:58 I'd be +1 FE though 16:53:39 +1 FE 16:53:46 * danofsatx will abstain and eat his soup 16:53:46 sure 16:54:04 +1 16:54:14 mostly for the unlikely chance its not fixed 16:55:45 proposed #agreed - 1255447 - AcceptedFreezeException Beta - We would consider a fix if this is still an issue during freeze. 16:57:00 ack 16:59:51 other acks? 17:00:26 there's a terrible shortage of acks 17:00:41 is the ack field barren? 17:00:49 but we bought that whole irrigation thing 17:01:13 .fire someone for forgetting to put the water it the ack irrigation system 17:01:13 adamw fires someone for forgetting to put the water it the ack irrigation system 17:01:39 we probably shouldn't have bought it from that guy who sold us the bridge. 17:02:01 ack 17:02:04 ackity ack 17:02:13 Don't talk back 17:02:17 * danofsatx was washing his soup bowl 17:02:34 #agreed - 1255447 - AcceptedFreezeException Beta - We would consider a fix if this is still an issue during freeze. 17:02:54 ok, last one for today 17:02:55 #topic (1245786) Build failure on F23 17:02:55 #link https://bugzilla.redhat.com/show_bug.cgi?id=1245786 17:02:55 #info Proposed Freeze Exceptions, tomcatjss, VERIFIED 17:03:53 this one is VERIFIED 17:04:04 so I don't think we have to do anything with it 17:04:19 well, we would if it hadn't been pushed yet 17:04:26 but "tomcatjss-7.1.3-1.fc23 has been pushed to the Fedora 23 stable repository.", soooo... 17:04:44 * adamw closes it 17:05:02 #topic Open Floor 17:05:09 anyone have anything for open floor? 17:06:36 wait, the floor is open? 17:06:45 * danofsatx looks for the safety barriers 17:07:00 we ordered them from the irrigation/bridge dude. 17:07:08 he says they're in transit. 17:07:22 well, at least the transit is safe. 17:07:33 so it looks like nightlies have been not showing up (boot.iso) / broken (live) for the last couple of days, so we probably have other blockers 17:07:40 i'll be looking into that today, look out for blocker proposals. 17:08:09 sounds like a plan 17:10:22 * roshi sets the fuse 17:10:30 3... 17:12:19 due.... 17:12:45 * danofsatx sets a goal to figure out unicode shortcuts on a US-EN keyboard 17:16:02 2... 17:16:05 1... 17:16:14 thanks for coming folks! 17:16:17 #endmeeting