16:01:09 <adamw> #startmeeting Fedora QA meeting
16:01:09 <zodbot> Meeting started Mon Jan 30 16:01:09 2012 UTC.  The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:09 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:01:12 <adamw> #meetingname fedora-qa
16:01:12 <zodbot> The meeting name has been set to 'fedora-qa'
16:01:15 <adamw> #topic roll call
16:01:20 * kparal is here
16:01:21 <adamw> hands up if you're not here!
16:01:22 * tflink is present
16:01:33 * tflink raises his hand, too :)
16:01:34 * jskladan still here
16:01:39 <haraldh> <-
16:01:39 * mkrizek here
16:01:48 * pschindl is here
16:02:07 <kay> \o
16:02:10 <adamw> wow, full house
16:02:11 <haraldh> no hands, no chocolate
16:02:11 <adamw> hi kay
16:02:21 * Cerlyn is here
16:02:48 <adamw> #topic previous meeting follow-up
16:02:56 <brunowolff> I'll watch for a bit, but need to go to a meeting in about 25 minutes.
16:03:07 <adamw> so, we don't actually have any action items from last week, but we DO have ones from the previous week which didn't get done
16:03:51 <adamw> #info adamw to file trac ticket(s) for getting arm into the criteria / validation process somehow: now done, see https://fedorahosted.org/fedora-qa/ticket/277
16:04:15 <adamw> #info adamw to co-ordinate with bcl on making sure all important old-UI bugs discovered in F16 validation get fixed in the old UI for F17: i've made some progress on that, still need to do some more digging
16:04:48 <adamw> #info adamw to get a discussion going with pjones/kparal/hongqing/robatino to decide how we want to use pjones' el torito boot checker: also done, we have a thread going
16:05:11 <adamw> tflink: you have "tflink to contact lmacken re co-ordination between bodhi 2.0 and autoqa", any news on that?
16:05:23 <pjones> We do?
16:05:50 <tflink> didn't need to, backwards compatibility is planned - http://fedoraproject.org/wiki/Bodhi/2.0#Well_tested_and_well_documented_RESTful_API
16:06:29 <tflink> unless I misunderstood the purpose of contacting him
16:06:41 <adamw> pjones: yeah, "Using pjones' El Torito checker in QA"
16:07:00 <adamw> tflink: i believe that was the purpose, yeah, so that's probably okay
16:07:11 <pjones> adamw: I haven't seen anybody say anything in like 6 days...
16:07:13 <adamw> tflink: oh, or was there also an angle of 'what does autoqa need in the new bodhi'?
16:07:27 <adamw> pjones: hey, the action item was to start the thread, the thread's started. i've been meaning to reply to it again
16:07:49 <pjones> okay.
16:07:51 <tflink> adamw: that's what I wasn't sure of but to be honest, I'm not sure there is a whole lot of point to that conversation until bodhi 2.0 is closer to release
16:07:59 <kparal> pjones: I hope the chinese will respond once they are back from holidays
16:08:17 <kparal> hongqing is the best one to talk to here
16:08:27 <adamw> oh, yeah, that's a point - hongqing and twu are out till early feb, chinese new year.
16:08:49 <adamw> okay, we have a packed agenda, so moving on
16:09:19 <adamw> #info tflink to contact lmacken re co-ordination between bodhi 2.0 and autoqa: bodhi 2.0 is listed as having backwards compatibility, so autoqa should continue to work
16:09:35 <adamw> #topic Fedora 17 status
16:09:58 <adamw> kparal: did you get anywhere with the second rats image?
16:10:10 <kparal> adamw: it's in your mailbox
16:10:14 <kparal> basically
16:10:37 <kparal> DVD images do not boot:
16:10:37 <kparal> http://i.imgur.com/tlEzi.png
16:10:43 <kparal> netinst images boot and install just fine
16:10:49 <kparal> direct kernel boot fails
16:10:56 <kparal> and the same happens for rats_install test
16:11:09 <kparal> [    5.636733] dracut: FATAL: No or empty root= argument
16:11:10 <kparal> [    5.637992] dracut: Refusing to continue
16:11:25 <adamw> that looks like an image/dracut bug, not a rats bug>
16:11:26 <adamw> ?
16:11:30 <kparal> yes
16:11:34 <haraldh> kparal, "no or empty root=" is not a dracut bug
16:11:43 <kparal> what's the problem in there?
16:11:57 <kparal> if was not required for f16
16:11:58 <haraldh> no "root=..." is specified on the kernel command line
16:12:17 <haraldh> check grub.conf
16:12:23 <haraldh> or syslinux.cfg
16:12:31 <haraldh> or whatever bootloader you are using
16:12:38 <adamw> hi john
16:12:39 <kparal> I used this command
16:12:41 <kparal> virt-install --name Foo --ram 1024 --disk /dev/vg/Foo,size=10 --location http://dl.fedoraproject.org/pub/alt/stage/20120127/Fedora/i386/os/ --arch=i386 --extra-args "console=ttyS0 serial lang=en keymap=us ksdevice=link ks=http://kparal.usersys.redhat.com:8000/f16-minimal.ks ip=dhcp ipv6=auto vnc" --nographics
16:12:46 <j_dulaney> Sorry I'm late, class ran over
16:13:18 <kparal> I don't understand why should I specify 'root=...'
16:14:07 <haraldh> kparal, well, well
16:14:43 <kparal> we can discuss post-meeting. anyway this is the current situation for rats_install
16:14:52 <kparal> we can fix it if it is our issue
16:15:12 <haraldh> I don't know what virt-install does.. sorry...
16:15:21 <kparal> or report bug in virt-install
16:15:30 <adamw> #info manual install of rats #2 boot.iso works, DVD image does not boot, rats_install run hits a dracut / virt-install issue with boot parameters
16:15:31 <kparal> because we use that internally inside rats_install
16:15:45 <adamw> still, we get some useful status info, which is the object of the rats tests
16:15:52 <adamw> did you file a bug for the dvd install failure to boot?
16:15:58 <kparal> not yet
16:16:16 * j_dulaney notes also the nightly from Friday does not boot
16:16:29 <adamw> #action kparal to file a  bug  for the failure of rats #2 DVD image to boot
16:17:48 <adamw> j_dulaney: the nightly live? hum. similar bug to kparal's?
16:17:57 <adamw> j_dulaney: http://i.imgur.com/tlEzi.png
16:18:06 <j_dulaney> adamw:  Indeed
16:18:23 <j_dulaney> What exactly was kparal's bug?
16:18:52 <kparal> DVD boot produces that output as you see in that image
16:19:36 <j_dulaney> adamw:  +1
16:19:59 <adamw> okay
16:20:11 <adamw> so seems like another dracut-ish thing
16:20:17 <j_dulaney> Let me modify
16:20:32 <j_dulaney> I get the udev stuff, but it doesn't go any further than that, seems to lock up
16:20:45 <j_dulaney> But, the udev error is the same
16:20:54 <haraldh> Nightly live seems to boot... https://bugzilla.redhat.com/show_bug.cgi?id=766955#c30
16:20:58 * maxamillion is here ... late but here
16:22:12 <adamw> haraldh: well, *that* bug was fixed, yeah. if everyone hits what j_dulaney says, this is something new or it's regressed somehow.
16:22:17 <adamw> but we'll have to check.
16:22:51 <kay> the udev multipath stuff there is just a warning, nothing else
16:23:18 <maxamillion> silly $dayjob ... I'll by only half-here because of a conference call I'm on, but I did want to try and partake in the fun :)
16:23:38 <maxamillion> kay: apologies for missing it, but what udev multipath stuff?
16:23:58 <adamw> maxamillion: we're looking at boot issues with current f17 images.
16:24:04 <j_dulaney> kay:  If it was but a warning, it should continue to boot, but it doesn't
16:24:21 <kay> maxamillion: oh, just the warning in the png mentioned above: http://i.imgur.com/tlEzi.png
16:24:25 <adamw> so it looks like we should ensure a bug gets filed for the rats #2 DVD boot fail, and get a few others to check the latest nightly's bootableness
16:24:40 <adamw> so if you haven't tried booting a nightly recently - grab one and see what happens
16:24:42 <maxamillion> kay: ah ok
16:24:48 * j_dulaney is downloading the newest one
16:24:48 <maxamillion> adamw: rgr
16:24:48 <adamw> if that's consistently broken, we'll need another bug
16:25:14 <kay> j_dulaney: yeah, the warning should not be the reason for any failure
16:25:17 <adamw> okay, that about covers the status of current isos
16:25:26 <adamw> kparal: thanks for working on rats
16:25:34 <kparal> my pleasure
16:25:44 <adamw> I also mentioned on the agenda "Retrospective tasks still needing action" - i just took a quick look through the list and they're mostly closed or well in progress
16:25:55 <j_dulaney> kay: The vm goes idle after the udev warning and nothing else happens
16:25:56 <maxamillion> it would appear the latest nightly job is still open in koji ...
16:26:00 <adamw> the one that isn't is assigned to hongqing, so hopefully will get worked on after cny
16:26:16 <adamw> #info retrospective tasks are mostly completed or well-advanced
16:26:36 <adamw> alright
16:26:39 <adamw> anything further on f17 status?
16:26:44 <j_dulaney> maxamillion:  I'm downloading the latest completed one
16:28:02 <maxamillion> j_dulaney: rgr, was just an observation ... I would have thought the compose would be done by now
16:28:07 <kay> j_dulaney: the warning is just a printf, nothing else: http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=430959910f1b9b67c2553f5f46c0487b0f8a3a00
16:28:52 <adamw> #topic /usr move feature and testing
16:29:12 <adamw> alrighty, thanks to kay for coming along for this bit of the meeting
16:29:44 <adamw> for anyone who's not aware: one of the big f17 features, moving things from /bin and /lib and so on into /usr , is in the process of landing at present
16:29:50 <kay> adamw: sure, no problem
16:29:51 <j_dulaney> kay:  Roger
16:29:53 <adamw> https://fedoraproject.org/wiki/Features/UsrMove
16:30:07 <j_dulaney> So, I'm probably hitting something else
16:30:09 <maxamillion> UsrMove ftw!
16:30:19 <adamw> right now the builds that implement the changes are available in a rawhide tag, and there's a post on the list (cross-posted to -devel) explaining how to test them
16:30:49 <adamw> first question, are we worried about the timing of when this is landing, from a qa perspective? there has been some suggestion it should have happened sooner, though nothing in the feature process requires this
16:30:53 <kay> j_dulaney: but we updated rawhide's udev last night with a fix for sme other lvm issue, maybe it affects the live stuff too ...
16:31:12 <adamw> personally i'm not hugely worried, we still have considerable time even to alpha tc1. i'm more worried when big things land in the middle of beta.
16:31:19 <adamw> anyone else have thoughts?
16:31:34 <j_dulaney> kay:  This was from Friday, I'm just now downloading the latest nightly
16:31:38 <tflink> do we want to wait until we at least have working RATS images before the usrMove stuff lands?
16:32:18 <j_dulaney> adamw:  Hard to test if I don't have any working rawhide
16:32:39 <adamw> j_dulaney: heh, true.
16:32:44 * j_dulaney thinks the boot issues really ought to get some attention
16:32:55 <haraldh> adamw, I think the "sooner" comment was about releng and the rpm issue...
16:32:58 <kparal> let them merge it asap, right? better sooner than later
16:33:09 <haraldh> kparal, yes
16:33:17 <adamw> kparal: in general, so long as it doesn't screw up alpha builds, yes
16:33:22 <maxamillion> I'm not worried, I've upgraded a virtual and a physical from F16 to rawhide with the change and had no real issue
16:33:30 <adamw> it does seem like initial tests are good
16:33:40 <j_dulaney> Hmm, kernel bug in Rawhide
16:33:43 <adamw> i would like to try and build a boot.iso with the updated packages and make sure it boots/installs
16:33:55 <maxamillion> adamw: +1
16:34:06 <tflink> adamw: that would be a minimum in my mind but would work
16:35:25 <adamw> tflink: do you mind giving that one a shot?
16:36:29 <tflink> adamw: sure, will do. are there any particular packages that you had in mind?
16:36:50 <j_dulaney> base, at the least
16:36:51 <adamw> just build a boot.iso exactly as normal, but use packages from the rawhide tag
16:37:21 <tflink> oh, you meant for usrMove. good thing I asked
16:37:22 <maxamillion> adamw: you mean the usrmove tag?
16:37:52 <adamw> maxamillion: yes
16:37:56 <tflink> so we're not concerned with getting something pre-usrMove working?
16:38:02 <maxamillion> adamw: k, just double checking
16:38:13 <adamw> tflink: according to kparal, rats #2 boot.iso *does* work, in a 'normal' boot
16:38:25 <adamw> though you may want to build it both ways, just to check the non-usrmove one boots
16:39:14 <tflink> k, I'll get started on that and will relay results
16:39:35 <adamw> cool.
16:39:45 <j_dulaney> tflink:  If it *does* boot, can you put it up somewhere?
16:39:46 <adamw> #action tflink to test building a boot.iso with usrmove builds
16:40:07 <j_dulaney> tflink:  Specifically, the usr move one
16:40:48 <adamw> okay, so it seems like we have enough results of a rawhide upgrade with the /usr move stuff to be happy that it broadly works
16:40:50 <tflink> j_dulaney: yeah, I was planning on it
16:41:06 <adamw> if we can build a boot.iso with the /usr move packages and have it working i think it'd be okay for the changes to be tagged into rawhide at that point
16:41:10 <adamw> what does everyone else think?
16:41:24 <j_dulaney> +1
16:41:26 * nirik notes there's a hold up with rpm on the builders.
16:41:42 <adamw> oh, goody.
16:42:04 <maxamillion> nirik: oh?
16:42:43 <nirik> this feature requires a change to rpm on the builders. rel-eng is not wanting to do that... I guess it will be discussed more in the fesco meeting later this morning.
16:42:44 <haraldh> yes, we need rpm in the builders to have a guard in filesystem ... to prevent user from shooting themselves in the foot
16:42:48 <adamw> #agreed testing of rawhide with /usr move packages so far is positive: if we can compose a working / installable boot.iso with /usr move packages, the feature can be tagged into rawhide
16:43:03 <haraldh> and installing F17 packages on an unconverted FS
16:43:41 <adamw> okay. that's not a QA issue, though, i don't think, so we can just keep an eye on fesco?
16:43:44 <haraldh> when we enable the guard in filesystem.spec, the builders rpm has to provide the requirement at runtime
16:43:48 <nirik> right, just thought I would mention it.
16:43:56 <maxamillion> nirik: ah
16:44:03 <maxamillion> nirik: thanks for the info :)
16:44:43 <haraldh> can FESCO kindly ask dgilmore to do the change to the builders? :-)
16:44:57 <j_dulaney> LOL
16:45:10 * kparal notes: DVD.iso boot problem reported as https://bugzilla.redhat.com/show_bug.cgi?id=785808
16:45:29 <adamw> #info issue with boot of rats #2 DVD iso reported as https://bugzilla.redhat.com/show_bug.cgi?id=785808
16:45:31 <adamw> thanks kparal!
16:45:38 <kparal> one more bug report to come
16:45:51 <adamw> alright, does anyone have any other concerns when it comes to the /usr move feature?
16:46:00 <adamw> ahem - *QA related* concerns
16:46:10 <adamw> filesystem philosophy can stay on the devel list :)
16:46:15 <maxamillion> nirik: is there a link to a doc somewhere about the changes needed? ... I'd be curious to read up on it a little
16:46:32 <j_dulaney> adamw:  My bug is not related to kparal, after all
16:46:45 <j_dulaney> https://bugzilla.redhat.com/show_bug.cgi?id=785801
16:46:56 <j_dulaney> Turns out to be a Kernel bug
16:47:20 <nirik> maxamillion: https://fedorahosted.org/fesco/ticket/690
16:47:29 <adamw> j_dulaney: cool.
16:47:32 <maxamillion> nirik: many thanks
16:48:03 <adamw> okay, moving on
16:48:07 <adamw> #topic upcoming events
16:48:34 <adamw> so, TC testing is slated to start tomorrow, we'll have to keep an eye on the /usr move stuff and decide whether to do tc1 with or without it
16:48:50 <adamw> we'll also need to have the DVD boot bug fixed at least
16:49:25 <kay> nirik: we just need a patched rpm, that has a guard active, so users can not install some converted f17 packages on f16 systems without converting the filesystem first
16:49:32 <j_dulaney> kay says that the bug I ran into *might* already be fixed; I'm checking into that
16:50:00 <adamw> we also have a blocker review meeting coming up on friday, of course
16:50:19 <tflink> yay! what would we do without blocker meetings?
16:50:20 <kay> nirik: the rpm patch is in f15,f16,f17 already, and approved for rhel6, but not in rhel6 released atm
16:50:32 <adamw> nothing much else upcoming this week
16:50:43 <nirik> kay: yes, I understand the issue. ;)
16:50:52 <kay> nirik: ok, cool
16:50:59 <adamw> #topic AutoQA update
16:51:04 <adamw> kparal: tflink: take the floor!
16:51:08 <adamw> #chair kparal
16:51:08 <zodbot> Current chairs: adamw kparal
16:51:11 <adamw> #chair tflink
16:51:11 <zodbot> Current chairs: adamw kparal tflink
16:51:43 <kparal> ok, some updates
16:52:06 <kparal> mkrizek pushed a patch to make autoqa better retry failed/timed-out connections
16:52:12 <kparal> e.g. when downloading from koji
16:53:01 <kparal> I refactored rats_install test and fixed many problems. there is still at least one remaining that I know of
16:53:13 <kparal> but generally it seems to work (with F16)
16:53:23 * jskladan yay for better rats :)
16:53:33 * j_dulaney likes rats
16:53:37 <kparal> and that's all I know about for the last week
16:53:40 <adamw> squeee
16:53:40 <maxamillion> jskladan: so many things about that statement make me chuckle
16:54:41 <adamw> tflink: anything from your side?
16:55:05 <tflink> adamw: not really
16:55:15 <adamw> okie dokie
16:55:25 <adamw> #info mkrizek pushed a patch to make autoqa better retry failed/timed-out connections
16:55:34 <adamw> #info kparal refactored rats_install test and fixed many problems
16:55:41 <adamw> aaaand finally...
16:55:43 <adamw> #topic open floor
16:55:57 <adamw> anything else anyone wants to raise? anyone at all?!
16:56:11 * j_dulaney raises a Beefy Miracle
16:56:16 <robatino> anyone know why the RATS images are smaller than usual?
16:56:16 <kparal> #link virt-install boot issue reported as https://bugzilla.redhat.com/show_bug.cgi?id=785815
16:56:18 <j_dulaney> And eats it
16:56:35 <adamw> robatino: still clueless
16:56:45 <robatino> i noticed that the libreoffice langpacks are no longer included but that should only account for about half of it
16:57:38 <robatino> i could upload package lists for F16 and RATS2 if someone wants to go through them
16:58:10 <j_dulaney> Prior to the blocker meeting, I noticed that the way the KDE folks were tracking their stuff was causing everything KDE related to wind up on the blocker list; I fixed that and let the KDE folks know
16:58:19 <adamw> you could presumably cut off the version information, sort, and do a diff?
16:58:23 <j_dulaney> Just throwing that out there
16:58:33 <adamw> #info f17 images so far are mysteriously smaller than f16, we're not sure of the cause
16:58:49 <kparal> haraldh: can you please post some of your insight to bug 785815?
16:58:51 <adamw> j_dulaney: it's normal for KDE to have a blocker bug that blocks the main blocker.
16:59:04 <adamw> j_dulaney: they don't put all their bugs on there, only ones they actually consider release blocking.
16:59:27 <j_dulaney> adamw:  They had everything in the world in there
16:59:41 <adamw> oh, kay. maybe they changed something. can you poke me with details? i didn't see this.
16:59:45 <j_dulaney> Feature requests, everything
17:00:15 <j_dulaney> adamw:  I fixed it and got up with the KDE folks about it
17:00:29 <adamw> okay
17:00:49 <adamw> anything else for open floor? or shall we all go back to refreshing penny arcade^H^H^H^^H^H^H^H^H^H^H working?
17:01:40 * jskladan wants his pirate pig back
17:01:57 <adamw> i...you...what?
17:02:21 <jskladan> research on WebOS programming got me here :D http://enyojs.com/samples/piratepig/
17:02:30 <jskladan> sooo, work & arcades, I say!
17:02:42 <kay> adamw: you meant okay not kay, right?
17:02:48 * kay has a name that gets unintentional highlighted some times :)
17:02:58 <adamw> kay: yeah :)
17:03:23 <twaugh> Is this where the FESCo meetings are?
17:03:23 <kay> o, kay :)
17:03:27 <j_dulaney> jskladan:  I don't get it
17:03:36 <adamw> twaugh: it will be
17:03:45 <j_dulaney> twaugh:  In an hour, I do believe
17:03:59 <twaugh> Where is the time advertised?
17:04:06 <twaugh> I'm looking at a page that says 1700 UTC
17:04:38 <adamw> okay, let's finish this sucker - thanks for coming, everyone
17:04:43 <adamw> #endmeeting