15:00:18 #startmeeting qa 15:00:18 Meeting started Tue Jun 28 15:00:18 2022 UTC and is due to finish in 60 minutes. The chair is kopecmartin. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:18 The meeting name has been set to 'qa' 15:00:25 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Weekly_QA_Team_meeting 15:00:33 the agenda for today ^^ 15:00:56 hi o/ 15:01:41 o/ 15:04:02 hello 15:04:17 hi 15:04:30 let's start 15:04:37 #topic Announcement and Action Item (Optional) 15:04:53 I'd like to cut an intermediate release for Tempest 15:05:03 to include latest bug fixes related to the sshable issues 15:05:19 #link https://review.opendev.org/c/openstack/tempest/+/847849 15:05:39 I'm waiting for one other patch to get merged first,then we'll proceed with the release ^^ 15:06:09 #topic Zed Priority Items progress 15:06:15 #link https://etherpad.opendev.org/p/qa-zed-priority 15:06:18 any updates on this front? 15:06:30 kopecmartin, nope 15:06:55 I started experimenting with enforce scope in tempest 15:06:56 #link https://review.opendev.org/c/openstack/tempest/+/847760 15:07:40 we have a few failures there, we probably need to tweak the roles used in tempest.conf 15:07:42 still in progress 15:08:45 moving on 15:08:46 #topic Gate Status Checks 15:08:52 #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) 15:09:11 one review there, already +w 15:09:32 any other urgent patches to review? 15:09:55 Nothing from my side kopecmartin 15:10:16 ack 15:10:25 Bare Recheck tracking: 15:10:35 #link https://etherpad.opendev.org/p/recheck-weekly-summary 15:10:45 seems like QA is doing 68.42 % of recheck as bare recheck which is not good. 15:11:11 yeah, this is from TC side we discuss per project bare recheck 15:11:14 so please, be careful and avoid bare rechecks - 'recheck' .. including me 15:11:20 i know i made a few :D 15:11:29 bare recheck means we should not juts to recheck without checking and debugging the failure 15:11:50 there is another document explaining about how to do debug and recheck 15:12:02 I added it in meeting wiki page also 15:12:06 #info STOP DOING BARE RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures 15:12:43 very helpful 15:13:04 i recommend going through that resource 15:13:39 gmann: thanks for the reminder 15:13:49 +1 and let's keep this item for very week meeting for reminder and monitoring 15:14:02 sure 15:14:51 gmann, kopecmartin, can i help here? 15:15:10 if any, let me know 15:15:10 you mean on the recheck front? 15:15:29 yeah 15:15:53 sure, just anytime before typing 'recheck' you and everyone should try debug first and decide whether it's worth rechecking or whether we know why we're rechecking 15:16:10 yeah, sure 15:16:53 i must admit it's a nice habbit as it also helps keep track of the current issues/failures across CI 15:17:31 #topic Periodic jobs Status Checks 15:17:39 stable 15:17:39 #link #link https://zuul.openstack.org/builds?job_name=tempest-full-yoga&job_name=tempest-full-xena&job_name=tempest-full-wallaby-py3&job_name=tempest-full-victoria-py3&job_name=tempest-full-ussuri-py3&pipeline=periodic-stable 15:17:47 master 15:17:47 #link https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic 15:19:28 seems all good there 15:19:54 #topic Distros check 15:20:02 cs-9 15:20:02 #link https://zuul.openstack.org/builds?job_name=tempest-full-centos-9-stream&job_name=tempest-full-py3-centos-8-stream&job_name=devstack-platform-centos-8-stream&job_name=devstack-platform-centos-9-stream&skip=0 15:20:08 fedora 15:20:08 #link https://zuul.openstack.org/builds?job_name=devstack-platform-fedora-latest&skip=0 15:20:15 debian 15:20:16 #link https://zuul.openstack.org/builds?job_name=devstack-platform-debian-bullseye&skip=0 15:20:24 jammy 15:20:24 #link https://zuul.openstack.org/builds?job_name=devstack-platform-ubuntu-jammy&job_name=devstack-platform-ubuntu-jammy-ovn-source&job_name=devstack-platform-ubuntu-jammy-ovs&skip=0 15:22:59 cs-9 constantly failing 15:23:02 still due to 15:23:05 #link https://bugs.launchpad.net/neutron/+bug/1979047 15:23:41 the other distros seem to be passing, that's great 15:23:45 sad they don't seem to have any urgency in fixing this 15:24:14 gmann: do we want debian or / and fedora be voting - check / periodic / other pipeline? 15:25:00 frickler: yeah, i haven't checked what exactly is wrong and whether it's moving anywhere, but it's true it's been failing for some time now 15:25:00 I think debian should be voting 15:25:08 and fedora in periodic is ok 15:25:17 +1 for debian 15:25:45 seems pretty stable with the switch to ovn 15:26:24 agree 15:26:31 AI make debian job voting 15:26:50 another one 15:27:03 AI find time and create rocky job 15:27:40 #topic Sub Teams highlights 15:27:44 Changes with Review-Priority == +1 15:27:50 #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) 15:28:14 no changes there 15:28:18 #link https://review.opendev.org/c/openstack/tempest/+/847330 15:28:23 gmann: is this ok now? ^^ 15:28:40 if yes, then after it's in the gate we can start with the release 15:28:43 #link https://review.opendev.org/c/openstack/tempest/+/847849 15:29:11 kopecmartin: sure, will check after meeting 15:29:25 thanks 15:29:40 #topic Open Discussion 15:29:44 anything for the open discussion? 15:30:36 i have one enforce scope related 15:30:55 i deployed an env with devstack using ENFORCE_SCOPE var 15:31:11 however, i'm failing to execute f.e. 'openstack endpoint list' command 15:31:19 i'm getting unauthorized error 15:31:44 i tried both users devstack provides in the openrc and still the same error 15:31:55 any pointers on how to handle this? 15:32:05 i guess i need a different role, but i'm not sure which one 15:32:06 I think you may need to use cloud users? 15:32:36 OS_CLOUD=devstack-system did you try that? 15:32:54 one sec 15:33:15 devstack-system-admin really 15:33:24 or -reader, -member 15:34:05 hm, cloud devstack-system not found 15:34:34 i would check what roles my user has, but i can't , i feel locked out :D 15:35:36 or i would create a user , i can't , interesting 15:36:30 devstack-system-admin is the cloud name 15:37:19 but I didn't try with enforce yet 15:37:23 yup, still getting 'You are not authorized to perform the requested action: identity:list_endpoints. (HTTP 403) (Request-ID: req-bdc87305-7c3e-4e56-b17b-24737d9feefe)' 15:38:02 oh, good, so it's not just me (maybe) 15:38:37 seems like we'll (on devstack's side) need to at least modify doc , or generate a new user(s) etc 15:39:49 anyway, that's all from my side 15:40:27 #topic Bug Triage 15:40:39 #link https://etherpad.openstack.org/p/qa-bug-triage-zed 15:40:46 I cleaned up a bit of the devstack backlog 15:40:48 the numbers were recorded as always 15:40:58 frickler: i've noticed, thank you! 15:41:10 you lowered the numbers quite a lot 15:41:33 revisited some bugs I triaged years ago 15:42:10 perfect 15:43:31 if there is nothing else , i think we're at the end of the today's office hour 15:43:55 thank you everyone 15:43:56 #endmeeting