15:00:21 <jlaska> #startmeeting Fedora QA Meeting
15:00:21 <zodbot> Meeting started Mon Apr 11 15:00:21 2011 UTC.  The chair is jlaska. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:21 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:26 <jlaska> #meetingname fedora-qa
15:00:26 <zodbot> The meeting name has been set to 'fedora-qa'
15:00:33 <jlaska> #topic Roll Call
15:00:42 * jsmith his here (but on conference calls)
15:00:53 <jlaska> helloooo
15:00:58 * jskladan is here
15:01:05 * tflink is present
15:01:17 * vhumpa says hey everybody
15:01:45 * maxamillion is here-ish
15:01:49 <adamw> yo
15:02:31 <jlaska> who are we missing ... kparal is lurking, robatino, Viking-Ice, anyone else?
15:02:38 * kparal here
15:02:52 <jlaska> btw ... I may be distracted for a portion of the meeting today
15:03:02 <jlaska> Our good friend kparal agreed to #chair if needed
15:03:06 <jlaska> #chair kparal
15:03:06 <zodbot> Current chairs: jlaska kparal
15:03:16 * kparal sits
15:03:18 <jlaska> :)
15:03:24 <jlaska> Let's get started ...
15:03:31 * maxamillion feels kparal got set up on that one :P
15:03:35 <jlaska> #topic Previous Meeting Follow-up
15:03:36 <jlaska> haha
15:03:47 <jlaska> #link https://fedoraproject.org/wiki/QA/Meetings/20110411
15:03:58 <jlaska> #info adamw will add a 'gnome fallback mode' to the F-15-Beta Desktop test matrix
15:04:07 <jlaska> added and the template was updated as well
15:04:18 <jlaska> we can talk more about what's in the matrix later on
15:04:35 * rbergeron lurks too
15:04:42 <jlaska> hi rbergeron
15:04:44 <jlaska> #info jlaska to discuss next anaconda build with clumens for RC1
15:05:00 <jlaska> discussed and we now have anaconda-15.27-1 ... which seems to be holding up pretty good so far
15:05:21 <jlaska> #info adamw + jlaska review blockers and discuss need for TC2 images
15:05:33 <jlaska> reviewed, discussed and denied!
15:05:34 <jlaska> :)
15:06:02 <jlaska> Same as what we discussed in the meeting last week, there weren't any major installation blockers that warranted another set of install images
15:06:08 <jlaska> #info jlaska will check-in with jforbes on the upcoming Virtualization test day
15:06:35 <maxamillion> which ever anaconda version is in Beta RC2 worked like a champ
15:06:47 <jlaska> I spoke (typed) w/ jforbes already, and need to check-in again to see how we can help with the virt event.  The wiki page is up and we can talk more about virt test day later ...
15:06:52 <jlaska> maxamillion: cool!
15:07:00 <jlaska> speaking of ...
15:07:01 <satellit__> bug 694712? cannot install to VirtualBox atm
15:07:06 <jlaska> #topic F-15-Beta RC2 status
15:07:07 * Viking-Ice half here half fixing his native iptables service files
15:07:16 <jlaska> vhumpa: heh, okay :)
15:07:20 <jlaska> ergh ... Viking-Ice ^^^
15:07:30 <jlaska> #info We have until Wednesday (2011-04-13) to complete testing of the installation and desktop matrices
15:07:45 <adamw> satellit_: 694712 is fixed in rc2.
15:07:48 <jlaska> #info Test results at https://fedoraproject.org/wiki/Category:Fedora_15_Beta_RC_Test_Results
15:08:00 <satellit__> : )
15:08:16 <jlaska> #info Monitor proposed and accepted blocker bugs - https://fedoraproject.org/wiki/Current_Release_Blockers
15:08:30 <jlaska> okay, now for the details ... how are these matrices holding up so far
15:09:07 <adamw> rhe reckons install is looking good so far.
15:09:16 <jlaska> awesome-ness
15:09:30 <adamw> desktop also looks good, we have most results in for gnome and kde.
15:09:43 <jlaska> holy cow, we've got almost all installation results in already
15:09:49 <adamw> i think you were worried about issues with upgrades, right?
15:10:13 <jlaska> I hit some odd stuff doing a F-14 (default) -> F-15 using preupgrade
15:10:25 <adamw> right, though we have checkmarks for preupgrade pulled in from rc1
15:10:32 <jlaska> I'll get started on tracking those issues down and filing if needed
15:10:35 <adamw> i was planning to see if i can reproduce your issues
15:10:36 <jlaska> yeah, preupgrade itself works great
15:10:58 <jlaska> adamw: oh thanks ... it could certainly be something specific in how I was testing.  So I need to re-run also
15:11:14 <adamw> well, our criteria do now specify that we expect upgraded systems to work
15:11:21 <jlaska> right
15:11:22 <adamw> so serious bugs post-upgrade can be an issue
15:11:44 <jlaska> and they did ... but some slight modifications were needed.  But ... will retest and see if Cranes was seeing things
15:12:07 <adamw> cool
15:12:11 <adamw> aside from that we're looking nice on rc2
15:12:14 <jlaska> outside of the wiki matrices, any other feedback to share?
15:12:30 <maxamillion> oh, speaking of pre-upgrade .... I have a friend who's trying to pre-upgrade and it keeps throwing errors about trying to download things that don't exist ... is there something that changed repo side that needs tweaking on the preupgrade side to work?
15:12:51 <jlaska> maxamillion: make sure you are using the latest preupgrade
15:13:06 <jlaska> which reminds me ... we need to give it karma
15:13:07 <maxamillion> jlaska: I'll ping him later ... that might be his problem :X
15:13:08 <jlaska> before release
15:13:16 <jlaska> preupgrade-1.1.9-1.fc14
15:13:23 <jlaska> nm ... bodhi lists it as 'stable' already
15:13:33 <maxamillion> :)
15:13:47 <jlaska> adamw: 0 proposed blockers ... yay
15:14:06 <jlaska> 1 accepted blocker still in MODIFIED (https://bugzilla.redhat.com/693588)
15:14:32 <adamw> we can close it, the update went stable.
15:14:38 <adamw> it didn't happen automatically as the bug id wasn't in bodhi.
15:14:40 <jlaska> perfect
15:15:04 <jlaska> alright, if nothing else on the Beta ... let's move to everyones favorite time .. Upcoming QA events!
15:15:26 <jlaska> #topic Upcoming QA Events
15:16:02 <jlaska> #info Wednesday, April 13 - F-15-Beta Go/NoGo meeting @ 21:00 UTC
15:16:15 <jlaska> unless we want to adjust the time ... I believe it's still 5pm EDT
15:16:29 <jlaska> ergh ... delivery.  Kparal, do you mind taking over?
15:17:16 <kparal> jlaska: ok
15:17:19 * jlaska walking through agenda at https://fedoraproject.org/wiki/QA/Meetings/20110411
15:18:02 <kparal> #info Thursday, April 14 - Virtualization Test Day
15:18:38 <kparal> there doesn't seem to be many test cases there
15:18:50 <kparal> is someone working on that?
15:19:18 <adamw> should be jforbes
15:19:26 <adamw> i will check in with him and make sure he's on schedule
15:19:26 <kparal> any volunteer to check with jforbes and rwmjones the status?
15:19:44 <kparal> #action adamw check the progress of tests cases in Virt Test Day
15:19:46 <kparal> adamw: thanks
15:19:50 * kparal coming up to speed
15:20:03 <kparal> #info Thursday, April 21 - GNOME3 Test Day #3
15:20:22 <kparal> our highly awaited test day
15:20:35 <adamw> yaay
15:20:36 <kparal> vhumpa: any more work to be done?
15:20:57 <vhumpa> Looks like it is mostly a questions of polishing the test set
15:21:37 <vhumpa> I was talking with Radek today, not really many ideas for new testcases due to new functionality
15:21:40 * jlaska back
15:22:03 * kparal was not very effective, giving back the leadership
15:22:23 <jlaska> hah, whatever
15:22:36 <jlaska> anything else on the GNOME3 test day?
15:23:32 <jlaska> well, we'll stay tuned to vhumpa and rlat for any future updates
15:23:35 <vhumpa> We will likely ad just about one test case and are thinking about removing some to reduce a number of them just a little bit so that testers dont get scared this time :)
15:23:44 <jlaska> oh, I spoke too soon
15:23:50 <jlaska> cool
15:23:57 <vhumpa> That is just about it :)
15:23:59 <jlaska> thanks vhumpa
15:24:03 <vhumpa> Will keep you posted
15:24:14 <jlaska> that's all I had for upcoming QA events
15:24:25 <jlaska> this of course assumed an on-time Beta hand-off :)
15:24:36 <jlaska> but, we'll let the criteria do the talking for that
15:24:46 <jlaska> #topic Nitrate project update
15:25:18 <jlaska> Samuel asked about nitrate project status last week .. so I just wanted to add some links to the meeting in case anyone else was following
15:25:30 <jlaska> and of course, Hurry can add more details if needed
15:25:39 <jlaska> #info Track package review - https://bugzilla.redhat.com/show_bug.cgi?id=690728
15:25:59 <jlaska> #info RFR (infrastructure) to setup a demo instance - https://fedorahosted.org/fedora-infrastructure/ticket/2673
15:26:06 <jlaska> #link https://fedoraproject.org/wiki/Tcms_feature_requirements
15:26:30 <jlaska> I think rhe made contact with nb with regards to the RFR.  I'm not sure where that stands presently
15:26:43 <jlaska> but I do believe thats the next big hurdle
15:26:59 <jlaska> The package review is getting some good feedback, which is great
15:27:41 <jlaska> So that's all I have here ... I know Hurry has been juggling this along with testing this release.  I know she has a lot more details for anyone that is interested
15:27:55 <jlaska> #topic Bruno Updated QA Spin kickstart
15:28:20 <jlaska> You may have seen Bruno's post to test@ today, but he made some changes to the QA spin kickstart
15:28:38 <jlaska> #info The full changes can be observed in the git shortlog - http://git.fedorahosted.org/git/?p=spin-kickstarts.git
15:28:52 <jlaska> #info Over the weekend I updated the QA Test Day spin to make the Desktop entries favorites instead
15:29:02 <jlaska> #info I also set these up so that they persist over an install (assuming that would make more sense for testing)
15:29:08 <jlaska> #info Firefox is also set to go to the current test day page even when not run as a fovorite and it will not display the welcome page on first use.
15:29:25 <jlaska> If there are any other changes we'd want for the QA spin ... just let bruno know
15:29:47 <jlaska> I'd like to inspect his changes in a little more detail, kind of curious how we enable application favorites in the shell now
15:30:09 <jlaska> Okay, that's all I had on my list ... time for open-discussion
15:30:12 <jlaska> #topic Open discussion - <Your topic here>
15:30:29 <nb> jlaska, /me has a little
15:30:40 <nb> on the nitrate topic
15:30:40 <jlaska> Anything not already discussed, that folks would like to discuss?
15:30:54 <jlaska> nb: nice, what's up?
15:30:57 <nb> 1. what OS are you wanting, RHEL5 or 6?
15:31:25 <nb> or Fedora?
15:32:15 <jlaska> nb: I don't know off-hand, but I can ask rhe and the nitrate-devel folks.  The wiki doc says it is python-2.4 compliant, so RHEL5 should work
15:32:26 <jlaska> but I'll pass along that question to rhe and company
15:32:32 <nb> It'll probably consist of first, you getting it set up on a publictest server, then setting everything up in puppet, and then we'll figure out where it's going to go on the production servers
15:33:08 <nb> thats about all i have at the moment
15:33:22 <nb> once i figure out what OS to use, i'll find you a publictest server to use
15:33:22 <jlaska> nb: okay, so we just need to determine what OS/release is needed
15:33:30 <nb> and get the appropriate people in the appropriate groups
15:33:37 <jlaska> great, thanks
15:33:53 <nb> oh kevin commented on your ticket also
15:34:35 <bk> one thing i would like to know is about what timeframe are updates pushed to the repo
15:34:47 <jlaska> oh boy, he did ... and I completely missed that :(
15:35:21 <jlaska> bk: are you speaking about nitrate, or are you referring to the F-15 'base' and 'updates-testing' repositories?
15:35:32 <jlaska> nb: I'll reply to kevin in the trac ticket
15:35:41 <bk> jlaska: f15 base and updates-testing, sorry i didnt specify
15:36:03 <jlaska> bk: updates are pushed once a day (unless there are failures generating the repos)
15:36:15 <bk> do we know what time or just any time?
15:36:45 <jlaska> #info nb provided some feedback for nitrate publictest instance.  Need to say what OS/release is required
15:36:58 <jlaska> bk: I don't know ... rel-eng would be best to ask for that
15:37:28 <jlaska> dgilmore: Are the repo's updated about the same time everyday, or does it change?
15:37:33 <bk> jlaska: ok thanks, what are the main objectives for this channel? also is -qa the best place to discuss bugs or?
15:37:47 <jlaska> bk: this change is a shared IRC meeting channel
15:38:05 <dgilmore> jlaska: which repos
15:38:17 <jlaska> bk: Yes, #fedora-qa (and test@lists.fedoraproject.org) is a good place to discuss quality issues, bugs and diagnosing failures
15:38:24 <dgilmore> jlaska: different repos are done differently
15:38:27 <jlaska> bk: which repos, were you speaking of F-15?
15:38:32 <bk> jlaska: ok awesome, thanks
15:38:42 <bk> jlaska: yes, f15
15:38:46 <jlaska> dgilmore: ^^
15:39:29 <bk> im running the first alpha right now (used live cd but was told updating via yum will be the same as what others have) and was just wondering really when the base repo was updated for core features etc
15:39:40 <dgilmore> jlaska: which one
15:39:48 <dgilmore> stable or updates-testing
15:39:51 <jlaska> yes :)
15:39:52 <bk> but also for gnome, but i can ask in gnome for that on gimpnet
15:40:02 <tflink> bk: are you talking about updating the livecd or an install based on the livecd?
15:40:04 <dgilmore> stable is done via a nightly cron job
15:40:09 <satellit_> when will the nightlys get anaconda that installs yesterdays desktop live failed to install to Virtualbox   RC2 here live is working downloaded just now
15:40:13 <dgilmore> so it should always land around the same time
15:40:15 <bk> tflink: not sure i understand the question
15:40:25 <dgilmore> but the updates-testing is manuulay run so we can sign the rpms
15:40:28 <dgilmore> and that does vary
15:40:29 <tflink> bk: are you looking to update a livecd that you are currently running?
15:40:46 <jlaska> dgilmore: I see, thanks for the info
15:41:10 <dgilmore> jlaska: np
15:41:10 <bk> tflink: basically yes, but was told i cannot update from alpha>beta since i used the live cd, so i was told if i just did a yum update i would be getting the same things as others are getting, so basically no need to switch to the beta
15:41:50 <tflink> bk: on second thought, this probably isn't the best place to have this conversation - propose moving it to #fedora-qa so that the meeting can end
15:41:58 <bk> tflink: the reason i used the livecd is because i had to use usb and only had a 2gb
15:42:00 <bk> ok
15:42:22 <jlaska> satellit_: should be any minute now ... anaconda-15.27-1 is marked for stable and has been pushed
15:42:29 <jlaska> Any other business to discuss in this meeting?
15:42:31 <satellit_> thanks
15:42:38 <jclinton> Is Ethernet enabled by default in the test criterial anywhere?
15:42:50 <jclinton> Installed RC2 last night on a desktop and it wasn't
15:43:07 <jlaska> jclinton: it largely depends on how you install
15:43:13 <jclinton> From the ISO
15:43:32 <jlaska> if you do a non-network installation, and don't manually enable networking during installation, you won't have networking automatically connected after installation
15:43:35 <maxamillion> RC2 on my machine was enabled by default this morning ... but Xorg causes a kernel panic about 90-ish seconds into every gnome session so I've given up
15:43:56 <adamw> jlaska: that fail isn't on anaconda, it's the dracut issue. it gets fixed when dracut goes to stable.
15:44:01 <adamw> jlaska: which dgilmore just pushed, i think.
15:44:05 <jclinton> jlaska: but firstboot offers NTP config. which *does* activate networking but fails to tell NM about it
15:44:16 <jlaska> adamw: great, thanks ( satellit_ see adamw's comment)
15:44:28 <jlaska> jclinton: please file a bug
15:44:40 <jclinton> i'm asking if this should be criteria or not
15:44:48 <jclinton> hence my first question
15:44:51 <jclinton> which was ignored
15:45:07 <adamw> it's not, no
15:45:12 <jclinton> fine
15:45:18 <jlaska> I don't think that impacts the criteria, and I wouldn't add criteria requiring networking to be automatically enabled in all cases
15:45:25 <adamw> we consider it an implied criterion that networking should *work*, but not that it should be enabled by default
15:45:34 <dgilmore> adamw: i did just push it
15:46:08 <adamw> dgilmore: cool. could you do a compose some time before the official beta release too? so that network installs will get the correct package set
15:46:26 <dgilmore> adamw: what do you mean?
15:46:35 <dgilmore> adamw:  the compose has all the packages we pushed
15:46:45 <adamw> dgilmore: er, i mean, of dist-f15
15:46:57 <jlaska> #info jclinton asked about network-related release criteria, and whether the network should be enabled in all cases
15:46:57 <adamw> dgilmore: whatever has to be done to make sure all the packages we pulled into rc2 are in the 'f15' repo on mirrors
15:47:06 * adamw always sucks at terminology
15:47:06 <dgilmore> adamw: oh that happens
15:47:09 <adamw> ok cool.
15:47:17 <dgilmore> adamw: the tree that we composed from is what gets pushed
15:47:30 <dgilmore> adamw: its just sitting there waiting for the green light
15:47:43 <dgilmore> adamw: we only make the isos available for testing
15:47:46 <dgilmore> and not teh repos
15:48:36 <jlaska> okay, last call for topics
15:48:39 * jlaska sets fuse for 2 mins
15:49:36 <jlaska> 1 minute ...
15:50:32 <jlaska> okay, thanks everyone
15:50:37 <jlaska> I'll send minutes to the list later today
15:50:39 <jlaska> #endmeeting