15:00:35 #startmeeting 2011-08-15 Fedora QA Meeting 15:00:35 Meeting started Mon Aug 15 15:00:35 2011 UTC. The chair is tflink. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:35 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:39 #topic roll call 15:00:45 * kparal here 15:00:50 * athmane is here 15:01:00 * mkrizek is present 15:01:14 kparal, athmane, mkrizek, pschindl: welcome 15:02:22 yo 15:02:24 sorry folks, was on hairball patrol... 15:02:33 adamw: that sounds like fun 15:03:11 * tflink waits another couple minutes to see if we get more people 15:04:50 sorry for no meeting announcement, either, was focusing on alpha 15:05:07 no worries, I was in the same boat :) 15:05:14 * tflink forgot until this morning 15:05:24 ok, let's get this started 15:05:33 #topic Previous Meeting Follow-Up 15:05:44 AFAIK, we don't have anything to follow up on 15:05:51 is there anything I'm missing? 15:06:01 were there any #action items last week? 15:06:05 * jskladan lurks in 15:06:19 the 'previous meeting followup' is mostly a checkin to make sure #actions were...actioned 15:06:40 adamw to split up 728891 into separate bugs and assign them appropriately 15:06:46 done! 15:06:59 that was the file conflict bug, it's been solved for a while now 15:07:16 #info 728891 successfully split up into separate bugs 15:07:27 that's the only one I'm seeing from last week 15:07:39 okay 15:07:47 on to the next topic 15:07:58 #topic Current Alpha Blockers 15:08:08 #link https://fedoraproject.org/wiki/Current_Release_Blockers 15:08:44 we have 2 new proposed blockers that it'd be nice to go over quick 15:09:10 #link https://fedoraproject.org/wiki/Fedora_16_Alpha_Release_Criteria 15:09:19 #topic https://bugzilla.redhat.com/show_bug.cgi?id=730415 15:09:28 #info kickstart with user --name=blah results in traceback 15:10:10 talking with bcl on friday, this should be fixed soon 15:10:21 IIRC, a patch has been posted to anaconda-devel 15:10:21 this doesn't really make any blocker criteria 15:10:29 nope, probably not 15:10:44 we don't have a specific 'kickstart install should work' criterion but if we did i bet it'd be beta 15:11:22 proposed #agreed 730415 - RejectedBlocker, AcceptedNTH - Does not hit any alpha release criteria but it is kind of ugly. Tested fix would be accepted. 15:11:55 i'm not sure about nth at this point 15:11:59 ack/nack/patch? 15:12:03 that'd involve respinning anaconda again to do nothing but fix this... 15:12:08 can you stay its a beta blocker 15:12:12 do we have an anaconda dev in the house? 15:12:19 * tflink thought that there was another bug that they wanted to fix 15:12:21 Southern_Gentlem: it can be proposed as one and then we'd discuss it on friday 15:12:31 oh, it's proposed nth 15:13:49 proposed #agreed 730415 - RejectedBlocker - Does not hit any of the alpha release criteria - repropose as beta blocker 15:14:12 THUD 15:14:14 ack for that 15:14:26 clumens: so we're split on whether 730415 should be nth 15:14:35 is there any other reason to rebuild anaconda at this point? 15:14:51 no 15:15:00 729599 would be the other one, but that's nth too 15:15:05 right 15:15:09 and we were having trouble reproducing that on friday 15:15:24 well, in the way that we were fearing anyways 15:16:02 any other votes? 15:16:02 so...yeah, i'm kinda -1 nth at this point. anyone else have a vote? 15:16:24 i'm fine with kicking it on down to final 15:16:46 * tflink is taking that as an ack so that we can move on 15:16:55 #agreed 730415 - RejectedBlocker - Does not hit any of the alpha release criteria - repropose as beta blocker 15:17:08 #topic https://bugzilla.redhat.com/show_bug.cgi?id=729500 15:17:19 #info Error while installing updates on Fedora 16 Alpha RC3 15:17:28 adamw: any luck reproducing this? 15:17:33 not seen it again 15:17:37 and no-one else has either 15:17:49 so let's reject it for now 15:17:49 rejected blocker? 15:17:54 and if others hit it for rc4...add it again 15:18:23 proposed #agreed - 729500 - RejectedBlocker - Have not been able to reproduce, rejecting as blocker. Re-propose if it shows up again. 15:18:27 ack/nack/patch? 15:18:56 ack 15:19:24 * tflink would prefer to have 3 votes ... 15:19:55 #agreed - 729500 - RejectedBlocker - Have not been able to reproduce, rejecting as blocker. Re-propose if it shows up again. 15:19:56 * maxamillion is here ... late but here 15:20:04 maxamillion: welcome 15:20:10 #topic https://bugzilla.redhat.com/show_bug.cgi?id=730438 15:20:11 tflink: thanks :) 15:20:22 #info SSL CA errors when reporting an installer bug to bugzilla 15:20:30 * adamw notes once more for the record that you don't need to pass an exam to vote on blockers 15:20:40 this is something that I hit on friday - it was covered up by another libreport bug 15:20:43 being an idiot on the internet with an opinion is enough 15:20:53 right, nice catch tflink 15:20:57 adamw: lol 15:21:06 but maybe we should start? 15:21:09 #info fix available, test boot.iso is being built for karma now 15:21:12 if we haven't formally voted yet: +1 blocker, prevents bug reporting from anaconda (again) 15:21:15 * maxamillion isn't entirely sure how to respond that 15:21:28 maxamillion: i recommend blithely ignoring it 15:21:37 proposed #agreed - 730438 - AcceptedBlocker - he installer must be able to report failures to Bugzilla, with appropriate 15:21:40 information included. 15:21:44 ack 15:21:46 adamw: rgr that 15:21:48 proposed #agreed - 730438 - AcceptedBlocker - he installer must be able to report failures to Bugzilla, with appropriate information included 15:22:07 ack/nack/patch ? 15:22:27 don't make me start calling people out by name :) 15:22:39 ack. with an extra t. 15:22:51 (no, not 'tack'.) 15:22:54 kparal, jskladan: votes? 15:22:56 attack? 15:23:03 ACK 15:23:08 finally :) 15:23:09 ubuntu is attacking?! 15:23:11 man the defences! 15:23:14 #agreed - 730438 - AcceptedBlocker - he installer must be able to report failures to Bugzilla, with appropriate information included 15:23:17 OMG 15:23:27 OK, proposed NTH time 15:23:31 * Viking-Ice joins in 15:23:32 * kparal was slow to vote 15:23:36 #topic https://bugzilla.redhat.com/show_bug.cgi?id=729599 15:23:41 tflink, to the Negative Review Cannon! 15:23:45 #info PartitionException: msdos disk labels do not support partition names. 15:23:49 rbergeron, to the FUD Dispenser! 15:24:04 adamw: only if it has a flip-back yead 15:24:05 head 15:24:13 you got it 15:24:21 * bcl pokes his head in 15:24:21 * maxamillion is pretty confident he missed something 15:24:28 I think that I'm -1 nth on this one for alpha - the impact doesn't seem to be quite as bad as we first thought 15:24:37 oh, right, this one... 15:24:38 +1 for NTH, -1 for blocker 15:24:46 (alpha blocker, that is) 15:24:50 tflink: is ther news that's not in the bug? 15:25:01 adamw: it was your testing, you tell me 15:25:05 ah 15:25:11 well, i don't wanna rely too much on my little test 15:25:19 * athmane is sorry, need to go 15:25:21 I'm not too strongly -1 15:25:26 athmane: thanks for joining us 15:25:27 if bcl is sufficiently worried about the impact of this one, i'm still +1 15:25:47 this happens only on upgrade right ? 15:26:01 the theory is that it could happen on clean install, too 15:26:08 yeah 15:26:15 with msdos partition ? 15:26:16 It happens any time you have a msdos labeled disk with the /boot partition on it 15:26:19 if you have msdos disk labels 15:26:29 the theory is that any install to a disk with an msdos disk label, which isn't being entirely reformatted, could be in trouble 15:26:55 which we clean out if default partitioning scheme is chosen in anaconda ? 15:26:57 i tried a test to confirm this and the install worked, but it's entirely possible i screwed something up. 15:27:10 Viking-Ice: default depends on exactly what's on the disk already, i think 15:27:27 proposed #agreed - 729599 - Doesn't hit any alpha criteria but could affect clean installs to disks with existing msdos partitions 15:27:33 ack/nack/patch? 15:27:46 whoops, that was supposed to say AcceptedNTH 15:27:56 proposed #agreed - 729599 - AcceptedNTH - Doesn't hit any alpha criteria but could affect clean installs to disks with existing msdos partitions 15:27:57 bcl: how messy is the fix for this? 15:28:03 so, i'll be doing an anaconda after all? 15:28:23 https://www.redhat.com/archives/anaconda-devel-list/2011-August/msg00181.html 15:28:38 looks straightforward to me 15:28:55 yeah... 15:29:01 lemme see, what's the worst that could possibly happen... 15:29:07 if the boot partition doesn't get a name, would it still work? 15:29:13 adamw: the fix is clean, I just had to check to make sure the disk label supports the feature before using it. 15:29:14 (i.e. if somehow that conditional was never satisfied) 15:30:02 yes, everything would probably be fine. The change was primarily for EFI 15:30:08 okay... 15:30:09 I'm +1 nth if there is no risk of breaking partitioning if there is -1 nth 15:30:15 i guess, based on the simplicity of the fix, +1 nth 15:30:26 so yeah, new anaconda 15:30:27 +1 nth 15:30:35 there is always risk. the question is -- is the risk better to take in Alpha or Beta? 15:30:40 ok, sounds like we have an agreement 15:30:43 can do. 15:30:51 #agreed - 729599 - Doesn't hit any alpha criteria but could affect clean installs to disks with existing msdos partitions 15:31:02 * tflink will wait for new anaconda build before putting out a test boot.iso 15:31:07 bcl: i thin this is a low risk change. 15:31:47 ok, accepted blocker time 15:31:56 wait, do we need to do this? 15:32:25 prolly worth reviewing the rpm fix 15:32:26 eh, there's only one and that'll come up a little later (rpm issue) 15:32:42 or we can do it now :) 15:32:53 #topic https://bugzilla.redhat.com/show_bug.cgi?id=728707 15:33:01 #info on package upgrade RPM is removing empty directories accidentally 15:33:02 so, good news, there's a 'fix' 15:33:10 bad news, it involves pulling in a medium-size bunch of package rebuilds 15:33:19 still, if we gotta do it, we gotta do it 15:33:30 yep 15:33:35 yup 15:33:37 * adamw is still not entirely sure why panu doesn't think rpm should be fixed. 15:34:00 what are the chances that the fix could break the package rebuilds? or cause $other? 15:34:25 it sounds like rpmbuild was part of the problem 15:34:30 the fix in rpm? negligible 15:34:52 adamw: cool 15:34:54 but in general, every time you rebuild a package even with no changes, there's a small-but-existent chance of it screwing _something_ up 15:35:08 well ... ture 15:35:11 true even 15:35:15 so do we want to try pushing for a fix in rpm? 15:35:15 bleh .... typing is hard 15:35:54 i just poked the bug with that. but panu already said the right thing is the rebuilds, and we're short on time 15:36:15 very true 15:36:17 what would the estimated ETA on the rebuilds be? 15:36:21 they're all done 15:36:25 oh 15:36:26 ;) 15:36:27 need karma, but that's about all 15:36:41 so we should just spin rc4 with the rebuilds of all packages on the dvd, and hope 15:36:50 then +1 to the rpm fix 15:37:04 * maxamillion likes his package manager to be as bug free as possible 15:37:36 adamw, yup 15:37:48 +1 to the rpm fix as well 15:37:55 proposed #agreed - 728707 - unless something new comes up, go with the rebuilds as a fix for the rpm issue and make sure RC4 has the new builds 15:38:03 ack 15:38:14 ack 15:38:16 #agreed - 728707 - unless something new comes up, go with the rebuilds as a fix for the rpm issue and make sure RC4 has the new builds 15:38:17 ACK 15:38:32 ok, done with the bug review party for now 15:38:36 great 15:38:44 #topic RC3 Testing Status 15:38:54 so, bcl and clumens, if we could get a new anaconda build asap that'd be great, then we can compose rc4 and get to testing 15:39:22 I'm probably not the best person for this update, anyone care to take it on? 15:39:45 well, it's pretty straightforward...we covered most everything that needs covering, and hit some bugs that should be fixed in rc4 15:39:51 i guess the only thing missing is kde desktop validation 15:40:07 at this point, might as well wait for RC4 15:40:12 yeah i can do that real quick 15:40:52 #info still missing KDE desktop validation, may wait for RC4 for those tests 15:41:19 anything else RC3 related? 15:41:37 then moving on ... 15:41:41 any issues anyone's worried about that haven't been reviewed as blockers? 15:41:46 speak now or forever hold thy peace... 15:42:15 #topic Fedora 16 Alpha RC4 ready-ness 15:42:42 As I understand it, we're pretty much ready for RC4 15:42:52 just waiting on an anaconda build and hopefully some karma 15:43:24 I assume that the plan is to spin up RC4 today and get testing 15:43:24 yeah 15:43:27 definitely 15:43:33 yup 15:43:38 we're pretty tight on time; we need at least alpha validation tests complete by wednesday 15:43:45 #info next go/no-go meeting is on Wednesday (2011-08-17) 15:43:55 given all these damn rebuilds landing, and changed anaconda, we should try to avoid relying on pulled-forward rc3 tests as much as possible 15:44:21 * jsmith agrees with adamw 15:44:27 #info due to all of the rebuilds needed for RC4, we should avoid carrying forward results from RC3 15:44:42 note that the Alpha, Beta, Final column on the validation matrix itself is somewhat out of whack - if in doubt, criteria take priority 15:45:16 (so if something's marked 'Alpha' on the matrix but the matching release criterion is Beta, then it's a Beta test and we should fix the table at some point) 15:45:53 alpha, beta ... they're all just greek letters :-D 15:46:05 if robatino's around when rc4 compose is done he'll do the announcing, otherwise myself or tflink will take care of it 15:46:44 #action robatino, adamw or tflink - do RC4 announcement once the compose is complete 15:47:12 overall, I think that the message is - be ready for testing. Let's not slip alpha another week 15:47:19 not that anyone needed reminding 15:47:41 but I think that about covers it for RC4 stuff until it's released 15:47:53 any concerns with RC4 that we didn't cover? 15:48:03 nope not from me 15:48:40 OK, I think that covers the agenda that I had in mind 15:48:45 #topic Open Discussion 15:48:54 any other topics that should be discussed? 15:49:21 i don't see anything else major upcoming 15:49:24 * jskladan needs to catch the bus home. see you tomorrow gang! 15:49:26 there's a test day slot thursday but it's empty 15:49:29 cya jskladan! 15:49:37 which is probably a good thing given all of this 15:49:43 do we have an autoqa update from anyone? 15:49:57 do we have an autoqa update at all? :) 15:50:02 we don't have much to say 15:50:05 we releases 0.6.1 15:50:10 have you all beek working on Project Colada? :) 15:50:11 that fixes some bugs 15:50:22 *released 15:50:24 cool 15:50:38 and planned 0.7 15:50:49 #info AutoQA 0.6.1 released and deployed to fix some bugs 15:50:55 https://fedorahosted.org/autoqa/query?status=new&status=assigned&status=reopened&milestone=0.7.0 15:51:09 sounds like everything's rolling 15:51:18 what are the major goals for 0.7.0? 15:51:19 #info AutoQA 0.7.0 has been planned, work is progressing 15:51:24 we would like to concentrate on the infrastructure for the next release 15:51:57 resultsdb and staging/testing are the general themes I believe 15:52:23 adamw: wasn't it Project Coconut? 15:53:10 it has many names 15:53:17 I see 15:53:21 but only one goal 15:53:34 * kparal imagining it vividly 15:54:03 any other thoughts on autoqa updates? 15:54:26 we need a package review (soon to be 2) 15:54:35 and a sposor for mkrizek 15:54:47 hongqing says he'll provide a new test for autoqa soon - mediakit_sanity. it should test ISO images of Branched release 15:54:47 s/sposor/sponsor 15:54:54 the package review thing is looking like a bit of a roadblock 15:55:11 i've been distracted by alpha, but one thought i had was to keep it in the family 15:55:27 there has been some progress for mkrizek I believe. the future now looks brighter 15:55:28 tflink: good news, I might get a sponsor this week hopefully 15:55:36 we can exchange (or just provide) reviews within the qa group; we have, or should have, enough packagers to do that 15:55:54 * tflink makes note to remember that 15:56:02 adamw: the roadblock was the packaging _sponsor_ I believe 15:56:22 they are scarce 15:56:35 but it sounds like mkrizek might have found one 15:57:57 * nb is a sponsor 15:58:30 here we go, remember that nick, mkrizek :) 15:58:38 mkrizek, have you already found someone? or are you still looking? 15:58:45 cool, progress :) 15:59:26 * kparal has dinner on the table. let's speed it up! :) 15:59:33 nb: I might, I have been contacted with one 15:59:41 two is better than one... 15:59:42 mkrizek, ok, if that doesn't work, let me know 15:59:50 nb: ok, thanks! 15:59:51 thanks a bunch nb 15:59:56 adamw, no problem 15:59:57 do we have anyone else who needs sponsoring? 16:00:24 * tflink was already sponsored but can't quite do reveiws yet 16:00:32 odd situation 16:00:38 tflink, you can't? 16:01:14 well, reviews shouldn't be a big deal 16:01:19 i can do those if no-one else can 16:01:30 nb: long story short, I got sponsored to take on a to-be-orphaned package and I still have a mentor 16:01:30 let's not let kparal's dinner go cold... 16:01:44 adamw: where were you when I was waiting 4 months for a review on py.test? 16:01:52 :) 16:01:54 * kparal already moved his notebook to kitchen, no worries 16:02:11 tflink, oh ok 16:02:23 anyhow, unless we have other topics I'm setting the #endmeeting fuse for 5 minutes 16:02:38 tflink: on project colada! 16:02:39 nb: so its not so much can't as shouldn't until I have more experience 16:04:01 any volunteers to do the bug updating? 16:04:50 i can, if no-one else wants to 16:05:09 dgilmore: i'll do an rc4 recipe update on the trac ticket once the anaconda update is up 16:05:12 then we can all get to testing... 16:06:00 adamw: think it's worth the effort to get a boot.iso out for karma on lorax, anacanda etc. ? 16:06:12 or can we just pull all that in to RC4 without karma 16:06:13 adamw: ok, what about rpm? 16:06:21 tflink: probably worth a sanity test, yeah. 16:06:27 dgilmore: the fix for the rpm issue does not appear to be in rpm. 16:06:32 k, just making sure I wasn't wasting my time :) 16:06:38 dgilmore: the fix is to rebuild all the affected packages, it seems 16:06:44 tflink: we can pull it in without, but it will not hurt to get it 16:06:47 dgilmore: so we'll have to pull all those rebuilds. 16:06:50 adamw: fun 16:07:28 alrighty, thanks for coming everyone 16:07:40 time to test the crap out of alpha RC4 16:07:48 * tflink will send out minutes shortly 16:07:50 #endmeeting