15:00:02 #startmeeting Fedora QA meeting 15:00:02 Meeting started Mon Mar 13 15:00:02 2017 UTC. The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:02 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:02 The meeting name has been set to 'fedora_qa_meeting' 15:00:08 #meetingname fedora-qa 15:00:08 The meeting name has been set to 'fedora-qa' 15:00:14 #topic Roll call 15:00:21 morning everyone, who's here for qa meeting? 15:00:36 * tenk is here 15:00:42 * kparal is here 15:00:43 * pschindl_wfh is here 15:00:59 * Sumantrom is here 15:01:02 * coremodule is here. 15:02:05 * roshi is here 15:02:29 * a2batic is here 15:02:36 morning folks 15:02:39 * cmurf thinks DST is for the birds, but then realizes even they've rejected this nonsense 15:02:47 #chair kparal roshi 15:02:47 Current chairs: adamw kparal roshi 15:02:49 cmurf: right? 15:03:00 Or did I say that 6 months ago? 15:03:01 let's all move to alberta 15:03:16 Morning adamw 15:03:17 is there good fishing in alberta? 15:03:24 pretty sure 15:03:36 i mean, i guess it depends whether you're the fish 15:03:43 if I can hunt and fish, sign me up :p 15:06:22 welp. let's get going then! 15:06:37 #topic What Adam Didn't Do Last Week 15:06:39 ;) 15:06:42 #topic Previous meeting follow-up 15:07:45 #info "adamw to look into Kerberos credential cache Change and see if it's significant" - didn't do that yet as there are more urgent breakages in FreeIPA bits 15:07:51 #action adamw to look into Kerberos credential cache Change and see if it's significant 15:07:59 that was the only action item on the list, any other follow-up? 15:09:22 * roshi has nothing 15:09:46 aallllrighty 15:09:53 #topic Fedora 26 status 15:09:57 so, just a quick F26 check-in 15:10:19 #info Fedora 26 Alpha freeze is in effect, Go/No-Go meeting is this Thursday 15:10:35 we'll have blocker review after this meeting, there seems to be quite a mess with FreeIPA ATM 15:10:50 ooh, fun 15:11:22 I've mostly been following up on that, are things looking OK in other areas? 15:11:31 anyone know of any other significant issues? 15:11:46 * roshi has been slacking in the Alpha readiness dept, but I don't know of anything 15:14:01 * Sumantrom and coremodule has mailed the test day owners of for dnf 2.0 , MBS and anaconda blivet GUI. The dnf change owners have replied that they will respond to ticket on Pagure #495 . 15:14:33 Awaiting response from rest of the change owners 15:14:57 so we sent out the call for test days or were you reaching out directly to change owners? 15:15:22 we sent out the call a while back, right sumantro? 15:15:33 Directly to the change owners. We didn't call anything yet. 15:15:34 * pwhalen notes arm should look good, checking on the selinux build (fix loading kernel modules) 15:15:40 #info there are several problems in the area of FreeIPA for Alpha, aside from that we're not aware of major issues at the present time 15:15:47 pwhalen: thanks 15:17:05 Yes adamw we sent out the call and most of the owners were waiting for the branch ..Now that it's out , we are all set to move along 15:18:20 if we haven't sent out the call for test days to test-announce, we probably should 15:20:21 Changes have to appear in alpha don't they? 15:20:24 it went out a while ago. 15:20:30 cmurf: they're supposed to be 'code complete' by alpha, yeah. 15:21:37 #info Test Day process is moving along now Alpha freeze is in place, sumantro is following up with proposed Test Day owners 15:23:06 welp, sounds like that's it 15:23:08 #info Automated update testing 15:23:34 so just wanted to mention this, for anyone who missed it: we're now running some of the openQA tests on Bodhi updates 15:25:20 \o/ 15:25:24 you can see the results at https://openqa.fedoraproject.org/group_overview/2 15:25:26 shiny 15:25:29 It lives 15:25:39 it's broken for F26 updates ATM, which explains the ones where there's a ton of failures, i'll look into that today 15:26:19 #info openQA testing of Bodhi updates to critical path packages is now live: see https://openqa.fedoraproject.org/group_overview/2 15:26:23 Adamw yeeeh!! 15:26:36 #info currently broken for Branched, we will try and fix this soon 15:26:57 we're planning to hook this up to the Bodhi web UI soon, so the results will be visible there alongside the taskotron results 15:27:16 fedfind seems confused about -r 26 15:27:43 that's not the problem the openqa tests are having... 15:27:45 how do you mean? 15:28:07 no results 15:29:04 Oh I see - it just doesn't like -r by itself 15:29:16 nevermind 15:30:29 yeah, it'll treat that as 'stable release 26'. 15:30:36 anyhoo 15:30:46 any thoughts / notes on the update testing stuff? 15:31:01 * roshi has nada 15:31:36 The ticket on test day with update testing.. when are we planning for that ? 15:32:04 It's like final freeze - 2 weeks or something much closer? 15:33:32 Sumantrom: sorry, which test day? 15:33:47 Adamw , it's the email that you sent me and coremodule 15:34:15 Which mentioned something about calling for a update testing test day. 15:34:35 Somewhere closer to the final freeze. 15:36:30 oh 15:36:32 *upgrade* testing 15:36:53 Oops my bad ... Really sorry !!! 15:37:13 it's ok, just update/upgrade can be confusing :) 15:37:41 i think yeah, the initial idea of a little before Final freeze would be best 15:38:37 Got it :) 15:40:43 #topic Atomic PRD 15:40:50 so...roshi, I believe this is a thing now? 15:40:56 it is 15:40:57 Is it done? 15:40:59 has been for a bit 15:41:36 it's been brought up the last few QA meetings calling for feedback, and I haven't seen any, so I was under the impression people thought it was good to go (I might have missed feedback though?) 15:42:13 yeah, I just wanted to give it a bit more prominence 15:42:19 what's the link again? 15:42:40 jas 15:42:53 https://fedoraproject.org/wiki/Atomic/PRD 15:42:56 https://fedoraproject.org/wiki/Atomic/PRD 15:43:02 lol 15:43:38 adamw loses urls so just as well we give them in duplicate 15:43:39 heh 15:44:19 ha 15:44:29 * roshi should look before he pastes 15:44:42 feedback still to cloud@ ? or is there an atomic list now? 15:45:10 still to cloud, or file an issue on pagure 15:45:18 rgr 15:45:21 https://pagure.io/atomic-wg 15:45:28 #info the updated Atomic PRD is available at https://fedoraproject.org/wiki/Atomic/PRD , please read through it to familiarize yourself with the aims for the Atomic deliverables, and send any feedback you have to cloud@ (or file an issue at https://pagure.io/atomic-wg ) 15:45:32 that's where they seem to be tracking pretty much everything 15:46:00 I'm not certain what deliverables are blockign 15:46:09 roshi: have you given any thought yet to getting from the PRD to some kind of testing requirements definition? 15:46:42 this doesn't seem to be any different 15:46:42 cmurf: well, https://fedoraproject.org/wiki/Releases/26/ReleaseBlocking is for tracking that, but the question is a bit tricky for Atomic 15:46:45 https://fedoraproject.org/wiki/Releases/26/ReleaseBlocking 15:46:52 as Atomic doesn't really follow the release schedule 15:46:56 right 15:47:02 so blocking doesn't mean the same thing anywya 15:47:28 adamw: from what I can tell, I really think it's going to be whatever we (Atomic WG) can get automated, with random smoke tests 15:47:34 DST drunkeness, can't type, duplicate urls, can't use fedfind, what's next? 15:47:50 cmurf: =) 15:48:16 between autoQA doing the install testing, and the tests we're working to get into taskotron, I think that's going to be the extent of the testing 15:48:32 roshi: openqa 15:48:48 damnit, that's what I typed first, and erased it because I thought it was wrong 15:48:50 =) 15:48:51 lol 15:48:51 you weren't even around during the autoqa days - how do you manage to mix those up? 15:48:54 one day, i'll get you all reprogrammed 15:48:57 inorite? 15:49:19 I knew it was a buzzprefix-qa of some kind 15:49:33 open, auto, cloud, synergy, TPSReport 15:49:38 maybe we should have kept the autoqa name - it certainly seems to have staying power :) 15:49:41 roshi: hmm, okay. do you think it would be useful to at least have a formal definition of the functionality requirements the automated tests are supposed to be enforcing, or can the PRD serve that purpose on its own? 15:49:52 tflink: i'll see if the suse folks want to rename openqa :P 15:50:00 SynergyQA! 15:50:11 I think having it formally declared would be good, but I haven't gotten to it yet 15:50:21 or gotten to telling the WG that would be a good idea 15:50:37 OK 15:51:01 is it OK if I give you an action item to move forward with that somehow? you got an idea of where to go, or need any help? 15:51:10 yeah, that's fine 15:51:25 I don't think so, but I'll write a thing up and get some feedback 15:52:08 #action roshi to draft up some sort of formal functional requirements / release criteria / something for Atomic 15:52:12 there, that's nice and vague! 15:52:51 #topic Open floor 15:52:57 alrighty, that brings us to open floor 15:52:59 any other business? 15:54:49 * roshi has nothing 15:55:12 .fire roshi 15:55:12 adamw fires roshi 15:55:40 not the first time, and certainly not the last :p 15:55:51 .fire up the smoker 15:55:51 adamw fires up the smoker 15:56:44 :P 15:56:48 allllrighty then, thanks for coming, folks 15:56:52 go no go thursday? 15:57:03 there'll be a blocker meeting in #fedora-blocker-review in 3 minutes, led by some doofus who just got fired 15:57:08 cmurf: yup yup 15:57:16 thanks for coming out, everyone! 15:57:18 * adamw sets teh fuse 15:57:30 whee! 15:57:35 exit 15:58:19 #endmeeting