16:59:58 #startmeeting f18final-blocker-review-1 16:59:58 Meeting started Wed Nov 28 16:59:58 2012 UTC. The chair is tflink. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:59:58 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:59:58 #meetingname f18final-blocker-review-1 16:59:58 The meeting name has been set to 'f18final-blocker-review-1' 16:59:58 #topic Roll Call 17:00:14 * kparal is not here this time 17:00:16 Anyone else who hasn't run away in terror? 17:01:22 * tflink is worried about the sound of crickets ... 17:02:02 * satellit listening 17:02:33 nobody can hide 17:03:17 win 27 17:03:28 oops, sorry :( 17:03:30 I see one person attempting to run away 17:03:52 just wrapping up the townhall and coming here :P 17:03:57 * jreznik_ opens windows (not windows) 17:04:09 and jumps 17:04:39 oh good lord, 48 proposed blockers, 23 proposed nth 17:05:04 adamw: you around for some blocker review? 17:06:42 * tflink waits for more people, we need more to continue 17:08:02 * tflink wonders how it is that we ended up with blocker review and fesco @ the same time 17:08:09 or at least overlapping times 17:08:28 morning 17:08:36 by changing it from friday without thinking very hard 17:08:51 I thought we changed our time slot first, though 17:10:00 either way, still waiting for more people. we have 1.5 not including me (I assume that jreznik has other meetings and hence the .5) 17:11:42 pity 17:12:22 viking usually shows up after a bit doesn't he? 17:13:44 assuming he's not busy with other stuff 17:16:33 * jreznik is free for next 45 minutes 17:16:59 I guess we can get started and see how far we get in 45 minutes 17:17:15 #topic Introduction 17:17:21 Why are we here? 17:17:21 #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. 17:17:28 #info We'll be following the process outlined at: 17:17:28 #link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting 17:17:33 #info The bugs up for review today are available at: 17:17:34 #link http://qa.fedoraproject.org/blockerbugs/current 17:17:38 #info The criteria for release blocking bugs can be found at: 17:17:39 #link https://fedoraproject.org/wiki/Fedora_18_Alpha_Release_Criteria 17:17:39 #link https://fedoraproject.org/wiki/Fedora_18_Beta_Release_Criteria 17:17:39 #link https://fedoraproject.org/wiki/Fedora_18_Final_Release_Criteria 17:17:49 * tflink starts with the proposed blockers 17:18:00 oh, forgot this: 17:18:08 #info Up for review today, we have: 17:18:11 #info 48 Proposed Blockers 17:18:11 #info 2 Accepted Blockers 17:18:11 #info 23 Proposed NTH 17:18:11 #info 0 Accepted NTH 17:18:25 * tflink dies a little inside and continues with the proposed blockers 17:18:34 #topic (878956) After installation is complete, Alt+F4 is broken 17:18:34 #link https://bugzilla.redhat.com/show_bug.cgi?id=878956 17:18:34 #info Proposed Blocker, anaconda, NEW 17:19:08 I really need to fix this sorting bug 17:19:37 i was planning to say we cap the meeting at 2 hours or something 17:19:45 anyway, let's see. 17:19:51 yeah, I was planning to cap it at 3 hours 17:19:55 like we did for beta 17:21:04 tflink: 3hrs.... 17:21:10 isn't this that kernel bug? 17:21:18 not sure it's connected to that two features - as it affects kde too 17:21:31 kernel bug? 17:21:41 akshayvyas: exciting thought, I know 17:21:48 could be kernel but kamil mentions it happens after anaconda setup... 17:21:55 tflink: gah, i can't find it now 17:22:14 i hate when you know you're CCed on a bug and can't find the damn thing 17:22:16 "This is tightly connected to Anaconda, because this bug does not shown before "Configuring installed system" phase in Anaconda." 17:23:05 c #4 says its ibus 17:23:17 Having a little trouble installing the beta. I have a 65GB chunk of free space, with no partitions, but it's saying I don't have enough room. 17:23:52 aha 17:23:52 https://bugzilla.redhat.com/show_bug.cgi?id=859485 17:24:22 akshayvyas: not sure how we use ibus in kde, it at all :) and it affects kde too... 17:25:04 hum, looks to be a bit different, but could be related. 17:26:07 either way, I'm not sure this hits the release critera very well 17:26:45 yeah 17:26:57 giving it the go/no-go smell test...i'm probably lightly -1 17:26:58 but could be extremely annoying - and makes desktop hard to use... 17:27:01 +1 nth 17:27:10 wll if it can be fixed with update then i am +1 nth 17:27:33 it can't be fixed w/ update on live 17:28:03 it sounds like we're mostly -1 blocker, +1 nth? 17:28:26 * jreznik is definitely +1 nth 17:28:49 and we need more info on this one 17:29:01 including whether it's a dupe of / related to that other one, yeah. 17:29:26 anyone know the room for (fedora18 openstack) ? 17:29:45 Black74hat: #fedora-cloud 17:29:57 tflink: thanks 17:30:05 proposed #agreed 878956 - RejectedBlocker, AcceptedNTH - This doesn't clearly hit any of the F18 final release criteria but is not good for the user experience and can't be fixed with an update on the livecds 17:30:22 ack 17:30:39 ack 17:31:22 any other ack/nak/patch? 17:32:08 ack 17:32:11 #agreed 878956 - RejectedBlocker, AcceptedNTH - This doesn't clearly hit any of the F18 final release criteria but is not good for the user experience and can't be fixed with an update on the livecds 17:32:16 #topic (830434) Omits "IPV6INIT=yes" from kickstart-generated ifcfg-* file 17:32:16 #link https://bugzilla.redhat.com/show_bug.cgi?id=830434 17:32:16 #info Proposed Blocker, anaconda, ASSIGNED 17:34:08 is it 17 or 18 ?? 17:34:16 this seems to be related to 852808 17:34:39 and was pulled in due to blocking that (which is marked as final blocker 17:35:51 we agreed as principle for f17 that IPv6 ought to work out of the box, iirc. 17:36:03 it arguably hits "The installer must be able to successfully complete a scripted installation, using the installer's preferred scripting system, which duplicates the default interactive installation as closely as possible" 17:36:05 i'm basically +1 blocker on anything Tore says breaks IPv6 ootb, he is our ipv6 guy. 17:36:30 if I'm understanding correctly, this would prevent a KS reinstall from something that was ipv6 enabled 17:36:30 i can't recall what criterion we were using. 17:36:42 i don't think it's at all ks-related. by my reading. 17:36:43 the other one would probably be updates 17:36:50 this one is, I think 17:36:53 the one it blocks isn't 17:37:42 it was will who added the word 'kickstart' to the description 17:37:51 tore's description omitted it, and tore says he did a completely normal install 17:38:01 and spun off another bug for the non-ks case 17:38:27 oh, hm 17:39:39 so this is ks case, 852808 is interactive case. still, +1 both 17:40:12 * jreznik is lost now... 17:40:21 proposed #agreed 830434 - AcceptedBlocker - Violates the following F18 beta release criterion for IPv6 systems: " The installer must be able to successfully complete a scripted installation, using the installer's preferred scripting system, which duplicates the default interactive installation as closely as possible" 17:42:43 ack/nak/patch? 17:45:05 ack 17:45:41 ack 17:45:53 ack if it was agreed ipv6 has to work 17:46:09 Ticket notification - f18finalnicetohave: [Bug 878985] MATE entry on RC1 i386 DVD install results in an incomplete mate-desktop (openbox login only) please remove mate and cinnamon from DVD left list 17:47:18 #agreed 830434 - AcceptedBlocker - Violates the following F18 beta release criterion for IPv6 systems: " The installer must be able to successfully complete a scripted installation, using the installer's preferred scripting system, which duplicates the default interactive installation as closely as possible" 17:47:33 #topic (852808) Omits "IPV6INIT=yes" from the generated ifcfg-* file 17:47:33 #link https://bugzilla.redhat.com/show_bug.cgi?id=852808 17:47:33 #info Proposed Blocker, dracut, ON_QA 17:48:25 proposed #agreed 852808 - AcceptedBlocker - Violates the following F18 alpha release criterion for IPv6 networks - "The installed system must be able to download and install updates with yum and the default graphical package manager in all release-blocking desktops" 17:48:42 this is the interactive case of the last bug 17:49:01 +1. 17:49:04 same reasoning. 17:49:11 ack/nak/patch? 17:49:25 ack 17:50:07 ack 17:50:26 ack 17:50:40 #agreed 852808 - AcceptedBlocker - Violates the following F18 alpha release criterion for IPv6 networks - "The installed system must be able to download and install updates with yum and the default graphical package manager in all release-blocking desktops" 17:50:48 #topic (861123) Please add x-systemd.device-timeout=0 to mount options for encrypted file systems that need a passphrase from the user 17:50:52 #link https://bugzilla.redhat.com/show_bug.cgi?id=861123 17:50:54 #info Proposed Blocker, anaconda, ASSIGNED 17:52:10 #topic (861123) Please add x-systemd.device-timeout=0 to mount options for encrypted file systems that need a passphrase from the user 17:52:13 #link https://bugzilla.redhat.com/show_bug.cgi?id=861123 17:52:13 #undo 17:52:13 Removing item from minutes: 17:52:15 #undo 17:52:15 Removing item from minutes: 17:52:17 #undo 17:52:17 Removing item from minutes: 17:52:20 #info Proposed Blocker, anaconda, ASSIGNED 17:52:28 In most cases (see Blocker_Bug_FAQ), a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode. This includes correctly accessing any encrypted partitions when the correct passphrase is supp 17:52:38 sigh, too long 17:53:13 but this could arguably hit that criterion - the system doesn't boot properly if the user isn't around to enter the passphrase right away 17:53:40 well, 'right away' is a stretch 17:54:06 seems like a 90 second timeout 17:54:24 i think i'm -1, again on the smell test. this can be fixed with an upgrade and it's no kind of showstopper. 17:54:27 update* 17:54:35 Ticket notification - f18finalnicetohave: [Bug 878956] After installation is complete, Alt+F4 is broken 17:55:01 actually, no, even longer than that. 17:55:01 good point 17:55:15 you're not going to have encryped filesystems on a livecd 17:55:24 well, can't tell. it's either 90 sec or 180 sec. either way, it's a while. 17:55:34 if you miss the timeout you just swear and reboot. i have experience with this. 17:55:55 it's an annoyance, yeah, blocker bug, no. 17:56:00 proposed #agreed 861123 - RejectedBlocker - This doesn't clearly hit any of the F18 final release criteria as it still has a reasonable timeout and could be fixed with an update. 17:56:46 ack 17:56:52 ack 17:57:08 ack 17:57:29 #agreed 861123 - RejectedBlocker - This doesn't clearly hit any of the F18 final release criteria as it still has a reasonable timeout and could be fixed with an update. 17:57:35 #topic (876716) anaconda crashes after setting root password 17:57:36 #link https://bugzilla.redhat.com/show_bug.cgi?id=876716 17:57:36 #info Proposed Blocker, anaconda, NEW 17:57:41 typically won't have encrypted filesystem on livecd -- someone somewhere might jump through the hoops to create it -- but likely shouldn't block 17:58:09 stephen_pollei: even if you have one, it won't be automatically mounted at boot, and even if it was and it failed to mount, it wouldn't break boot. 17:58:28 oh, i guess you could theoretically create a live image which was itself encrypted. maybe. not even sure if that's possible. 17:58:43 it probably is but would take quite a bit of work to make it happen 17:59:02 not sure about this one, though. sounds like it is a timing problem 18:00:01 i haven't ever seen this in any of my test installs, and i've done a lot 18:00:23 same here 18:00:28 it's a nasty bug for sure, but otoh, i can imagine us not being able to pin it down by release, and i'm not sure we'd block indefinitely for a bug like this while waiting for someone to be able to nail it down 18:00:35 while nasty, not sure if it's common enough to block release for 18:00:38 nth? 18:00:38 so, i'm on the fence 18:00:43 nth for sure 18:01:03 it can be re-proposed as a blocker if we get more info or it turns out to be more common 18:01:19 we could ask on-list if anyone has seen it 18:01:59 reject or punt? 18:02:27 * satellit what if not a large enough HD to install to ...I have seen this happen while installing files 18:03:04 i think punt for a week, since this is a small meeting 18:03:18 ok, punt 18:04:21 proposed #agreed 876716 - While this is nasty, we need more information on how common the issue is. Ask test@ if anyone else has been seeing this and re-visit at the next meeting 18:05:19 ack 18:05:31 #action adamw to ask for reproducers of 876716 on test@ 18:05:36 do i have a chair? 18:05:50 #chair adamw 18:05:50 Current chairs: adamw tflink 18:05:55 #action adamw to ask for reproducers of 876716 on test@ 18:06:07 I think we may have lost everyone else 18:07:07 #agreed 876716 - While this is nasty, we need more information on how common the issue is. Ask test@ if anyone else has been seeing this and re-visit at the next meeting 18:07:18 is anyone else here other than adam and I? 18:07:29 well, here to participate in the blocker review 18:07:39 looks like jreznik is busy with the fesco meeting 18:08:56 it's going to be hard... 18:09:20 i guess we could wrap up for now. 18:09:23 akshayvyas: still around? 18:09:30 yeah, I guess we'll continue tomorrow 18:10:03 or try to. 18:10:22 #topic Open Floor 18:10:34 #info we don't have enough people to continue the blocker review today 18:11:00 #info we will attempt to continue tomorrow, in the hope that we will have enough people to make progress 18:11:13 If there's nothing else we can do ... 18:11:19 * tflink sets fuse for ~ 5 minutes 18:13:25 * akshayvyas is back 18:16:14 Thanks for coming everyone 18:16:23 * tflink will send out minutes and new announcement shortly 18:16:26 #endmeeting