Tuesday, 2024-12-10

opendevreviewTim Burke proposed openstack/tempest master: Stop sending underscores in header names to Swift  https://review.opendev.org/c/openstack/tempest/+/93741600:44
*** mhen_ is now known as mhen03:02
*** ralonsoh_ is now known as ralonsoh09:21
opendevreviewLiron Kuchlani proposed openstack/tempest master: Add support for specifying fixed IP address in floating IP association  https://review.opendev.org/c/openstack/tempest/+/93740613:15
opendevreviewLiron Kuchlani proposed openstack/tempest master: Add support for specifying fixed IP address in floating IP association  https://review.opendev.org/c/openstack/tempest/+/93740614:04
kopecmartin#startmeeting qa15:00
opendevmeetMeeting started Tue Dec 10 15:00:34 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
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
opendevmeetThe meeting name has been set to 'qa'15:00
kopecmartin#link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours15:00
kopecmartinagenda ^15:00
fricklero/15:00
kopecmartin\o15:02
gmanno/15:02
opendevreviewNathan proposed openstack/tempest master: Fixed encryption type methods to comply with documentation  https://review.opendev.org/c/openstack/tempest/+/93552615:02
kopecmartinhey gmann isn't it too early for you? 15:02
lpiwowaro/15:03
gmannkopecmartin: I am attending board meeting today so can join here too :)15:03
kopecmartin:) 15:03
kopecmartin#topic Announcements and Action Items15:03
kopecmartinthis is the last office hour before the holidays which means the last office hour this year 15:04
nperezo/15:04
kopecmartinas I mentioned last time, i won't be able to host these in the new year, so we'll need a new volunteer :) 15:04
kopecmartinhi nperez15:04
kopecmartinone of the discussed options was that gmann would take over, however, in that case we'd shift the meeting for a later time to better accomodate his time zone 15:05
kopecmartinif that happens, it'll be shared on the ML as well 15:05
kopecmartinoh, one other update, i've got a volunteer for reviews (as my capacity for this kind of thing in the new year will be decreased)15:07
kopecmartintosky volunteered that he would like to help with reviews on tempest side15:08
kopecmartinyou may have seen his commits to cinder-tempest-plugin and a few related projects, e.g. cinder, glance and even tempest 15:08
toskyeven though I don't know a lot of the internal bits, so I may not always be perfectly helpful15:09
tosky(I do have some experience on devstack and grenade, though, to be refreshed a bit)15:09
kopecmartinthat is absolutely ok .. i'm sure tempest can benefit from that 15:10
fricklercool, yes, I remember you were around when I started digging into devstack15:10
gmannperfect thanks tosky 15:10
kopecmartinluigi is everywhere ;) 15:10
kopecmartinhttps://review.opendev.org/q/from:ltoscano@redhat.com15:10
kopecmartin#action so, one action item for me is to hand over the hosting of this office hour and find (if needed) a new time 15:12
kopecmartinthat's all from announcements 15:13
kopecmartin#topic Epoxy Priority Items progress15:13
kopecmartin#link https://etherpad.opendev.org/p/qa-epoxy-priority15:13
* kopecmartin checking if there are any updates 15:13
* kopecmartin feeling a bit ashamed as he didn't get to a few action items there :/ 15:14
kopecmartinthe migration to noble went more or less fine15:15
kopecmartinthe email thread:15:15
kopecmartin#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/JOMDY26TCW7OX3NXRGOYQCIDXNNJ4E25/15:15
fricklerwell still some cleanup happening, but nothing major that I'm aware of, yes15:15
gmannone of the bug is in devstack-plugin-container CRI-O installation on noble failing15:15
kopecmartinonly 24 patches left open out of almost a hundred15:16
kopecmartin#link https://review.opendev.org/q/topic:%22migrate-to-noble%22+status:open15:16
gmannI pinged hongbin who is mainly maintaining this plugin and he will look into that15:16
kopecmartingreat 15:16
gmannyeah, I am trying to get those merged but they may take time15:16
gmannCRI-O thing only impact k8s jobs15:17
gmannand the doc job migration is still left15:18
kopecmartinack , thanks15:18
kopecmartinlet's move on 15:19
kopecmartin#topic Gate Status Checks15:19
kopecmartin#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:19
kopecmartin2 patches, both approved 15:19
kopecmartin#topic Sub Teams highlights15:19
kopecmartinChanges with Review-Priority == +115:19
kopecmartin#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:19
kopecmartin6 patches, most of them approved15:20
kopecmartini need a second opinion on 15:20
kopecmartin#link https://review.opendev.org/c/openstack/tempest/+/93330815:20
kopecmartinand 15:20
kopecmartin#link https://review.opendev.org/c/openstack/tempest/+/93552615:20
nperezhey you wanted me to fix the "closes bug" part of my commit message and fixed it15:21
kopecmartinperfect, thank you15:21
nperezhttps://review.opendev.org/c/openstack/tempest/+/93552615:21
nperezthank you for reviewing it 15:21
kopecmartinthank you for working on it 15:22
kopecmartini reviewed it, let's see what the automatic jobs think 15:23
kopecmartin#topic Periodic jobs Status Checks15:23
kopecmartinPeriodic stable full: https://zuul.openstack.org/builds?pipeline=periodic-stable&job_name=tempest-full-2023-1&job_name=tempest-full-2023-2&job_name=tempest-full-2024-1&job_name=tempest-full-2024-2 15:23
kopecmartinPeriodic stable slow: https://zuul.openstack.org/builds?job_name=tempest-slow-2024-2&job_name=tempest-slow-2024-1&job_name=tempest-slow-2023-2&job_name=tempest-slow-2023-1 15:23
kopecmartinPeriodic extra tests: https://zuul.openstack.org/builds?job_name=tempest-full-2024-2-extra-tests&job_name=tempest-full-2024-1-extra-tests&job_name=tempest-full-2023-2-extra-tests&job_name=tempest-full-2023-1-extra-tests 15:23
kopecmartinPeriodic master: https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic15:23
frickleryou can drop 2023.1 from those searches now15:24
fricklerthat moved to unmaintained15:24
kopecmartinoh, right, thanks frickler15:24
kopecmartinall builds looks pretty standard 15:26
kopecmartin#topic Distros check15:27
kopecmartinCentos 9: https://zuul.openstack.org/builds?job_name=tempest-full-centos-9-stream&job_name=devstack-platform-centos-9-stream&skip=015:27
kopecmartinDebian: https://zuul.openstack.org/builds?job_name=devstack-platform-debian-bookworm&skip=0 15:27
kopecmartinRocky: https://zuul.openstack.org/builds?job_name=devstack-platform-rocky-blue-onyx15:27
kopecmartinJammy: https://zuul.opendev.org/t/openstack/builds?job_name=devstack-platform-ubuntu-jammy-ovn-source&job_name=devstack-platform-ubuntu-jammy-ovs&skip=015:27
kopecmartinNoble: https://zuul.opendev.org/t/openstack/builds?job_name=devstack-platform-ubuntu-noble&skip=0 15:27
fricklerthe latter two also need updates now I think. more noble less jammy15:27
kopecmartinoh, right15:29
kopecmartinhmm, the search filters based on the name only15:29
kopecmartin.. on the other hand, it might be good to see the results on the unmaintained branch 15:30
kopecmartinhmm, but if there is something wrong, we can't fix that anyway 15:30
kopecmartinI'll try to limit the search 15:30
frickleryes, but devstack-platform-ubuntu-jammy-ovn-source was replaced by devstack-platform-ubuntu-noble-ovn-source for example on master15:30
kopecmartinright .. ok, another action item then 15:31
fricklerand devstack-platform-ubuntu-noble is replaced by tempest-full-py3 ;)15:31
kopecmartin#action kopecmartin to update the above searches15:31
fricklerinstead there is devstack-platform-ubuntu-jammy now. or so I think15:32
frickleranyway, we can go on I think15:33
kopecmartinack15:33
kopecmartin#topic Open Discussion15:33
kopecmartinanything for the open discussion?15:33
clarkbI wanted to call out https://bugs.launchpad.net/devstack/+bug/2082617 and less the specific issue and more the thing that made it difficult to debug15:34
clarkbas noted in there I think the |default(omit) default module arguments may mask early detection of failures to render the config dicts15:34
clarkbit would probably be a good idea for the qa team to investigate refactoring that in devstack so that we're less likely to pass a null default and wonder why the job isn't working as expected15:35
clarkbThe good news is I don't think jobs would pass if they have broken jinja in their localrc config so I don't think we have a bunch of jobs doing the wrong thing15:36
clarkbbut debugging is difficult as is15:36
kopecmartinthat's a good point 15:37
fricklerah, yes, that was a fancy issue. I just think the "qa team" is essentially near zero by now, so not sure who would take that up. except tosky maybe? :)15:38
kopecmartini'll check it15:39
clarkbya its an easy one to fix at a superficial level. Just update that CEPH ip address to the private ipv4 address and move on. My concern is more that debugging future issues may be more painful/ less obvious15:39
clarkband I suspect changing how defaults are handled may expose the issue more directly with a "jinja broke" error15:40
kopecmartinright, that;s a good idea 15:41
kopecmartincool, anything else/15:42
kopecmartin?15:42
kopecmartinok then, we're done 15:43
kopecmartinthank you all 15:43
kopecmartinsee you around15:43
fricklero/15:44
kopecmartin#endmeeting15:44
opendevmeetMeeting ended Tue Dec 10 15:44:04 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:44
opendevmeetMinutes:        https://meetings.opendev.org/meetings/qa/2024/qa.2024-12-10-15.00.html15:44
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/qa/2024/qa.2024-12-10-15.00.txt15:44
opendevmeetLog:            https://meetings.opendev.org/meetings/qa/2024/qa.2024-12-10-15.00.log.html15:44
opendevreviewEmilien Macchi proposed openstack/devstack master: ovn_agent: start OVS processes with retries  https://review.opendev.org/c/openstack/devstack/+/93746215:58
opendevreviewMerged openstack/devstack stable/2023.2: [stable-only] Drop Neutron grenade jobs in the CI  https://review.opendev.org/c/openstack/devstack/+/93612616:21
fricklerkopecmartin: gmann: ^^ forgot I wanted to discuss how to disable grenade jobs with unmaintained branches as base. or do we just ignore that?16:38
opendevreviewMerged openstack/devstack stable/2024.2: Install setuptools 'core' extra  https://review.opendev.org/c/openstack/devstack/+/93720317:08
opendevreviewMerged openstack/devstack master: lib/placement: Migrate placement to WSGI module path  https://review.opendev.org/c/openstack/devstack/+/91958117:08
elodillesnote that the jobs should work now. i know that we don't need to support the grenade jobs from an unmaintained branch, but let's not drop the definition globally, rather let the teams decide if they want to throw them away (or delete them when it is blocking their stable gates). this is maybe useful especially for 2023.1 Antelope, which is now unmaintained, but was the 1st official base for Skip 17:09
elodillesLevel Upgrade.17:09
opendevreviewMerged openstack/devstack master: lib/cinder: Migrate cinder to WSGI module path  https://review.opendev.org/c/openstack/devstack/+/90290517:19
gmannfrickler: elodilles yeah, as long as they work it is fine to run  but if broken then I will suggest to drop unless unmaintained maintainers fix it and keep green. Since starting, we said upgrade testing guarantee is only on supported stable branches only.17:45
elodillesgmann: +117:49
fricklergmann: well the problem is that as long as the defition is made in the global template, projects cannot opt out except by dropping the integrated-gate project-template completely17:59
gmannfrickler: I see, I think we should keep/maintained global template for unmaintained branches somewhere else. otherwise we need to maintained unmaintained templates in tempest and then release a new tempest tag to be used for unmaintained one (which we do but do not separate out the template for unmaitained)18:02
gmannfrickler: or easy way is to stop using the global template in unmaintained and run jobs explicitly when they need to do18:02
gmannour requirement for unmaintained branches is to run at least one integrated testing job18:03
gmannI really want to avoid injecting the new things for unmaintained in QA tooling and we end up being responsible for those. 18:04
fricklergmann: well this isn't about unmaintained branches directly, it is about grenade forced to run on 2023.2 and 2024.1, upgrading from unmaintained/2023.118:14
frickler(grenade-skip-level for the latter branch)18:15
opendevreviewMerged openstack/tempest master: For test VM validation resource were added.  https://review.opendev.org/c/openstack/tempest/+/93330818:32
gmannfrickler: ohk, so this one basically https://github.com/openstack/tempest/blob/master/zuul.d/integrated-gate.yaml#L63318:44
gmannI will say, let it be there as long as it is green and if fail then we can stop running it on oldest supported stable branch. same way we did for EM18:46
*** atmark_ is now known as atmark19:37
opendevreviewTim Burke proposed openstack/tempest master: Stop sending underscores in header names to Swift  https://review.opendev.org/c/openstack/tempest/+/93741621:51
opendevreviewJames Parker proposed openstack/whitebox-tempest-plugin master: Test live migration after attach/detach port  https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/93748722:05
JayFI think https://review.opendev.org/c/openstack/devstack/+/934909 is a positive change -- given we don't actually ensure virtualenv package is installed, and the module is generally preferred now22:43
JayFplease review when you have time22:43
clarkblooks like GLOBAL_VENV does use the venv module and not virtualenv22:52
clarkbso it helps align those two features. That said I wonder if we need the two different virtualenv setups? JayF out of curiousity do you have a specific use case for using venv per project?22:53
JayFI have a patch for ironic fixing USE_VENV, which I was going to try and use to go down a rabbithole of trying to make Ironic's BMC-emulators not need to be global-requirements compatible (by getting Ironic, and them, in their own independent venvs)22:54
JayFbut at this point, realistically, it's there, and it should work or be removed22:54
JayFmaking it work is 100x less work than getting confidence it's unused22:54
clarkbsure. I only ask beacuse its been there for liek 10 years and I'm pretty sure it hasn't ever worked until you made it work :)22:54
JayFheh22:55
clarkbbut also the use case of installing python things that don't use openstack requirements is a reasonable one22:55
JayFI have had a habit the last few months of running full speed into ancient brick walls, this wouldn't be the first time :D 22:55
clarkbthough specifically it was the functionality of running every service in its own venv that didn't work iirc. The underlying code tomanage various venvs probably was fine22:57
clarkbI looked into that when osc was slow because reducing the number of pacakges that osc saw would speed up entrypoint loading22:58
JayFthe code is fine /if `virtualenv` exists on the path/ :D 23:12
JayFwhich my change fixes23:12

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!