16:00:33 #startmeeting nova 16:00:33 Meeting started Tue Feb 20 16:00:33 2024 UTC and is due to finish in 60 minutes. The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:33 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:33 The meeting name has been set to 'nova' 16:00:35 hey folks 16:00:44 #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting 16:00:46 oj 16:00:56 oj too ;) 16:01:16 o/ 16:02:29 awaiting a few more people before we start 16:03:03 o/ 16:03:56 do we want to discuss now ? 16:04:03 o/ 16:04:05 not sure we have a quorum 16:04:26 ok, lemme do a quick meeting then 16:04:31 #topic Bugs (stuck/critical) 16:04:36 #info No Critical bug 16:04:41 #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 66 new untriaged bugs (+7 since the last meeting) 16:04:46 #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster 16:04:51 #info bug baton is bauzas 16:05:00 I'll continue to take the baton 16:05:09 o/ 16:05:20 #topic Gate status 16:05:24 #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs 16:05:24 o/ 16:05:31 #link https://etherpad.opendev.org/p/nova-ci-failures-minimal 16:05:37 #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status 16:05:41 #info Please look at the gate failures and file a bug report with the gate-failure tag. 16:05:44 #info Please look at the gate failures and file a bug report with the gate-failure tag. 16:06:13 all the periodics are green (except again nova-emulation for stable/zed but meh) 16:06:17 we just merged the 8g swap change for nova-lvm which will help 16:06:24 cool to know 16:06:29 been a lot of nova-lvm fails lately 16:06:56 o/ 16:07:18 I also saw (again) some guest kernel issues 16:07:39 (for bfv instances resized) 16:07:47 but... meh 16:07:55 moving on 16:07:57 #topic Release Planning 16:08:01 #link https://releases.openstack.org/caracal/schedule.html#nova 16:08:07 #info Caracal-3 (and feature freeze) milestone in 1 week 16:08:13 yeah, next Thursday 16:08:23 tick-tock again 16:08:31 #topic Review priorities 16:08:35 #link https://etherpad.opendev.org/p/nova-caracal-status 16:08:41 #topic Stable Branches 16:08:47 elodilles: anything you want to discuss ? 16:09:16 #info stable/2023.* gates don't seem blocked (though non-voting grenade-skip-level is broken, probably due to stable -> unmaintained yoga branch) 16:09:30 * for 2023.1 16:09:37 #info stable/zed gate is broken, as nova-grenade-multinode started failing (probably due to stable -> unmaintained yoga branch) 16:09:54 :) 16:10:09 i'm investigating this, but might be easier to set nova-grenade-multinode non-voting for now 16:10:18 I don't have time for looking at it unfortunately 16:10:22 but yeah 16:10:25 until i figure out where to patch the job ;) 16:10:47 so that gate will be unblocked 16:10:51 opinions? 16:12:24 anyway, we can track things here: 16:12:27 #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci 16:13:34 ++ 16:13:54 (i know the timing isn't best: one week before Feature Freeze...) 16:15:47 (and that's all from me) 16:15:49 ok, can we move to the next topic ? 16:15:51 elodilles: is it possibel teh failure is a real upgrade issue 16:15:52 cool 16:16:06 #topic vmwareapi 3rd-party CI efforts Highlights 16:16:10 fwiesel: anything to tell ? 16:16:13 #info Possible solution to bug (https://bugs.launchpad.net/nova/+bug/2053027) proposed. 16:16:33 sean-k-mooney: could be, though i'd give it really low probability o:) 16:16:38 So, after a long time I found the culprit... Now I just have to find an acceptable solution. 16:16:56 #info Regression in the CI setup (FIPs not working outside of routers network namespace). 16:17:16 I hope, I can work that out quickly. 16:17:25 #info Proposed with regression above leaves us with a tempest result of (Passed: 435, Failed: 41, Skipped: 42) 16:17:42 So, still progress. Down from 200-something failures. 16:18:04 ++ 16:18:12 There are also some tests still in, which need to get blacklisted, like the iSCSI attachment tests. But first, FIPs. 16:18:22 Questions? 16:18:27 none from me 16:18:30 anyone else ? 16:18:55 How does it look then with the feature freeze and the vmware driver? 16:19:21 feature freeze is only for blueprints 16:19:35 if you have bugfixes, we can merge them until RC1 16:19:36 Ah great... that gives us a bit more time. 16:20:00 fwiesel: you probably don't know, but at RC1, we git branch from master 16:20:39 so, then after RC1 tag, the master branch is then related to Dalmatian 16:20:58 every change we merge after RC1 is then a Dalmatian one 16:21:44 if we want to fix Caracal before GA, then we need to fix the bug in master (Dalmatian) and then backport it to the Caracal stable branch... but only if this is a regression from that release 16:22:06 And if it is a regression from yoga? :) 16:22:16 I mean xena. 16:22:32 so say you add a fix, we could merge it before or after RC1, but we wouldn't be able to backport it to Caracal and Bobcat only after Caracal GA 16:22:49 (that's just a 2-week time) 16:22:56 (3 weeks actually) 16:22:59 I see. I'll keep that in mind. I don't think we are in that a hurry. 16:23:29 fwiesel: fwiw, you could only backport the fix down to Zed 16:23:50 https://releases.openstack.org/ 16:24:02 Fine by me. We are targeting bobcat as the next release. 16:24:09 (Internally) 16:24:32 elodilles: do you know when eventually all the EM branches will become Umaintained ? 16:24:53 in the coming weeks i'll propose transition branches for them 16:25:08 ok 16:25:25 Well, that's from my side then. 16:25:26 since Yoga became EOM in the past days officially 16:26:15 yeah, it would look bizarre to backport to Zed and then punt Yoga by directly backporting to Xena 16:26:23 (and Zed will transition from May 2nd, 2024) 16:26:49 ok, anyway I think we're done 16:26:58 elodilles: thanks for replying 16:27:02 and thanks fwiesel 16:27:13 #topic Open discussion 16:27:22 nothing in the agenda, anything anyone ? 16:28:03 looks not 16:28:08 thanks all folks 16:28:12 #endmeeting