Tuesday, 2023-10-10

gmannslaweq: ralonsoh: ykarel: do you know any known issue on neutron-linuxbridge-tempest on stable/2023.2 ? it seems it is failing 100% now https://zuul.openstack.org/builds?job_name=neutron-linuxbridge-tempest&branch=stable%2F2023.2&skip=002:39
gmannit is blocking the devstack setup of stable/2023.2 https://review.opendev.org/q/topic:qa-2023-2-release+status:open02:39
ralonsohgmann, yes, it should be solved with https://review.opendev.org/c/openstack/neutron/+/89743806:12
slaweqgmann but You should also know that since some time linuxbridge is marked as "experimental" feature in Neutron and we support it only in best effort manner. We also don't run neutron-tempest-plugin-linuxbridge job in gate anymore (just in experimental and periodic queues)07:03
fricklerso we should just drop it from devstack testing I guess? not sure when and why it was added initially07:18
fricklerseems this goes back to at least the great zuul job refactoring of 2018. /me goes and makes a dropping patch. https://review.opendev.org/c/openstack/devstack/+/60099007:21
opendevreviewDr. Jens Harbott proposed openstack/devstack master: zuul: Drop neutron-linuxbridge-tempest job  https://review.opendev.org/c/openstack/devstack/+/89775907:23
ykarel+107:24
fricklergmann: kopecmartin: ^^ we can backport that to 2023.2 to unblock things07:24
ralonsohthe neutron patch is enough to unblock the gate, just to let you know07:34
fricklerralonsoh: yes, but it neutron doesn't gate linuxbridge any longer, devstack should even less07:51
fricklers/it/if07:51
ralonsohperfect then07:52
opendevreviewMerged openstack/devstack master: zuul: Drop neutron-linuxbridge-tempest job  https://review.opendev.org/c/openstack/devstack/+/89775911:58
opendevreviewDr. Jens Harbott proposed openstack/devstack stable/2023.2: zuul: Drop neutron-linuxbridge-tempest job  https://review.opendev.org/c/openstack/devstack/+/89780412:44
*** haleyb|away is now known as haleyb13:26
opendevreviewDr. Jens Harbott proposed openstack/devstack stable/2023.2: [stable only] Make devstack-platform-rocky-blue-onyx non voting  https://review.opendev.org/c/openstack/devstack/+/89763113:30
opendevreviewDr. Jens Harbott proposed openstack/devstack stable/2023.2: Update branches for stable/2023.2  https://review.opendev.org/c/openstack/devstack/+/89686313:30
opendevreviewDr. Jens Harbott proposed openstack/devstack stable/2023.2: Stop installing Tempest at system wide for stable/2023.2  https://review.opendev.org/c/openstack/devstack/+/89686413:30
opendevreviewDr. Jens Harbott proposed openstack/devstack stable/2023.2: Cap max microversions for stable/2023.2  https://review.opendev.org/c/openstack/devstack/+/89686513:30
opendevreviewDr. Jens Harbott proposed openstack/devstack stable/2023.2: Cap stable/2023.2 network, swift, volume api_extensions for tempest  https://review.opendev.org/c/openstack/devstack/+/89686613:30
yadneshCentos9 telemetry jobs are failing due to " Problem: package gcc-c++-11.4.1-2.1.el9.x86_64 from appstream requires gcc = 11.4.1-2.1.el9, but none of the providers can be installed" https://zuul.opendev.org/t/openstack/build/d2d5e609b70d47ff908c256bc0fbc0b9/log/job-output.txt#3724-372714:38
fricklermy suggestion is to switch to a stable distro like ubuntu or debian. or maybe rockylinux, though they also have had some mirror issues lately14:42
slaweqgmann hi, I wanted to ask You about S-RBAC and service role testing14:52
slaweqwe recently merged https://review.opendev.org/c/openstack/neutron/+/886724 in Neutron so we have policies for service role already. Is there any job already to test that in CI together with other projects?14:53
kopecmartin#startmeeting qa15:00
opendevmeetMeeting started Tue Oct 10 15:00:24 2023 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
frickler\o15:01
kopecmartino/ 15:02
kopecmartin#topic Announcement and Action Item (Optional)15:02
kopecmartinwe're past the release, although there are a few patches still needed to be merged15:02
lpiwowar\o15:02
kopecmartin#link https://review.opendev.org/q/topic:qa-2023-2-release+status:open15:02
kopecmartino/15:02
kopecmartin#topic Bobcat Priority Items progress15:03
kopecmartin#link https://etherpad.opendev.org/p/qa-bobcat-priority15:03
kopecmartin'unit test coverage in Tempest' has been completed 15:03
kopecmartin#link https://review.opendev.org/c/openstack/tempest/+/89308015:04
kopecmartinthe rest will be triaged during the PTG15:04
kopecmartinthat brings us to the next topic15:04
kopecmartin#topic OpenStack Events Updates and Planning15:04
kopecmartinthe next PTG will be held virtually, October 23-27, 202315:04
kopecmartinless than 2 weeks from now15:04
kopecmartinyou can propose topics that we will discuss during PTG here15:05
kopecmartin#link https://etherpad.opendev.org/p/oct2023-ptg-qa15:05
kopecmartini assume everyone is already registered :) 15:05
frickleryou assume wrongly15:05
kopecmartinoh, sorry, i remember now :D 15:05
lpiwowarI think I should ... I'm just double-checking. 15:06
kopecmartinanyway, anyone can join the calls regardless the registration ;) 15:06
kopecmartinyou may also influence dates of QA PTG sessions, just fill this:15:06
kopecmartin#link https://framadate.org/f26R3EcZ2BOo7r8Q15:06
kopecmartinI'll schedule something by the end of next week15:06
kopecmartinthe topic etherpad looks tragic for now, although proposals always appear kind of last minute, so I'm not worrying 15:07
kopecmartin#topic Gate Status Checks15:08
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:08
kopecmartinno patches, anything urgent to review?15:08
fricklerthe devstack series for 2023.215:08
fricklerI should've marked that stack15:08
kopecmartinthese?15:09
kopecmartin#link https://review.opendev.org/q/topic:qa-2023-2-release+status:open15:09
fricklerhttps://review.opendev.org/c/openstack/devstack/+/896866 and below15:09
kopecmartini'm monitoring it 15:09
kopecmartin+115:09
kopecmartinactually i can already leave my vote there15:10
lpiwowarkopecmartin: I have these two open patches: https://review.opendev.org/c/openstack/tempest/+/896011 (tempest), https://review.opendev.org/c/openstack/devstack/+/897402 (devstack)15:10
kopecmartini voted on the first one, the other one is on my list15:11
kopecmartingmann: when you have a sec please ^15:11
frickleroh, devstack was also affected by the Pillow bump https://zuul.opendev.org/t/openstack/build/1f99c77a838b40659f6f85d7f6e2787115:12
fricklerso we need to look at rewriting that (the?) blockdiag(s). but maybe there will be a cross project discussion at the ptg for that, too15:13
kopecmartinoh, good point15:14
kopecmartinmoving on 15:16
kopecmartin#topic Bare rechecks15:16
kopecmartin#link https://etherpad.opendev.org/p/recheck-weekly-summary15:16
kopecmartinall good there15:16
kopecmartin#topic Periodic jobs Status Checks15:16
kopecmartinperiodic stable full15:16
kopecmartin#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-215:16
kopecmartinperiodic stable slow15:16
kopecmartin#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-xena15:16
kopecmartinperiodic extra tests15:16
kopecmartin#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-tests15:16
kopecmartinperiodic master15:16
kopecmartin#link https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic15:16
kopecmartintempest-centos9-stream-fips failed twice , hmm15:17
kopecmartinno, just once15:17
fricklerplain centos too15:18
kopecmartinno module named pip, hopefully random 15:18
fricklersee also the comment just before the meeting15:18
opendevreviewKatarina Strenkova proposed openstack/tempest master: [WIP] Implement purge list in tempest cleanup  https://review.opendev.org/c/openstack/tempest/+/89784715:18
kopecmartinthe one about centos9? yeah .. it doesn't look like it's in our hands 15:19
fricklerIMHO we should stop supporting it, it breaks way too often because of uncoordinated or broken pkg updates15:19
kopecmartinright, that would make sense, let's have a brief PTG topic about that?15:20
* kopecmartin added that to the etherpad15:21
kopecmartin#topic Distros check15:22
kopecmartincs-915:22
kopecmartin#link https://zuul.openstack.org/builds?job_name=tempest-full-centos-9-stream&job_name=devstack-platform-centos-9-stream&skip=015:22
kopecmartindebian15:22
kopecmartin#link https://zuul.openstack.org/builds?job_name=devstack-platform-debian-bullseye&job_name=devstack-platform-debian-bookworm&skip=015:22
kopecmartinrocky15:22
kopecmartin#link https://zuul.openstack.org/builds?job_name=devstack-platform-rocky-blue-onyx15:22
kopecmartinopenEuler15:22
kopecmartin#link https://zuul.openstack.org/builds?job_name=devstack-platform-openEuler-22.03-ovn-source&job_name=devstack-platform-openEuler-22.03-ovs&skip=015:22
kopecmartinjammy15:22
kopecmartin#link https://zuul.opendev.org/t/openstack/builds?job_name=devstack-platform-ubuntu-jammy-ovn-source&job_name=devstack-platform-ubuntu-jammy-ovs&skip=015:22
kopecmartinyep, centos is broken, on master as well as 2023.215:23
kopecmartinrocky is broken on stable/2023.2 too, but there is a fix for that, isn't it?15:24
kopecmartinoh, right15:24
kopecmartin#link https://bugs.launchpad.net/devstack/+bug/203873315:24
kopecmartinthat's why it was familiar, i saw the LP 15:25
kopecmartineuler hasn't been running on master for a month due to the libvirt version incompatibility .. we'll revisit that after the PTG15:26
kopecmartin#link https://bugs.launchpad.net/devstack/+bug/203522415:26
fricklerI wonder why that is passing on 2023.2 though15:27
fricklerah, no, 2023.1 is passing, nvm15:27
kopecmartinthat's about it15:29
kopecmartin#topic Sub Teams highlights15:29
kopecmartinChanges with Review-Priority == +115:29
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:29
kopecmartinno patches15:29
kopecmartin#topic Open Discussion15:29
kopecmartinanything for the open discussion?15:29
lpiwowarNothing from my side15:30
frickleranything on global venv? do we need to punt that to the ptg, too?15:30
kopecmartinnothing new, i gave it a few hours couple weeks back, couldn't figure it out15:31
kopecmartinyeah, we can add it to the ptg list15:31
*** haleyb_ is now known as haleyb15:32
kopecmartin#topic Bug Triage15:34
kopecmartin#link https://etherpad.openstack.org/p/qa-bug-triage-bobcat15:34
kopecmartinwe have 2 bugs in tempest that have fixes looking promising:15:35
kopecmartin#link https://bugs.launchpad.net/tempest/+bug/203880215:35
kopecmartin#link https://bugs.launchpad.net/tempest/+bug/203491315:35
kopecmartinwhen you have a minute gmann, please check 15:35
kopecmartinthat's all from my side15:36
kopecmartinanything else to cover?15:36
lpiwowarkopecmartin: probably no15:36
kopecmartinthank you all then, see you around15:37
kopecmartin#endmeeting15:37
opendevmeetMeeting ended Tue Oct 10 15:37:06 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:37
opendevmeetMinutes:        https://meetings.opendev.org/meetings/qa/2023/qa.2023-10-10-15.00.html15:37
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/qa/2023/qa.2023-10-10-15.00.txt15:37
opendevmeetLog:            https://meetings.opendev.org/meetings/qa/2023/qa.2023-10-10-15.00.log.html15:37
lpiwowarkopecmartin: thanks!15:37
fricklerthx o/15:38
gmannslaweq: ralonsoh frickler thanks for reply for linuxbridge job, +1 on dropping it15:54
gmannkopecmartin: can you review this too https://review.opendev.org/c/openstack/devstack/+/89780415:54
fricklerkopecmartin: and https://review.opendev.org/c/openstack/devstack/+/897631/3 , seems you only went by the topic16:14
dansmithartom: so, on my whitebox cpu state thing17:04
dansmithartom: not sure if you caught up, but I had to change the dedicated cpus to 4-5 instead of 0-1 because cpu0 can't be offlined and nova crashes on start if it tries (filed another bug for that)17:04
dansmithbut now another test is failing that seems cpu-number-specific17:05
dansmithcan you have a look?17:05
artomdansmith, yeah, I didn't look into it too deeply, but it looks pretty systematic, I suspect something's not being cleaned up properly17:05
dansmithI sure hope it doesn't have cpu numbers hard-coded in it17:05
dansmithso you think it's something not cleaned up after my test and not that rearranging the cpus is breaking it?17:05
artomWhat doesn't have CPU numbers hard-coded?17:06
artomNot hardcoded per se, but there's an assumption that both compute hosts come with disjoint cpu_dedicated_set and cpu_shared_set out of the box17:06
dansmiththe test that's failing, I haven't even looked at the test itself17:06
dansmithdisjoint, sure17:06
dansmiththis is the change I made: https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/897579/8/.zuul.yaml17:06
dansmithis it complaining because that overlaps with the other compute?17:07
artomOh, didn't even notice the zuul.yaml change17:08
dansmiththat's why I'm asking, to make sure you saw that I had to change that17:08
artomOK, I think yeah, that broke it - the assumption is that cpu_dedicated_set and cpu_shared_set are all disjoint four-ways17:09
artomSo the cpu_shared_set is different between the two computes17:09
artomAnd cpu_dedicated_set is disjoint between the two computes17:09
artomAnd then cpu_shared_set and cpu_dedicated_set are disjoint from each other17:09
dansmithokay, so, hmm17:10
artomIf you can't offline 0, could you not boot on the node that doesn't have 0 in its dedicated set? There's bound to be 117:10
dansmiththat will mean that my test would fail if it landed on the other compute17:10
artomYou can inspect the host, get its dedicated set, and pick the one that doesn't have CPU 0 in that set17:11
dansmithwell, I kinda think that zero should likely never be in the dedicated set regardless, so I'm not sure that's really a good fix17:11
artomWe could try that as well17:11
dansmithcan we remove zero from both sets on both hosts?17:11
artomI... _think_ so?17:12
artomIf we've done our stuff properly, it should pass CI17:12
artomBut the cardinality of shared and dedicated sets has to remain the same on both hosts (so 3 and 3 and 2 and 2, or whatever)17:12
dansmithwell, if I just remove zero from both sets on both hosts, they should be good/17:13
dansmithoh because one will shrink if I do that17:14
artomWould have to run it through CI, I don't remember off the top of my head17:14
artomBut yeah, one will shrink17:14
opendevreviewDan Smith proposed openstack/whitebox-tempest-plugin master: Test nova's cpu host state management  https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/89757917:15
dansmithso this maybe ?17:16
dansmithto keep them all the same size17:16
artomYep, looks sensible17:17
artomI can't remember if anything depends on there being 4 dedicated CPUs17:17
artomLike, booting 2 VMs with 2 CPUs each or something17:17
dansmithack, we'll see17:17
artomSo it might pass, but we'll need to look at the skipped tests as well17:17
* dansmith nods17:17
artomdansmith, you're finding a whole bunch of problems with how whitebox was coded :)18:44
artom... Thanks? :)18:44
dansmithsorry man18:44
dansmiththey seem legit tho :)18:44
artomYeah, I left comments18:45
artomWe were too coupled to the deployment (which makes sense, tests like that don't have much of a choice), but that coupling was hardcoded, and we should have done it better18:45
dansmithare you saying this because you've looked at the latest failure?18:46
artomYes18:47
dansmithack, will look after my current meeting18:47
artomAck18:47
opendevreviewMerged openstack/devstack stable/2023.2: zuul: Drop neutron-linuxbridge-tempest job  https://review.opendev.org/c/openstack/devstack/+/89780418:54
dansmithartom: okay so you want me to make those changes in this patch, or a separate one, or are you working on that now and I can base this on something?19:01
artomdansmith, I was thinking you'd introduce a new "base" patch under your test19:02
slaweqgmann hi, I'm not sure if You saw my question earlier so I will ask again :)19:02
slaweqwe recently merged https://review.opendev.org/c/openstack/neutron/+/886724 in Neutron so we have policies for service role already. Is there any job already to test that in CI together with other projects?19:02
slaweqI'm now leaving for today but please send me here any info You have (if You have anything) and I will get back to it tomorrow morning19:02
slaweqthx in advance19:02
gmannslaweq: sorry, i read and got distracted while replying19:02
gmannslaweq: sure, I think existing job should validated those but I will check and update you tomorrow. 19:04
dansmithartom: aight19:05
opendevreviewMerged openstack/devstack stable/2023.2: [stable only] Make devstack-platform-rocky-blue-onyx non voting  https://review.opendev.org/c/openstack/devstack/+/89763119:06
gmannfrickler: kopecmartin: base changes on jobs are merged now, can either of you want to approve these https://review.opendev.org/q/topic:qa-2023-2-release+status:open 19:10
kopecmartingmann: sure, done19:11
gmannthanks19:11
opendevreviewDan Smith proposed openstack/whitebox-tempest-plugin master: Test nova's cpu host state management  https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/89757919:14
opendevreviewDan Smith proposed openstack/whitebox-tempest-plugin master: Fix some dedicated CPU assumptions  https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/89786819:14
opendevreviewDan Smith proposed openstack/whitebox-tempest-plugin master: Fix some dedicated CPU assumptions  https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/89786820:11
opendevreviewDan Smith proposed openstack/whitebox-tempest-plugin master: Test nova's cpu host state management  https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/89757920:11
opendevreviewMerged openstack/devstack stable/2023.2: Update branches for stable/2023.2  https://review.opendev.org/c/openstack/devstack/+/89686321:19
dansmithartom: https://7135d89174e90d2f7667-4e27fa9e0f4edf99cfff42f0877124d7.ssl.cf2.rackcdn.com/897868/2/check/whitebox-devstack-multinode/c057a13/testr_results.html21:22
dansmithI guess that's not failing as expected because I lowered the dedicated-per-node,21:23
dansmithbut the number matches the size of the dedicated set on each, so I'm not sure why21:23
dansmithah, it's not getting set properly:21:24
dansmithcompute.cpu_dedicated_set      = 0-321:24
dansmithcompute.cpu_dedicated_set      = 4-721:24
dansmithhrm21:25
dansmith2023-10-10 20:29:37.541 | + inc/meta-config:merge_config_file:164    :   eval 'iniset $NOVA_CONF compute cpu_dedicated_set "0-3"'21:25
dansmithoh, duh21:26
dansmithokay yeah, I need to obviously trim the two sets down in the same patch where I drop that number21:28
dansmiththat's why this all passed on the second one21:28
opendevreviewDan Smith proposed openstack/whitebox-tempest-plugin master: Fix some dedicated CPU assumptions  https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/89786821:28
opendevreviewDan Smith proposed openstack/whitebox-tempest-plugin master: Test nova's cpu host state management  https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/89757921:28

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