15:00:20 #startmeeting qa 15:00:20 Meeting started Tue Nov 16 15:00:20 2021 UTC and is due to finish in 60 minutes. The chair is kopecmartin. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:20 The meeting name has been set to 'qa' 15:00:27 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours 15:00:33 the link to the agenda ^^^ 15:01:05 o/ 15:02:12 let's start 15:02:15 #topic Announcement and Action Item (Optional) 15:02:29 nothing from my side here 15:02:57 #topic Yoga Priority Items progress 15:03:00 hello 15:03:02 #link https://etherpad.opendev.org/p/qa-yoga-priority 15:03:09 any updates regarding the priority items? 15:03:43 on RBAC thing, as you might know we are having weekly call on RBAC new design things and we are in good shape for things to do in Yoga 15:04:03 and on tempest and devstack side how to test/setup, it will be more easy now 15:04:37 I am going to start looking into open reviews this week and then migrate devstack's nova lib to new one 15:04:50 that sounds amazing! 15:05:49 i've started with some reviews regarding FIPS 15:05:51 for FIPS things, we discussed the proposed goal in TC meeting last week 15:06:27 and there were concern on making it default, but goal proposal is in discussion so may be we can wait for the direction in goal first? #link https://review.opendev.org/c/openstack/governance/+/816587 15:06:38 I have not looked into the current patches yet 15:07:14 like we can make openstack FIPS compatible but not testing as default or so.. 15:07:35 I think that decision is important for QA to proceed on this. 15:08:07 i see, that makes sense, changes like these take some time, i'd say that for now it's important to have it enabled in some jobs (not as default) to test compatibility 15:08:34 making it default can be discussed at the next PTG and it would be something for future cycles, not for this one 15:09:19 yeah, having in one job and we need to make sure it is compatible for non-FIPs also. like no change in existing things/testing/interface/code|requirement-compatible etc 15:09:56 I mean we should not add changes which make it incompatible for existing distro/requirements etc 15:10:09 at least until goal direction is finalized in TC 15:10:32 of course 15:11:02 also all the current changes are in early stages, most of them are WIP ones still figuring out things 15:11:34 +1 15:12:06 and having a tempest/devstack job with that enable or so will be good example to show in goal also. 15:12:29 good, i think we're on the same page 15:12:32 yeah, i agree 15:13:59 moving on 15:14:02 #topic OpenStack Events Updates and Planning 15:14:09 nothing here 15:14:09 +1 15:14:15 #topic Gate Status Checks 15:14:21 #link https://review.opendev.org/q/label:Review-Priority%253D%252B2+status:open+(project:openstack/tempest+OR+project:openstack/patrole+OR+project:openstack/devstack+OR+project:openstack/grenade+OR+project:openstack/hacking) 15:14:23 Alfredo Moralejo proposed openstack/devstack master: [WIP] Support CentOS Stream 9 https://review.opendev.org/c/openstack/devstack/+/800903 15:14:28 I don't see any urgent patches 15:14:34 any issues to bring up? 15:15:01 I have not seen any blocker 15:15:05 yet :) 15:15:34 me neither 15:15:43 classic :) 15:15:47 #topic Periodic jobs Status Checks 15:15:55 #link https://zuul.openstack.org/builds?job_name=tempest-full-xena-py3&job_name=tempest-full-wallaby-py3&job_name=tempest-full-victoria-py3&job_name=tempest-full-ussuri-py3&job_name=tempest-full-train-py3&pipeline=periodic-stable 15:16:00 #link https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic 15:16:04 all green \o/ 15:16:12 nice 15:16:23 #topic Sub Teams highlights 15:16:28 any updates, highlights we need to discuss today ? 15:16:40 Changes with Review-Priority == +1 15:16:40 #link https://review.opendev.org/q/label:Review-Priority%253D%252B1+status:open+(project:openstack/tempest+OR+project:openstack/patrole+OR+project:openstack/devstack+OR+project:openstack/grenade+OR+project:openstack/hacking) 15:16:56 no changes there with priority set 15:17:31 nothing from me specifically other than we already discussed on RBAC and FIPs 15:17:49 https://review.opendev.org/c/openstack/devstack/+/780417 could do with some attention 15:18:04 frickler: sure, will check after meeting 15:18:12 it's the basis for some of lbragstad's rbac stuff 15:19:15 frickler: did we check no plugins are replying on those env variable? 15:19:44 gmann: I had some patches to clean things up, yes 15:20:29 https://review.opendev.org/c/openstack/devstack/+/780033 I also didn't review myself because I amended it 15:20:46 ok 15:20:55 this should be the last remaining cleanup https://review.opendev.org/c/openstack/glance_store/+/817344 15:21:09 sure, I will check those rbac bits which is in my list 15:22:41 frickler: thanks for the review 15:22:58 i'll check them too, later today/tomorrow 15:23:29 #topic Open Discussion 15:23:48 (gmann) Turning off the openstack-health service and so does retirement of it? 15:24:01 I agree with retiring, we don't have resources to fix and maintain that , TripleO CI team is working on TripleO Health which should provide similar functionality 15:24:22 oh, similar functionality ? 15:24:49 then we can fix this itself with TripleO team collaborating in this repo ? 15:25:49 it's not up yet i think, let me check with them, i'm not sure how they have done it .. 15:25:52 how is this related to what dpawlik is doing with https://review.opendev.org/c/openstack/ci-log-processing/+/815604 ? 15:26:57 I mean with that whole project, not just the single patch 15:27:08 frickler: dpawlik work on bringing opensearch on our logging. openstack-health dashboard is broken and not maintained now. I hardly see people using it now a days 15:27:30 openstack-health dashboard was additional dashbaord for checking tests stability then e-r 15:28:00 but it was working on the same logging data, wasn't it? 15:28:01 I used to be useful in initial time but later one it did not receive much attention. 15:28:17 yeah, from subunitsql 15:28:34 and only for check queue 15:29:36 as per current plan and dpawlik bandwidth, o-h dashboard is not in that plan and it is upto QA team if we want to maintain it or ask more help like from TripleO team as they are doing same kind of thing? 15:29:53 if nothing work then shut it down. 15:30:20 +1 to shutdown 15:30:25 .. i've found it, i believe this is the wip page - http://health.sbarnea.com/openstack-health/#/ - looks exactly like openstack-health 15:31:08 let me check with the tripleo ci team on how they are planning to build the o-h like service 15:31:10 kopecmartin: this seems fork of existing o-h ? 15:31:22 it looks like that 15:31:24 :/ 15:32:03 yeah of they are interested then we can discuss if they can collaborate otherwise my vote also to shutdown 15:32:32 good, let me bring this up again next week ,meanwhile i'll check more details 15:32:35 I will start the ML thread and ask if tripleO or other team can help 15:32:40 +1 15:32:44 +1, thanks 15:32:47 let's keep it in agenda until then 15:32:56 yeah .. anything else for open discussion 15:32:57 ? 15:33:10 nothing from my side 15:33:41 #topic Bug Triage 15:33:43 #link https://etherpad.opendev.org/p/qa-bug-triage-yoga 15:33:51 numbers are recorded as always 15:34:10 i've reviewed and merged some patches addressing a few bugs today 15:34:28 apart from that i haven't had time to do more detailed triaging 15:34:33 i'll try this week 15:35:00 that's all from my side 15:35:12 if there isn't anything else from anyone, let's close this office hour 15:35:19 yeah, thanks kopecmartin 15:35:26 (after 35 minutes :D) 15:35:34 just one more thing 15:35:43 sure 15:35:57 I started digging through the open devstack patches 15:36:21 oldest first, closing some, asking for feedback on others 15:36:45 but decided to keep it manually for now, because I found some few that actually still were interesting 15:37:07 interesting, that's good news 15:37:41 frickler: thanks for triaging the reviews 15:37:46 +1 15:37:51 I hope once I'm done we can run some automatic cleanup with more confidence 15:38:41 frickler: feel free to set priority flags to fast forward the review process if needed 15:39:27 kopecmartin: yeah, I'm pretty hesitant to do that most of the time ... because what is really important? 15:39:33 but I can keep that in mind 15:40:14 :) 15:40:34 and that's it from me 15:40:53 thank you 15:41:09 that's it then for today, thank you all, see you around 15:41:13 #endmeeting