17:00:16 #startmeeting qa 17:00:16 Meeting started Wed Nov 8 17:00:16 2023 UTC and is due to finish in 60 minutes. The chair is kopecmartin. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:16 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:16 The meeting name has been set to 'qa' 17:00:23 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours 17:01:09 o/ 17:01:23 o/ 17:01:30 #topic Announcement and Action Item (Optional) 17:01:45 we have a new schedule of office hour 17:02:06 it's gonna alternate, odd weeks Wednesdays at 17:00 UTC (like today) 17:02:23 even weeks Tuesdays at 15:00 UTC (practically as before) 17:02:43 the reason is to accommodate multiple time zones 17:02:52 +1 17:03:06 #topic Caracal Priority Items progress 17:03:13 #link https://etherpad.opendev.org/p/qa-caracal-priority 17:03:31 ^^ the priority etherpad for this cycle 17:03:44 all unfinished items from previous etherpad were copied to this one 17:04:42 #topic OpenStack Events Updates and Planning 17:04:50 we had a virtual PTG 2 weeks ago 17:04:56 agenda: 17:04:57 #link https://etherpad.opendev.org/p/oct2023-ptg-qa 17:06:14 a summary was also sent to the ML 17:06:17 #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/WTWU6N77AQS7QHAI6EDD5SHNRNZE4VH6/ 17:07:27 #topic Gate Status Checks 17:07:27 #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) 17:07:37 any urgent reviews? 17:08:24 #topic Sub Teams highlights 17:08:24 Changes with Review-Priority == +1 17:08:24 #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) 17:08:36 one priority patch 17:08:42 already workflowed 17:09:15 let's get to usual, jobs status 17:09:18 #topic Periodic jobs Status Checks 17:09:18 periodic stable full 17:09:18 #link https://zuul.openstack.org/builds?pipeline=periodic-stable&job_name=tempest-full-yoga&job_name=tempest-full-xena&job_name=tempest-full-zed&job_name=tempest-full-2023-1&job_name=tempest-full-2023-2 17:09:20 periodic stable slow 17:09:22 #link https://zuul.openstack.org/builds?job_name=tempest-slow-2023-2&jjob_name=tempest-slow-2023-1&job_name=tempest-slow-zed&job_name=tempest-slow-yoga&job_name=tempest-slow-xena 17:09:24 periodic extra tests 17:09:26 #link https://zuul.openstack.org/builds?job_name=tempest-full-2023-2-extra-tests&job_name=tempest-full-2023-1-extra-tests&job_name=tempest-full-zed-extra-tests&job_name=tempest-full-yoga-extra-tests&job_name=tempest-full-xena-extra-tests 17:09:28 periodic master 17:09:30 #link https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic 17:09:59 I wonder if we need to update these links (i'm copy pasting them from the agenda) 17:10:06 o/ 17:10:11 sorry little late 17:10:31 np, i'm going through the usual 17:12:54 periodic jobs seem fine , well tempest-full-test-account-no-admin-py3 doesn't :/ 17:13:04 lot's of weird errors: 17:13:04 https://577c7db1b7d82ddde14e-e0bdf3ad49ea8c697978dcccacccf379.ssl.cf2.rackcdn.com/periodic/opendev.org/openstack/tempest/master/tempest-full-test-account-no-admin-py3/831b2e8/testr_results.html 17:13:30 Forbidden, Exceeded quota 17:14:21 That looks strange ... I'm taking a look. 17:15:30 some of the failures look similar as in 17:15:33 #link https://bugs.launchpad.net/tempest/+bug/2020860 17:16:18 403 one seems valid one and policy changes to new defaults might have caused them. 17:16:21 do we have bug for that? 17:16:30 maybe cause by this? 17:16:31 rule:create_network is disallowed by policy 17:16:32 #link https://review.opendev.org/c/openstack/tempest/+/899310 17:16:57 no bug apart from the one i shared above (2020860) 17:17:30 ok, can you create one and I will fix sometime this or next week 17:17:58 sure, lpiwowar can you please create a new LP? :D 17:18:05 i'm gonna continue with the meeting :) 17:18:16 :D ok:) 17:18:41 btw, gmann can we consider this LP done? 17:18:44 #link https://bugs.launchpad.net/tempest/+bug/2020860 17:18:56 checking 17:19:03 oh, i've just noticed that the patch has "Related-bug" .. so maybe not 17:19:12 but it's couple of months old .. 17:20:06 kopecmartin: no, we did disable the new defaults but we need to run pre-provisioned testing with new default 17:20:17 this requires more changes in pre provisioned account things 17:20:26 I am keeping this low priority for this cycle 17:20:49 ack 17:20:55 currently pre provisioned job run on old defaults whihc is just a workaround 17:21:41 #topic Distros check 17:21:41 cs-9 17:21:41 #link https://zuul.openstack.org/builds?job_name=tempest-full-centos-9-stream&job_name=devstack-platform-centos-9-stream&skip=0 17:21:43 debian 17:21:45 #link https://zuul.openstack.org/builds?job_name=devstack-platform-debian-bullseye&job_name=devstack-platform-debian-bookworm&skip=0 17:21:47 rocky 17:21:49 #link https://zuul.openstack.org/builds?job_name=devstack-platform-rocky-blue-onyx 17:21:51 openEuler 17:21:53 #link https://zuul.openstack.org/builds?job_name=devstack-platform-openEuler-22.03-ovn-source&job_name=devstack-platform-openEuler-22.03-ovs&skip=0 17:21:55 jammy 17:21:57 #link https://zuul.opendev.org/t/openstack/builds?job_name=devstack-platform-ubuntu-jammy-ovn-source&job_name=devstack-platform-ubuntu-jammy-ovs&skip=0 17:24:00 all seems good 17:24:13 i need to check where we're with openeuler in regards of this libvirt LP 17:24:14 #link https://bugs.launchpad.net/devstack/+bug/2035224 17:26:07 #topic Open Discussion 17:26:12 anything for the open discussion? 17:27:17 Just FYI I'm writing the bug and this one seems to be similar => https://bugs.launchpad.net/tempest/+bug/2020860 . It appeared after NOVA_ENFORCE_SCOPE was changed in devstack. 17:28:02 that's what i thought too 17:28:59 the job was broken even before, maybe it has several issues 17:29:09 ok, can you add those new failing tests also in that bug 17:29:39 otherwise i will forgot those the one failing for 403 17:30:26 gmann: ack, I will add it there 17:30:34 lpiwowar: thanks 17:31:15 i have one question about this patch, also commented there 17:31:16 #link https://review.opendev.org/c/openstack/tempest/+/879923 17:31:49 i think that the point 3 , gmann mentioned in the previous comment, is optional, well it depends on what we wanna achieve 17:32:24 my goal is to limit the cleanup tool by default so that it doesn't delete anything that isn't prefixed with tempest-test - in that case we can omit point 3 17:32:26 however 17:32:54 if we wanna also allow users to customize the prefix, then we need the point 3 obviously 17:33:09 so my question is more like, do we want to allow users to customize the prefix? 17:33:25 kopecmartin: replied 17:33:40 if we do not make it configure then it seems it will have same issue as we have today 17:34:17 configuration make it easy for users to use and detect the tempest created resource eaisly. that can help in our cleanup script or the one if they have any 17:34:41 ok, i just wanted to double check as that will require modification of quite a lot of files .. i didn't wanna commit anyone's time if we were't sure we want that 17:34:51 if we are doing this effort, it is better to make it configurable also 17:35:43 I think if we are fixing that then we should do it fully otherwise sometime later someone will come to make it configurable 17:36:33 kopecmartin: if you think author scope of work or bandwidth is the issue to do this bug change then we can do it in two steps 1. hard coded value with tempest-test 2. make it confiugrable 17:36:49 s/bug change/big change 17:37:16 right, i was thinking the same, the author has already 2 commits anyway, this is the other one 17:37:17 #link https://review.opendev.org/c/openstack/tempest/+/897231 17:37:40 ohk, did not see that 17:38:09 can you ask them to make it in dependent so that it will be easy to review both. config one on top of hardcoded value 17:38:19 yep, absolutely 17:38:36 cool, thanks 17:38:42 I am adding both in my list 17:39:50 thanks 17:39:53 #topic Bug Triage 17:39:53 #link https://etherpad.openstack.org/p/qa-bug-triage-caracal 17:39:57 Link to the bug: 17:40:01 #link https://bugs.launchpad.net/tempest/+bug/2043038 17:40:29 lpiwowar: +1 17:41:16 anyway, the bug numbers are recorded 17:41:27 i don't have any bug to bring up this time 17:41:33 that's all from my side 17:41:35 anything else? 17:42:09 nothing else from my side 17:42:35 ack, see you all around then :) 17:42:39 thanks everyone 17:42:40 nothing from my side 17:42:46 thanks kopecmartin 17:42:47 #endmeeting