09:07:39 <gmann> #startmeeting qa
09:07:40 <openstack> Meeting started Thu Jan 10 09:07:39 2019 UTC and is due to finish in 60 minutes.  The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:07:41 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:07:44 <openstack> The meeting name has been set to 'qa'
09:07:49 <gmann> who all here today ?
09:08:11 <frickler> o/
09:08:49 <gmann> frickler: hi
09:09:21 <frickler> gmann: welcome back, hope you had a good time off
09:09:49 <gmann> frickler: thanks. yeah it was nice. but I am still reading my emails...
09:10:31 <gmann> #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours
09:11:00 <gmann> this is agenda for today ^^ but I think I have not prepared all the items yet
09:11:06 <gmann> for this week
09:11:22 <gmann> i will jump around open discussion and anything we want to discuss
09:12:49 <gmann> one update is to get the number for coming  PTG attendance from QA side.  i will check with other members via emails also.
09:13:00 <gmann> frickler: will you be able to make it to denver in april ?
09:13:07 <mbindlish> hi
09:13:15 <gmann> mbindlish: hi
09:13:24 <frickler> no, no PTG or summit for me in Denver
09:14:20 <gmann> ohk
09:16:37 <gmann> other item I want to bring is multinode job on stable branch. I have replied on ML also. currently tempest multinode job 'tempest-multinode-full' is restricted to run on master only
09:17:01 <gmann> which i am trying to make it for pike onwards but getting failure for pike, queens migration tests
09:17:10 <gmann> #link https://review.openstack.org/#/q/topic:tempest-multinode-slow-stable+(status:open+OR+status:merged)
09:17:17 <gmann> for rocky it pass.
09:17:57 <gmann> so this job or any job derived from this will not be seen running on stable branches until tempest patch is merged.
09:20:27 <frickler> hmm, do we need this for all stable branches? or would changing for rocky be enough?
09:21:14 <gmann> it should be for all supported stable branch but it depends on job stability. changing from Rocky will be last option we can go with
09:23:51 <gmann> i will debug the failure sometime in next week.
09:25:04 <frickler> a bit related topic: migrating the grenade job to zuulv3
09:25:28 <frickler> andreaf starting things a long time ago, tosky continued a bit, but things are stalled for some time now
09:25:37 <gmann> frickler: yeah.
09:26:03 <frickler> https://review.openstack.org/548936
09:26:15 <frickler> I'll try to find some time to continue with this
09:26:25 <gmann> #link https://review.openstack.org/#/c/548936/
09:26:51 <gmann> frickler: thanks, as per last chat with tosky , he was busy with other stuff.
09:27:22 <frickler> recent trigger to look at this was that mordred noticed that the grenade-py3 job running on sdk actually did test only the released sdk lib
09:27:40 <frickler> and it didn't seem to be easy to change that
09:29:13 <gmann> ohk
09:29:22 <frickler> another thing to note is that keystone now actually started using system-scope for some new functionality. so we added a cloud.yaml stanza that provides the needed credentials https://review.openstack.org/629235
09:29:36 <gmann> you mean to test sdk-released-version -> master
09:30:19 <frickler> gmann: well, not master, but patch-under-test when the job is running in the sdk repo itself
09:31:11 <gmann> yeah
09:31:35 <gmann> but do we do that for any library etc ?
09:32:53 <frickler> I don't know, maybe it isn't useful at all to run grenade for that repo.
09:33:42 <gmann> not yet, it is all service only - https://docs.openstack.org/grenade/latest/plugin-registry.html
09:34:10 <gmann> i agree after having grenade job on zuulv3 it will be easy to do.
09:37:09 <gmann> frickler: for system-scope, this is the series of adding system-scope in tempest also so that we can test it on gate - #link https://review.openstack.org/#/q/topic:system_scope_testing+(status:open+OR+status:merged)
09:37:51 <gmann> there are few pending item to debug/discuss though
09:38:23 <frickler> yeah, I saw these, but most things seemed to fail. I can take a closer look later
09:39:03 <frickler> maybe lbragstad and/or cmurphy would be interested in helping with those, too
09:39:56 <gmann> yeah i am debugging those with lbragstad and we left with few items/scenario to discuss before vacation
09:41:19 <frickler> another issue: dtantsur noticed that elastic-recheck is lacking support for targeting queries against stories instead of lp bugs, maybe someone wants to dig into that https://storyboard.openstack.org/#!/story/2004745
09:46:15 <gmann> frickler: yeah, it is only LP bugs only.
09:52:28 <gmann> frickler: on grenade for sdks, I am thinking whether we need to support LIBS_FROM_GIT from greande so that target devstack branch can checkout the current sdk version of tested change
09:53:31 <gmann> or it should be always the current changes if target devstack branch is master.
09:53:50 <gmann> as tested repo is added to LIBS_FROM_GIT by default in devstack
09:54:26 <frickler> yeah, I've been thinking whether that should be a grenade-tips variant, similar to what osc does
10:00:03 <gmann> ok, I will check current job for sdk with target branch etc
10:00:39 <gmann> that is time up for today office hour, let me close that. thanks for joining .
10:00:39 <frickler> the current job get removed https://review.openstack.org/629503
10:00:44 <gmann> #endmeeting