17:03:25 #startmeeting F17alpha-blocker-review-3 17:03:25 Meeting started Fri Feb 10 17:03:25 2012 UTC. The chair is tflink. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:03:25 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:03:26 * pschindl is here and waiting for some fun 17:03:38 yo 17:03:38 #meetingname F17alpha-blocker-review-3 17:03:38 The meeting name has been set to 'f17alpha-blocker-review-3' 17:03:46 #topic roll call 17:03:55 * nirik is lurking and happy to help with anything he can 17:04:03 who's ready for some blocker review fun time? 17:04:05 * jskladan1 is distracted with the anaconda stuff on #fedora-qa 17:04:14 same here 17:06:51 ok, it looks like the anaconda testing discussion has died down for the moment 17:07:02 and I think we have enough people to get started 17:07:22 #topic Introduction 17:07:35 #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:07:54 #link https://fedoraproject.org/wiki/Current_Release_Blockers 17:07:55 #link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting 17:08:06 #info 8 proposed blockers 17:08:07 #info 3 accepted blockers 17:08:07 #info 1 proposed NTH 17:08:24 if there are no objections, let's get started with the proposed blockers 17:08:36 go for it 17:08:45 note: bcl will be out until I think 10:30 or 11:30 17:08:45 #topic (787744) RuntimeError: device is already mapped (F17 Alpha TC1) 17:08:49 #link http://bugzilla.redhat.com/show_bug.cgi?id=787744 17:08:51 Bug 787744: unspecified, unspecified, ---, anaconda-maint-list, MODIFIED, RuntimeError: device is already mapped (F17 Alpha TC1) 17:08:51 #info Proposed Blocker, MODIFIED 17:08:54 er, 1.5hrs from now -> 2.5 hrs from now 17:09:03 i asked him to add notes in the bug reports on bugs that concern anaconda 17:10:35 I'm thinking +1 blocker on this 17:10:41 but it needs to be re-tested 17:11:13 yup, should be fixed in tc2 17:11:20 proposed #agreed - 787744 - AcceptedBlocker - The installer must be able to complete an installation using the text, graphical and VNC installation interfaces 17:11:21 brian didn't really answer my question, so i find it hard to vote 17:11:32 but going on the safe side, sure 17:11:38 i'll test it first thing in the morning 17:11:44 on monday 17:12:06 and will report to bugzilla 17:12:27 ack/nak/patch? 17:12:35 ack 17:12:43 ack 17:12:52 #agreed - 787744 - AcceptedBlocker - The installer must be able to complete an installation using the text, graphical and VNC installation interfaces 17:13:01 #topic (789181) repoclosure failure on 17-Alpha.TC2 DVDs (gnome-python2-bonobo-2.28.1-8.fc17) 17:13:04 #link http://bugzilla.redhat.com/show_bug.cgi?id=789181 17:13:06 Bug 789181: unspecified, unspecified, ---, walters, NEW, repoclosure failure on 17-Alpha.TC2 DVDs (gnome-python2-bonobo-2.28.1-8.fc17) 17:13:07 #info Proposed Blocker, NEW 17:13:17 clear blocker per the criteria 17:13:20 oh, anyone willing to play secretary? 17:13:23 we need to unravel this particular thicket today 17:13:50 proposed #agreed - 789181 - There must be no file conflicts (cases where the files in some packages conflict but the packages have explicit Conflicts: tags are acceptable) or unresolved package dependencies during a media-based (DVD) install 17:14:28 ack 17:14:29 ack 17:14:33 * adamw will be secretary if no-one else wants to 17:14:36 #agreed - 789181 - There must be no file conflicts (cases where the files in some packages conflict but the packages have explicit Conflicts: tags are acceptable) or unresolved package dependencies during a media-based (DVD) install 17:14:53 #topic (789180) repoclosure failure on 17-Alpha.TC2 DVDs (libguestfs-1.17.4-7.fc17) 17:14:57 #link http://bugzilla.redhat.com/show_bug.cgi?id=789180 17:14:58 Bug 789180: unspecified, unspecified, ---, rjones, NEW, repoclosure failure on 17-Alpha.TC2 DVDs (libguestfs-1.17.4-7.fc17) 17:14:59 #info Proposed Blocker, NEW 17:15:25 similar boat, pretty clear blocker 17:15:42 yup 17:15:42 proposed #agreed - 789180 - There must be no file conflicts (cases where the files in some packages conflict but the packages have explicit Conflicts: tags are acceptable) or unresolved package dependencies during a media-based (DVD) install 17:15:45 ack 17:15:46 ack 17:15:52 #agreed - 789180 - There must be no file conflicts (cases where the files in some packages conflict but the packages have explicit Conflicts: tags are acceptable) or unresolved package dependencies during a media-based (DVD) install 17:16:02 #topic (789233) cannot login system with minimal packages 17:16:03 #link http://bugzilla.redhat.com/show_bug.cgi?id=789233 17:16:03 #info Proposed Blocker, NEW 17:16:04 Bug 789233: high, unspecified, ---, bcl, NEW, cannot login system with minimal packages 17:16:28 * tflink wonders what image was used for this 17:17:08 yeah, it would help to know 17:17:32 we also have https://bugzilla.redhat.com/show_bug.cgi?id=787838 and my https://bugzilla.redhat.com/show_bug.cgi?id=788829 as kinda-similar bugs, my spidey senses are tingling 17:17:36 Bug 787838: unspecified, unspecified, ---, mgrepl, CLOSED RAWHIDE, no login for liveuser 17:17:37 Bug 788829: urgent, unspecified, ---, mgrepl, NEW, Cannot log in with SELinux enabled in 2012-02-08 rawhide 17:19:04 * tflink has also seen some problems with SELinux but has been using non-standard media 17:20:08 I'm thinking that there is something here but it doesn't seem clear what exactly is going on 17:20:13 punt for this week? 17:20:15 going by the date i'd guess it's a tc2 test 17:20:36 * tflink can't even get a working TC2 install :) 17:20:36 yeah, punt seems reasonable, there's clearly something wiggy going on with selinux imho, i'm going to keep bugging dan about it 17:21:21 proposed #agreed - 789233 - We need more information on the image used and what exactly is going on before making a decision on blocker status 17:21:40 i saw this on one of the TC2 DVDs (didn't get a working install with the other) 17:21:58 ack/nak/patch? 17:22:04 so it probably affects both 17:22:15 ack 17:22:17 ack 17:22:30 #agreed - 789233 - We need more information on the image used and what exactly is going on before making a decision on blocker status 17:22:32 * maxamillion slides into the back of the room quietly 17:22:39 #topic (787781) Lorax Templates are deleting required binaries post usrmove 17:22:42 #link http://bugzilla.redhat.com/show_bug.cgi?id=787781 17:22:44 Bug 787781: urgent, unspecified, ---, wwoods, MODIFIED, Lorax Templates are deleting required binaries post usrmove 17:22:45 #info Proposed Blocker, MODIFIED 17:22:55 this was blocking image composition, so I think it's a pretty clear blocker 17:23:08 LATE AGAIN, Mr. MAXAMILLION?! 17:23:18 adamw: I know!!!!! :( 17:23:22 * maxamillion slaps $day_job 17:23:47 tflink: +1 17:24:15 proposed #agreed - 787781 - AcceptedBlocker - Prevents image composition 17:24:24 ack 17:24:29 ack 17:24:42 on second thought, that criterion isn't quite right 17:24:58 #agreed - 787781 - AcceptedBlocker - The installer must boot (if appropriate) and run on all primary architectures, with all system firmware types that are common on those architectures, from default live image, DVD, and boot.iso install media 17:25:08 ack 17:25:10 the image does compose, it just doesn't work :) 17:25:24 well, ack 17:25:24 this one, on the other hand ... 17:25:27 #topic (787787) mkefiboot crashes with --apple option by using old mkfs command 17:25:29 although we should just close it, right? 17:25:30 #link http://bugzilla.redhat.com/show_bug.cgi?id=787787 17:25:32 Bug 787787: high, unspecified, ---, wwoods, MODIFIED, mkefiboot crashes with --apple option by using old mkfs command 17:25:33 #info Proposed Blocker, MODIFIED 17:25:41 adamw: probably, yeah. I was waiting to test with TC2 first 17:25:44 the newer lorax is built and pushed and tc2 was composed with it 17:25:45 okay 17:25:48 will set on_qa though 17:25:50 then 17:26:02 this one can be closed, though. it was crashing pungi 17:26:30 so blocker status is pretty much pointless :) 17:27:01 proposed #agreed 787787 - AcceptedBlocker - Prevents image composition because pungi was crashing 17:27:17 or we can just close it - either is fine with me 17:27:41 * dgilmore pops in from 30,000 feet 17:28:18 sorry /me got distracte d by phonecall 17:28:54 * tflink glares disapprovingly at jskladan 17:29:00 any thoughts? 17:29:21 the safest route would be to accept and propose it closed pending testing on an EFI mac 17:29:26 tflink: doesnt matter either way its fixed 17:29:26 if its resolved, might as well close it 17:30:29 maxamillion: +1 17:30:30 dgilmore: yep, just waiting for some input rather than unilaterally making a decision :) 17:30:48 but it sounds like "close it" 17:30:51 yeah 17:31:16 #agreed - 787787 - Since images build with the new verison, this can be closed 17:31:25 #topic (788829) Cannot log in with SELinux enabled in 2012-02-08 rawhide 17:31:28 #link http://bugzilla.redhat.com/show_bug.cgi?id=788829 17:31:30 Bug 788829: urgent, unspecified, ---, mgrepl, NEW, Cannot log in with SELinux enabled in 2012-02-08 rawhide 17:31:31 #info Proposed Blocker, NEW 17:31:34 aaand, on to this again :) 17:32:33 I'm thinking punt until we have more information since it doesn't sound like this was a F17 install 17:32:43 not that there isn't an issue here 17:32:54 tflink: the TC2 live images appear to have the same issue for me 17:33:23 proposed #agreed - 788829 - We need more information on the cause of an requirements to hit this bug, will revisit next week 17:33:27 (granted I just downloaded so I only have about 20 minutes of testing so far, but I'm seeing an issue that behaves similarly so I assume its the same) 17:33:28 ack/nak/patch? 17:33:41 sorry, just hit a weird bug where my keyboard stops responding and had to log out 17:33:54 maxamillion: it sounds like there are ~ 3 bugs hinging at the same issue, so there's probably a bug here 17:33:55 did i miss any bugs before 788829? 17:34:05 adamw: just the 2 lorax issues 17:34:25 both accepted blockers i guess? 17:34:39 im +1 for a blocker, something is going on there, but it seems it needs some more testing/triaging 17:34:44 adamw: accepted on 787781 and close on 788829 17:34:55 dgilmore: +1 17:35:25 tflink: what on 787787? 17:35:36 I'm not saying that there isn't an issue here, but I'm not convinced that this bug hits the alpha criteria 17:35:52 adamw: it's fixed so we agreed to just close it 17:36:07 this _particular_ bug, rather 17:37:04 but then again, code freeze is on tuesday, right? 17:37:57 * tflink is -1 blocker -1 NTH right now because we don't have a cause or proposed fix 17:38:39 but it also sounds like I'm in the minority right now 17:38:58 any other votes? I'm seeing +2/-1 blocker right now 17:38:59 tflink: yes code freeze for alpha is tuesday, which means you need to get stuff in Monday 17:39:50 well, I guess I'm looking at it as a "zomg that's a shitty issue to have off the bat from fresh boot into TC2 live image" but does it actually contend with any criteria for a blocker? 17:39:52 adamw: care to weigh in? 17:40:02 I don't think it's blocker. I can't find any criterium for this. 17:40:11 -1 blocker for me 17:40:12 we're on my bug here? 17:40:16 yep 17:40:18 adamw: yes 17:40:20 well...as experienced it's clearly a blocker. you can't log into the system. 17:40:44 "Following on from the previous criterion, after firstboot is completed and on subsequent boots, 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 a working graphical environment without unintended user intervention. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied " 17:40:53 aaa /me got ninja'd 17:40:56 adamw: but this wasn't a F17 install, was it? 17:40:56 but the question is, what the hell is actually going on, and is it happening to anyone else 17:41:02 ah, sure enough 17:41:18 it's an upgrade, yeah. so the question is does it actually impact fresh installs / anyone else. 17:41:21 exactly, I'm not saying that it isn't blocker material. I'm just not comfortable accepting as a blocker until we know more 17:41:24 adamw: i think it needs more investigation, but as it stands its got blocker on it 17:41:24 sure 17:41:27 i'm happy with that 17:41:32 adamw: its happening to me with the TC2 for Desktop Live and XFCE Live ... I'm installing from the XFCE TC2 into a VM right now and I'll verify off that install as well 17:41:33 but i was replying to pschindl's 'can't find a criterion' 17:41:46 ok, sounds like we're +3/-2 blocker 17:41:50 adamw: yeah, rgr 17:42:13 maxamillion: 'it's happenign to me', as in, same symptoms? can't log in if selinux is enabled, and the contexts appear to be completely out of whack? 17:42:26 adamw: yes, sorry for lack of clarification 17:42:29 adamw: how does that criteria apply? This was on a rawhide system, no? 17:42:43 tflink: oh, i see your confusion. at the time i filed, f17 hadn't branched. 17:42:53 adamw: I'm experiencing similar symptoms and I can log in once I boot with enforcing=0 17:42:54 tflink: but according to maxamillion, it also hits the TC2 17:43:05 so if it's the same, then I'm +1 on blocker 17:43:20 jskladan1: he also said that he'd been testing for ~20 mins 17:43:21 let's put it this way 17:43:22 I don't know that its the same, but the symptoms are certainly similar 17:43:29 * tflink is writing a proposal, hold your horses 17:43:31 is anyone actually running f17 right now and *not* seeing this? 17:43:55 tflink: boot TC2 Live image and you can't login, boot TC2 Live image with enforcing=0 and login just fine 17:44:03 adamw: I'm not running anything right now that I would be comfortable calling F17 17:44:15 lots of hacked together installs 17:44:25 adamw: im planning a f17 upgrade this weekend 17:44:49 so would we rather defer for more testing/diagnostics? 17:45:05 i'm not hugely concerned either way, i'm going to be poking it whichever we pick. 17:45:06 +traige 17:45:13 proposed #agreed - 788829 - AcceptedBlocker - Following on from the previous criterion, after firstboot is completed and on subsequent boots, 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 a working graphical environment without unintended user intervention. This includes correctly accessing any encrypted partitions when the correct pa 17:45:15 bleh ... I can't type 17:45:20 we need to fix that criterion 17:45:27 ack/nak/patch? 17:45:36 ack 17:45:48 tflink: heh 17:45:52 * dgilmore is going to have to drop out soon for a bit 17:45:54 mild ack 17:45:57 ack 17:46:01 ack here 17:46:15 adamw: patch? 17:47:27 no patch 17:47:43 ok 17:47:48 i note in the -85 selinux-policy changelog "- sshd fixes seem to be causing unconfined domains to dyntrans to themselves" 17:47:51 i wonder if that's related 17:47:55 #agreed - 788829 - AcceptedBlocker - Following on from the previous criterion, after firstboot is completed and on subsequent boots, 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 a working graphical environment without unintended user intervention. This includes correctly accessing any encrypted partitions when the correct passphrase 17:48:07 #topic (789271) firstboot-text prevents system from booting 17:48:07 #link http://bugzilla.redhat.com/show_bug.cgi?id=789271 17:48:07 #info Proposed Blocker, NEW 17:48:10 Bug 789271: unspecified, unspecified, ---, xgl-maint, NEW, firstboot-text prevents system from booting 17:48:26 oh yeah, this wasn't actually fixed for F16 17:48:28 just disabled 17:48:58 nvm, I spoke too soon 17:49:36 * dgilmore is off 17:49:41 * jskladan1 is not at all sure, what the bug actually means 17:50:03 I think it's an issue with basic video on reboot after install 17:51:29 yeah, we need more info here 17:51:37 is it some issue with startup sequence, or does X start fail 17:51:47 adamw: +1 17:52:07 if this was a net install, it may have got the older libpciaccess, so vesa driver was broken 17:52:23 proposed #agreed - 789271 - It isn't clear what the actual failure is here, more information and triage is needed before deciding on blocker status 17:52:30 ack 17:53:13 ack 17:53:27 #agreed - 789271 - It isn't clear what the actual failure is here, more information and triage is needed before deciding on blocker status 17:53:35 ok, that's all of the approved blockers 17:53:42 hi bcl 17:53:44 s/approved/proposed 17:54:06 we have 1 proposed NTH 17:54:09 #topic (785815) virt-install URL install fails with dracut Warning: dracut: FATAL: No or empty root= argument 17:54:12 #link http://bugzilla.redhat.com/show_bug.cgi?id=785815 17:54:13 #info Proposed NTH, NEW 17:54:14 Bug 785815: unspecified, unspecified, ---, dracut-maint, NEW, virt-install URL install fails with dracut Warning: dracut: FATAL: No or empty root= argument 17:54:16 hey folks. 17:54:32 * maxamillion has to run for about 15 minutes 17:54:52 ooh, I have an opinion. it is a virt-install issue and not a blocker. 17:55:40 bcl: I think the NTH part is that virt-install is used for testing 17:56:48 but I'm borderline -1 NTH on this 17:57:09 bcl: it's an NTH proposal, not blocker proposal 17:57:27 well yes. The issue is that you need to have the rootfs image available, which may not be easy to automate. eg. using --kernel and --initrd instead of --location 17:57:51 it does seem like something we might not want to poke in a freeze 17:57:53 bcl: so the assertion that this will be fixed when a dracut fix lands isn't tru? 17:58:07 i'm not hugely expert so i don't want to cast a very strong vote, though 18:00:31 I'm not sure how you'd fix it in dracut. 18:01:16 In f16 the rootfs was in the initrd, now it is back to being 'someplace else'. So you have to tell virt-install or dracut where that other place is. 18:01:47 it sounds like the current assumption is that the loader changes in dracut will fix this 18:01:51 virt-install *should* be able to find it when using location, as long as that points to a tree or mounted iso. 18:02:05 I do not have strong opinion either way, I know Kamil uses virt-instlall quite extensively for RATS etc, so this si probably more of "pain in the rear" for the test automation 18:02:14 I may be missing something, but I don't see how. 18:02:39 whoever is using virt-install ought to be able to work around it easily. 18:03:06 also, this should just work if you are using an iso. 18:03:07 aiui you just have to be a bit more careful when invoking virt-install, right? it's not like it's completely broken. 18:03:15 exactly. 18:03:16 i'd be worried if this was some kind of insurmountable issue for autoqa. 18:03:59 * tflink isn't familiar enough with the RATS code to know 18:04:20 so ... any thought on reject or defer? 18:05:35 proposed #agreed - RejectedNTH - There are no criteria around virt-install and it sounds like this problem is workaround-able. 18:05:41 I'm -1 blocker +1 NTH but I'd bounce it to virt-install not dracut. 18:06:51 i'm weakly -1 nth 18:06:59 i don't see the justification for changing this during a freeze 18:07:13 I don't see how changing this during code freeze would help anything 18:07:13 adamw: +1 18:07:37 or hurt, as long as the change is in virt-install and not dracut 18:08:07 I don't see how it could hurt. and it makes things easier for testers. 18:08:08 tflink: +1 18:08:44 either way, it sounds like an overall ack on the proposal? 18:09:03 ack 18:10:01 #agreed - RejectedNTH - There are no criteria around virt-install and it sounds like this problem is workaround-able. 18:10:01 ack 18:10:22 and now it's time for the accepted blockers 18:10:30 #topic (787261) Fedora 17 Alpha TC1 still has all F16 artwork 18:10:31 #link http://bugzilla.redhat.com/show_bug.cgi?id=787261 18:10:31 #info Accepted Blocker, NEW 18:10:32 Bug 787261: unspecified, unspecified, ---, tcallawa, NEW, Fedora 17 Alpha TC1 still has all F16 artwork 18:10:47 sounds like this still isn't fixed 18:11:13 who do we poke about this? I'd really rather not have to respin just to fix the artwork 18:11:38 ? 18:11:45 i got new artwork with a rawhide upgrade two days ago 18:11:52 i was kinda assuming it had made tc2, though i didn't check yet 18:11:56 adamw: https://bugzilla.redhat.com/show_bug.cgi?id=787261#c2 18:11:57 Bug 787261: unspecified, unspecified, ---, tcallawa, NEW, Fedora 17 Alpha TC1 still has all F16 artwork 18:12:36 oh, looks like there are beefy backgrounds but not an update to fedora-logos yet 18:12:53 * adamw has beefy-miracle-backgrounds-single and beefy-miracle-backgrounds-gnome 18:13:25 i think we poke mo and spot 18:13:28 i can do that 18:13:34 adamw: ok, thanks 18:14:01 #info it appears that the artwork does indeed exist but fedora-logos still needs to be updated 18:14:16 #action adamw to poke mo and spot about getting this done 18:14:21 oh, am i a chair? 18:14:25 adamw: you beat me to it 18:14:29 #chair adamw 18:14:29 Current chairs: adamw tflink 18:14:58 #action adamw to poke mo and spot about getting this done 18:15:14 #topic (736993) error install bootloader with serial interface install 18:15:17 #link http://bugzilla.redhat.com/show_bug.cgi?id=736993 18:15:19 Bug 736993: medium, unspecified, ---, pjones, ASSIGNED, error install bootloader with serial interface install 18:15:20 #info Accepted Blocker, ASSIGNED 18:16:05 sounds like there hasn't been progress on this 18:16:27 hmm, wwoods sent a serial patch, not sure if its related... 18:16:55 this isn't an accepted f17 alpha blocker 18:17:06 it was accepted as an f16 final blocker, then re-opened and nominated as an f17 alpha blocker 18:17:13 the 'acceptedblocker' field should have been cleared 18:17:19 adamw: ah, nobody cleared the field 18:17:25 bcl: could this be something that got fixed in 16.x and didn't get merged into 17.x? 18:18:17 doubtful, pretty much everything goes onto master. 18:18:18 so i'm -1 on this as an alpha blocker, i think we *still* haven't decided whether serial install should be a beta/final issue or never block at all, but we've always been pretty clear it doesn't block alpha 18:18:22 k 18:18:45 -1 alpha here. +1 final though. 18:19:04 I think wwood's patch is unrelated. 18:19:15 it would appear the TC2 KDE image still has the F16 artwork but the XFCE and Gnome images seem to have the beefy miracle fireworks .... just a random side note going back to the previous discussion about art 18:19:26 bcl: yeah, sounds like that to me, as well 18:19:36 the alpha criterion is "The installer must be able to complete an installation using the text, graphical and VNC installation interfaces", which intentionally excludes serial (and cmdline) 18:20:15 i think the intent was to broaden it out at beta / final criteria pages, but we so far haven't actually done that. 18:20:24 anyway, clearly -1 alpha. 18:20:37 proposed #agreed - 736993 - RejectedBlocker - This does not hit any of the alpha release criteria and the serial install criterion hasn't been decided for beta/final 18:20:46 ack 18:20:47 ack 18:20:52 re-propose for beta, for now, so it doesn't fall off 18:20:54 ack 18:20:56 ack 18:21:05 #agreed - 736993 - RejectedBlocker - This does not hit any of the alpha release criteria and the serial install criterion hasn't been decided for beta/final, re-propose for beta 18:21:28 #topic (785808) dracut Warning: "/dev/disk/by-label/Fedora\x2017-Alpha\x20i386" does not exist 18:21:31 #link http://bugzilla.redhat.com/show_bug.cgi?id=785808 18:21:34 #info Accepted Blocker, NEW 18:21:34 Bug 785808: unspecified, unspecified, ---, dgilmore, NEW, dracut Warning: "/dev/disk/by-label/Fedora\x2017-Alpha\x20i386" does not exist 18:21:44 and it sounds like this has been fixed 18:22:22 #info according to c#7, this has been fixed - needs to be closed 18:23:00 sounds like not a problem anymore. 18:23:04 +1 for close 18:23:11 ditto 18:23:12 it doesn't appear to be an issue in TC2 either 18:23:15 #action tflink to ask tester to close bug if it is indeed fixed 18:23:33 well 18:23:37 i'm not so sure this is exactly *fixed* 18:23:52 oh? 18:24:05 it may be simply that it's broken with the label used for a rats image, works with the label used for a tc 18:24:38 or, to make it more general, it's broken with rats composes, works with tc/rc composes 18:24:43 in which case it's not a blocker, but it's not *fixed* 18:24:54 #undo 18:24:54 Removing item from minutes: 18:24:58 i don't think we have the information to declare for sure that it's fixed, anyway - too many variables 18:25:27 so, request more testing? 18:25:51 huh? seems pretty simple. boot, no work. 18:26:23 and since it was reported pre-TC1 that would lend weight to it being invalid for current images. 18:26:49 my point is that rats images and tc images are somewhat different 18:27:00 so just the fact that it works with tc images doesn't mean the underlying bug is actually fixed 18:27:02 err, why the hell? 18:27:16 it might be the case that if we composed an image right now with the RATS labels / naming it might still not work 18:27:32 I don't know what RATS images are. but we ought to be testing the same stuff. 18:28:03 if i sound like i'm drooling to everyone, i probably am. 18:28:10 RATS -> Rawhide Anaconda Test S____ (can't remember what the S is) 18:28:17 automated test suite isn't it? 18:28:30 adamw: that would make more sense 18:28:37 * tflink learned something today :) 18:28:43 heh. 18:28:47 i thought it was Rawhide Acceptance Test Suite? 18:28:53 oh, i think you win the prize. 18:29:02 couldn't find any good links on it, though, so wasn't sure 18:29:07 at least one of us knows what it means 18:29:13 lol 18:29:15 okay, so one more try to explain 18:29:21 look at the report: the key error seems to be "dracut Warning: "/dev/disk/by-label/Fedora\x2017-Alpha\x20i386" does not exist" 18:29:37 i'm not sure the label for a TC image is actually in the same format 18:29:41 if it is, then fine, the bug is fixed 18:30:01 if i'm raving, then by all means tell me so, and we can close the bug and move on ;) 18:30:30 yeah, that sounds about right to me 18:30:33 * maxamillion fires up another TC2 image to check 18:30:34 It is. at least with the dumb hex spaces in there. 18:30:41 no longer a blocker, but may not be fixed 18:31:14 maxamillion: that won't help since the issue was with the RATS images 18:31:17 TC2's label is exactly that, but with x86_64 18:31:30 Is RATS blocker worthy? I would hope not. 18:31:51 tflink: but I thought he needed to know if the TC2 image label was the same format 18:31:55 bcl: no but like we said, probably not a blocker anymore but maybe not fixed 18:32:05 maxamillion: ah, I misunderstood then 18:32:07 bcl: in that case, i'm happy calling it fixed. 18:32:26 tflink: bcl says the labels are the same, in which case, my concern doesn't apply. 18:33:01 and we can just go ahead and close it. 18:33:14 sorry to delay. 18:33:16 proposed #agreed - 785808 - Close Bug - The labels from RATS are the same as TC2 and the issue no longer exists - the bug can be closed 18:34:19 #agreed - 785808 - Close Bug - The labels from RATS are the same as TC2 and the issue no longer exists - the bug can be closed 18:34:29 ok, that should be all the blockers to review 18:34:34 #topic open floor 18:34:47 adamw: it was a valid concern, just not one that most of us were familiar with 18:34:48 anything else that needs to be addressed or that I missed? 18:35:23 it sounds like we're going to have some test builds of anaconda/dracut soon 18:35:30 testing what exactly? 18:35:34 but that's less related to blocker review 18:35:44 adamw: the new dracut loader stuff 18:36:06 wwoods wants to test it a bit instead of just throwing it in for alpha right before the freeze 18:36:41 * tflink sets the fuse for ~ 5 minutes 18:36:51 #info Next Blocker Review Meeting: 2012/02/17 @ 17:00 UTC in #fedora-bugzappers 18:37:13 * adamw missed that one entirely. 18:37:30 adamw: it was in #fedora-qa right before the blocker meeting 18:37:59 feh, i was busy flaming people on devel! 18:38:08 yeah, that thread is turning epic 18:38:30 adamw: productivity-- :) 18:38:33 it's making me think about the new anaconda testing stuff we talked about @ FUDCon, though 18:38:57 er, stuff for testing the anaconda changed planned for F18 18:40:41 ok, thanks for coming everybody! 18:40:51 * tflink will send out minutes shortly 18:40:54 #endmeeting