16:01:13 <eglute> #startmeeting interopwg
16:01:14 <openstack> Meeting started Wed Apr  4 16:01:13 2018 UTC and is due to finish in 60 minutes.  The chair is eglute. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:15 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:17 <openstack> The meeting name has been set to 'interopwg'
16:01:24 <eglute> #chair hogepodge markvoelker
16:01:24 <openstack> Current chairs: eglute hogepodge markvoelker
16:01:31 <eglute> #topic Agenda
16:01:35 <eglute> hello everyone!
16:01:40 <markvoelker> o/
16:01:41 <kbaikov> hello
16:01:45 <kbaikov> o/
16:01:53 <eglute> today's agenda: #link https://etherpad.openstack.org/p/InteropWhistler.10
16:01:58 <eglute> please update as needed
16:02:46 <eglute> anyone else here for the interop meeting?
16:02:49 <mguiney> o/
16:02:57 * eglute waves
16:03:24 <eglute> #topic Creating orchestration.2018.02.json guideline
16:03:34 <eglute> #link https://review.openstack.org/#/c/547692/
16:03:34 <markvoelker> o/
16:04:02 <eglute> so this one actually has all the relevant bits pulled in from the patch that Rico commented
16:04:38 <eglute> markvoelker if you would not mind taking a quick look and merging it when you have a chance?
16:04:58 <markvoelker> will do (sorry, pulling double duty this morning) =)
16:05:22 <eglute> thank you markvoelker
16:05:34 <eglute> #topic Move next.json to schema 2.0
16:05:41 <eglute> #link https://review.openstack.org/#/c/554395/
16:06:16 <eglute> this one is eroring out cause something is still checking against the old schema
16:06:48 <eglute> markvoelker not sure if you had a chance to look at it
16:07:00 <markvoelker> I've started picking at it but not sure what's wrong yet
16:07:15 <markvoelker> I did get the jobs docs failure sorted though
16:08:39 <eglute> cool
16:09:56 <eglute> markvoelker do you think you will have time in the next 2 weeks?
16:10:21 <markvoelker> I've blocked some time to poke at it again tomorrow morning, so will hopefully get it worked out then
16:11:06 <eglute> awesome thanks
16:11:27 <eglute> #topic Missing/renamed tests
16:11:50 <eglute> kbaikov brought up today the fact that we still have missing tests in the guideline
16:12:07 <eglute> kbaikov which guideline were you trying to use?
16:12:13 <kbaikov> 2018.02
16:12:29 <mguiney> which tests appear to be missing?
16:12:41 <eglute> Dirks comment in here:  https://review.openstack.org/#/c/554359/
16:13:03 <eglute> "The changeset https://review.openstack.org/#/c/396159/ also deleted this test - can you flag it as well please?"
16:13:33 <eglute> looks like cinder tests
16:13:40 <mguiney> apparently havent had enough coffee yet, thank you for the list
16:14:15 <eglute> so we need another patch
16:14:27 <markvoelker> I think those were dealt with in an alias....there are passing tests now with the current 2018.02 guideline
16:14:37 <markvoelker> Example: https://refstack.openstack.org/#/results/21c2f5b7-09d4-4478-92ed-030b77aca33e
16:14:42 <eglute> ah ok
16:14:52 <mguiney> ^ was going to ask if we wanted to alias or remove the tests from the list, in this case
16:14:59 <eglute> kbaikov says he has issues with those?
16:17:32 <eglute> ok... we will wait for kbaikov to get back to us later
16:17:44 <eglute> unless other comments?
16:18:05 <eglute> #topic Build Gate Job against Tempest
16:18:10 <eglute> i think this was hogepodge?
16:18:43 <eglute> i dont have any updates on this from Chris, and he doesnt appear to be at this meeting
16:18:52 <kbaikov> ah, sorry
16:19:15 <eglute> kbaikov, go ahead
16:19:31 <mguiney> kbaikov: do you have logs showing the traceback from the test failures in greater detail?
16:19:54 <kbaikov> yes, i do not pass those because of the missing test. See example here: https://refstack.openstack.org/#/results/87aa93c9-7de5-4c80-a379-e296a950d866
16:20:30 <mguiney> yes, just wondering what the actual traceback is saying
16:20:50 <kbaikov> there are no failures. This test is just not in tempest. It was renamed. Or became tempest private test
16:20:52 <mguiney> as is, the results uploaded to refstack server have very little in the way of information to debug with
16:20:59 <kbaikov> so i was thinking if we can flag it
16:21:42 <mguiney> it's essentially a list of passed tests. so it wasnt showing when you tested locally as a test failure, only threw errors re: its absence when you uploaded the result?
16:22:25 <mguiney> good news is, it looks like the tests in question are already flagged :)
16:23:29 <mguiney> in fact, it looks like the openstack instance you are testing against has a 100% pass rate against all unflagged required tests, meaning that it meets the guideline requirements :)
16:23:32 <kbaikov> The thing is that if the test was skipped by tempest, because it just did not find it; the refstack will add it to failed
16:24:35 <kbaikov> mguiney: i am confused. where do you see that? it tells me this: Excluding flagged tests, this cloud passes 99.7% (329/330) of the required tests.
16:25:09 <mguiney> 21c2f5b7-09d4-4478-92ed-030b77aca33e is the test id, correct?
16:25:09 <kbaikov> my failing non flagged test is this: tempest.api.compute.volumes.test_attach_volume.AttachVolumeTestJSON.test_list_get_volume_attachments
16:25:48 <kbaikov> mguiney: no. this one: https://refstack.openstack.org/#/results/87aa93c9-7de5-4c80-a379-e296a950d866
16:26:14 <mguiney> ok, it looks like i was looking at the incorrect result, then
16:26:43 <kbaikov> the 030b77aca33e result was from markvoelker
16:26:56 <mguiney> whoops, taking a look now
16:27:51 <markvoelker> Hmm, I though that got fixed in https://review.openstack.org/#/c/554359/
16:28:16 <markvoelker> nope, different test
16:28:19 <markvoelker> crap
16:28:44 <markvoelker> Ok, looks like we do have some work to do then
16:28:55 <eglute> Any volunteers?
16:29:14 <markvoelker> I'll take it...should be quick and I can probably knock it out today.
16:29:19 <eglute> thank you markvoelker
16:29:32 <kbaikov> super cool, guys. Thanks!
16:29:40 <mguiney> I can handle it, if you don't have the time
16:29:48 <eglute> thanks markvoelker and mguiney
16:30:37 <markvoelker> mguiney: I'll probably grab a sammich after this and my next meeting and knock it out then...if you don't see a patch up from me in a few hours feel free to jump on it. =)
16:30:48 <eglute> :)
16:30:59 <mguiney> sounds good, would just be the addition of a flag, yes?
16:31:22 <markvoelker> Yeah, I just need to check on something upstream in tempest too.  Should be trivial
16:31:34 * mguiney nods
16:32:15 <eglute> ok... so back to the gate job
16:32:38 <eglute> mguiney do you have any updates on that from hogepodge?
16:32:53 <mguiney> Not that i'd heard of, unfortunately
16:33:28 <eglute> ok, will skip this topic for today then
16:33:38 <eglute> #topic Next guideline: 2018.08
16:34:01 <eglute> I havent seen any patches on scoring
16:34:18 <eglute> mguiney or markvoelker any updates on those? I haven't looked yet
16:34:46 <mguiney> not as of yet, should be able to get started on that this week
16:34:47 <markvoelker> I've started looking into it, but no patches forthcoming just yet (and I'm traveling in Europe next week so probably not then either)
16:35:14 <eglute> cool, we still have time
16:35:44 <eglute> georg let me know he is not going to be here today, so no updated on NFV from him
16:36:07 <eglute> i think that covers today's meeting, is there anything else we should discuss?
16:36:48 <markvoelker> One quick thing: DST change.  Does this meeting time still work for folks?  I assume so but figured I'd ask. =)
16:37:01 <eglute> works for me!
16:37:16 <eglute> i assume it is better this way for those in pacific time zone...
16:37:45 <mguiney> works for me, yes
16:38:38 <eglute> cool! anything else?
16:39:16 <eglute> thanks everyone!
16:39:19 <eglute> #endmeeting