15:00:55 #startmeeting qa 15:00:55 Meeting started Tue Dec 7 15:00:55 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:55 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:55 The meeting name has been set to 'qa' 15:01:03 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Weekly_QA_Team_meeting 15:01:07 agenda ^^^ 15:01:17 o/ 15:01:18 hi o/ 15:01:41 o/ 15:02:10 hi all o/ 15:02:12 let's start 15:02:18 #topic Announcement and Action Item (Optional) 15:02:35 nothing from my side here 15:02:45 #topic Yoga Priority Items progress 15:02:51 #link https://etherpad.opendev.org/p/qa-yoga-priority 15:02:56 any updates on this front? 15:03:41 not much from me 15:04:05 me neither 15:04:42 regarding FIPS , there is the patch for supporting ecdsa keys 15:04:44 #link https://review.opendev.org/c/openstack/tempest/+/807465 15:05:02 i see it has got updated , i need to revisit that 15:05:43 seems like most of gmann's comments were addressed, I'll revisit it after the meeting 15:06:56 moving o 15:06:57 on 15:06:59 #topic OpenStack Events Updates and Planning 15:07:03 nothing here yet 15:07:07 #topic Gate Status Checks 15:07:13 #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:07:28 no changes with priority == +2 15:07:36 #topic Periodic jobs Status Checks 15:07:42 #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:07:47 #link https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic 15:09:21 i see 2 failures in ussuri and victoria jobs , however, seem random 15:09:43 2 timeouts 15:10:08 #topic Sub Teams highlights 15:10:13 Changes with Review-Priority == +1 15:10:18 #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:10:27 no changes 15:10:31 anything to bring up? 15:11:16 Nothing on my part 15:12:40 #topic Open Discussion 15:12:53 (gmann) Turning off the openstack-health service and so does retirement of it? 15:13:12 (kopecmartin) 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:13:51 so, we need to retire openstack-health as we know it, because it's been out of date for more than 6 months already and we don't have resources to fix it 15:14:09 we got reply now to have discussion on collaboration 15:14:16 from TripleO CI team, 15:14:17 tripleo ci team is working on their health app (to me it provides very similar functionality as openstack-health) for their jobs 15:14:21 gmann: yes 15:14:56 and that is branched from openstack-health repo 15:15:12 so it means they are user of it? 15:15:19 and I think we can come up with a solution which will allow our jobs publish data to that application 15:15:25 gmann: that's a good question 15:15:31 yeah 15:15:31 i'm not absolutely sure 15:15:40 we could discuss that during the call 15:15:50 anyways we need to discuss on that with them and get more clarity 15:15:53 yeah 15:16:22 also I don't understand whether they will reuse openstack-health UI 15:16:24 may be you can invite them in next meeting. I will reply to email also to have discussion in next meeting 15:16:49 i can, sure 15:16:50 if it is branched or forked then they are using it. that is my understanding currently 15:17:09 i think we should have a call, if it fits everyone's schedule of course 15:17:44 you mean separate call or in QA meeting? 15:18:06 yes 15:18:26 i think it would be more efficient to talk rather than write 15:18:37 but let's see, if can find a time slot 15:18:39 sure. 15:19:31 i like that we may have revive openstack-health (to a certain point) because it turned out it was very good for checking a test stability 15:20:10 right now, if we have a test marked as unstable (if it fails it won't fail the whole job) we don't have a way to see it's passing rate 15:20:15 *its 15:20:58 yeah, that is true. we are in position of retiring it due to maintainers and infra hosting not due to it is not useful 15:21:20 exactly 15:21:26 good 15:21:34 anything else for Open Discussion? 15:21:52 anyways let's get more clarity in call with TripleO team and see 15:24:10 #topic Bug Triage 15:24:15 #link https://etherpad.opendev.org/p/qa-bug-triage-yoga 15:24:21 bug numbers are recorded at ^ 15:24:39 I don't have a specific bug to bring up this week 15:25:25 so if there isn't anything else , let's wrap it up 15:26:05 oh, maybe this 15:26:07 #link https://review.opendev.org/c/openstack/tempest/+/733066 15:26:14 it's related to 15:26:14 #link https://bugs.launchpad.net/tempest/+bug/1881863 15:26:53 ah, this is open in my tab but I did get chancw 15:26:53 i see there was a good discussion about the proposed solution 15:27:02 I will try to do it by this week 15:27:37 gmann: thank you 15:27:50 I think main things was to know reason why we did not do that in resource setup in first place. 15:28:19 I will try to check/recall the history of it I think that was Tokyo summit :) 15:28:31 do not even remember when it was 15:28:49 but I will check and reply/fix something this week for sure 15:29:33 uff 15:29:41 good, thank you 15:29:53 ok, that's it then 15:30:09 thank you all, see you around 15:30:12 nothing else from me too 15:30:15 thanks kopecmartin 15:30:30 #endmeeting