15:00:16 #startmeeting qa 15:00:16 Meeting started Tue Apr 2 15:00:16 2024 UTC and is due to finish in 60 minutes. The chair is kopecmartin. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:16 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:16 The meeting name has been set to 'qa' 15:00:21 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours 15:01:40 #topic Announcement and Action Item (Optional) 15:01:58 QA release patches: 15:02:00 #link https://review.opendev.org/q/topic:%22qa-2024-1-release%22 15:02:05 most of them are already merged 15:02:29 #topic OpenStack Events Updates and Planning (Optional) 15:02:49 #link https://etherpad.opendev.org/p/apr2024-ptg-qa 15:03:18 i booked 2 one hour slots, in case there won't be more topics we don't need to use the other slot 15:03:40 Monday and Wednesday 14-15 UTC 15:04:02 info in the etherpad ^^ or in the email sent to the ML 15:04:22 #topic Gate Status Checks 15:04:23 #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:04:23 #topic Sub Teams highlights 15:04:24 Changes with Review-Priority == +1 15:04:26 #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:04:39 no reviews 15:04:47 #topic Periodic jobs Status Checks 15:04:47 periodic stable full 15:04:47 #link https://zuul.openstack.org/builds?pipeline=periodic-stable&job_name=tempest-full-zed&job_name=tempest-full-2023-1&job_name=tempest-full-2023-2 15:04:49 periodic stable slow 15:04:51 #link https://zuul.openstack.org/builds?job_name=tempest-slow-2023-2&job_name=tempest-slow-2023-1&job_name=tempest-slow-zed 15:04:53 periodic extra tests 15:04:55 #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 15:04:57 periodic master 15:04:59 #link https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic 15:05:38 do we have 2024.1 periodic jobs yet? 15:05:58 I think so 15:06:08 oh, i need to edit hte links .. 15:07:03 #link https://zuul.openstack.org/builds?job_name=tempest-full-zed&job_name=tempest-full-2023-1&job_name=tempest-full-2023-2&job_name=tempest-full-2024-1&pipeline=periodic-stable&skip=0 15:07:15 yes, looking green https://zuul.openstack.org/builds?job_name=tempest-full-2024-1&project=openstack/tempest 15:07:19 yeah 15:09:39 agenda edited 15:10:29 yep, all green 15:10:33 moving on then 15:10:35 #topic Distros check 15:10:35 cs-9 15:10:35 #link https://zuul.openstack.org/builds?job_name=tempest-full-centos-9-stream&job_name=devstack-platform-centos-9-stream&skip=0 15:10:37 debian 15:10:39 #link https://zuul.openstack.org/builds?job_name=devstack-platform-debian-bullseye&job_name=devstack-platform-debian-bookworm&skip=0 15:10:41 rocky 15:10:43 #link https://zuul.openstack.org/builds?job_name=devstack-platform-rocky-blue-onyx 15:10:45 openEuler 15:10:47 #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 15:10:49 jammy 15:10:51 #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 15:12:05 seems like devstack-platform-centos-9-stream fails on stable/2024.1 15:13:33 no module named pip 15:14:41 o/ 15:15:07 my first question would be, do we want to run that job on a stable branch or master is enough? 15:16:19 seems like devstack-platform-rocky-blue-onyx has the same issue on stable/2024.1 15:17:52 on the other hand, openeuler fails on master 15:18:42 it gets deployed at least and majority of the tests pass 15:20:32 gmann: frickler thoughts ^ centos / rocky should run only on master or on a stable branch too? 15:21:37 I even wouldn't mind dropping them completely, so don't count on my opinion for that I guess ;) 15:21:37 I think they should be running on stable branch also especially rocky which we are thinking to make it in runtime as more regular testing 15:22:08 centos one I am also not monitoring more so dropping if ok if they are failing and no one fixing them 15:22:47 ok, .. now they fail for the same reason, if one gets fixed, the other one has the same issue too 15:23:10 i'll try to check if there is a simple solution for the 'no pip found' error 15:24:16 if it's not as simple, i'd like to escalate that to someone who knows more about rocky distribution 15:24:42 btw, who should be the point of contact for rocky issues? assuming there is someone if the plan is to use it more 15:25:41 NeilHanlon has been doing some rocky things, but isn't around here, not sure if interested in devstack, too 15:26:12 ack, thanks 15:26:16 i've suggested he join here 15:26:22 jrosser: thanks 15:26:43 he's been extremely helpful for us in openstack-ansible regarding all things rocky 15:27:12 amazing 15:27:59 if that doesn't work out, asking some kolla people might also be an option 15:29:31 great, thanks 15:29:39 NeilHanlon: welcome :) 15:29:43 o/ hiya :) 15:29:48 what'd I break this time ;) 15:30:03 nothing, probably :D 15:30:17 we're having issues with rocky on stable/2024.1 due to 'no module named pip' 15:30:31 #link https://9821a3f9f0b1702a953f-5d9007d54f55ca0ff60ac5193693c3de.ssl.cf1.rackcdn.com/periodic-weekly/opendev.org/openstack/devstack/stable/2024.1/devstack-platform-rocky-blue-onyx/de1b47c/job-output.txt 15:30:42 with python3.9 15:31:52 and this is in devstack, yes? 15:31:59 I think the real error is: Error: Unable to find a match: liberasurecode-devel 15:32:01 scrolling up, the issue will be something else that results in not installing pip 15:32:05 NeilHanlon: yes 15:32:14 yep good catch frickler 15:32:31 hm 15:32:47 failing early on dnf failures would also be a good tasks to do 15:34:06 thinking out loud here: I wonder if we can support the swift project in producing wheels for pyeclib that can bundle up those deps and make it easier for CI jobs to run (and theoretically to deploy in general). I think timburke was looking at what was needed to use manylinux to build wheels at one point wonder where that ended up 15:34:16 okay... i don't think liberasurecode is part of Rocky or RHEL, actually. It's in RDO. 15:35:14 amoralej may know more, looks like it should be coming from Stream mirrors. https://cbs.centos.org/koji/buildinfo?buildID=34707 15:36:23 that's seems to be almost 3 years old 15:36:47 seems to still be pushed here: https://mirror.stream.centos.org/SIGs/9-stream/cloud/x86_64/openstack-zed/Packages/l/ 15:39:45 anyway, let's move on so that we can close the meeting 15:39:52 #topic Open Discussion 15:39:52 anything for the open discussion? 15:41:01 that's it then .. see you next week at PTG 15:41:21 o/ 15:41:22 #endmeeting