16:00:43 #startmeeting nova 16:00:44 Meeting started Tue Feb 14 16:00:43 2023 UTC and is due to finish in 60 minutes. The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:44 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:44 The meeting name has been set to 'nova' 16:00:47 howdy 16:00:58 what a crazy week 16:01:03 #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting 16:01:32 who's around ? 16:01:48 o/ 16:01:55 . 16:02:20 o/ 16:02:24 .. 16:03:11 I can start a monolog, and people can join meanwhile 16:03:16 o/ 16:03:24 #topic Bugs (stuck/critical) 16:03:30 #info No Critical bug 16:03:30 * gibi here for the monologs 16:03:36 #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 17 new untriaged bugs (-11 since the last meeting) 16:03:43 great numbers 16:05:10 artom: thanks for that 16:05:18 oh wao 16:05:23 kudos artom 16:05:36 * bauzas was checking who was the owner last week :) 16:06:02 next in the roster is Uggla but he's on PTO till next week 16:06:30 and next in the queue is sean (I'll avoid to highlight him, he needs rest :) ) 16:06:44 so, I can try to triage a few bugs this week 16:07:03 I mean, this isn't like I'm already doing a shit ton of bugs checks 16:07:38 #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster 16:07:51 #info bug baton is being passed to bauzas this week 16:07:52 bauzas: thansk 16:08:07 #topic Gate status 16:08:11 #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs 16:08:15 #link https://etherpad.opendev.org/p/nova-ci-failures 16:08:26 that was (and that still is) an hectic week 16:08:43 tl;dr: our gate was blocked but we eventually merged the fix 16:09:19 but now we continue to have a ton of CI false positives with vif plugged events missed and other funs 16:09:40 I must to admit I beg people to share my pain 16:10:17 I do share your pain 16:10:21 for some degree 16:10:21 Kashyap Chamarthy proposed openstack/nova stable/train: libvirt: At start-up rework compareCPU() usage with a workaround https://review.opendev.org/c/openstack/nova/+/873722 16:10:25 anything now to raise except complaining that you do lots of rechecks ? 16:10:37 one thing 16:11:11 please be aware that upper constraints bumps cannot be merged at the moment due to failures 16:11:16 oh that 16:11:20 forgot to mention 16:11:21 so even though we released os-traits 2.10 16:11:26 we cannot use that yet in placement and nova 16:11:47 yeah, tbc, that's not only the nova master gate which is broken broken (c) elodilles 16:12:07 the requirements project do has its own pain, and tempest too 16:12:09 yeah as far as I see every u-c bump is blocked 16:12:15 correct 16:12:29 we discussed that in #openstack-requirements earlier today 16:12:35 there is a fix in the air 16:12:37 but, 16:12:42 it seems virtualenv release came just in time 16:12:43 there is another open issue 16:13:02 elodilles: yeah, that's lovely, a perfect Murphy timing 16:13:36 bauzas: could have been worse -> more closer to release date :) 16:13:47 not sure it changes anything tho 16:14:03 but let's jump to the next topic 16:14:11 fwiw, looking at https://etherpad.opendev.org/p/recheck-weekly-summary 16:14:32 I can still see around 18% of rechecks that are bare rechecks 16:14:39 this is desesperating 16:14:56 I mean, we know we have CI failures 16:15:15 but if you just call 'recheck' without further info, you basically piss off your problems 16:15:46 and you make looking that you don't care about the CI, then why should we care about your own patches then ? 16:15:55 nova is on 13.5% that is an improvement from the last 90 days (18.5%) 16:16:22 I'd like to be optimistic 16:16:30 I know that debugging a CI failure is tricky 16:16:56 but if you don't make the effort to try looking, then basically that means you don't care 16:17:17 * bauzas is grumpy today, sorry 16:17:25 #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status 16:17:29 all greens 16:17:36 #info Please look at the gate failures and file a bug report with the gate-failure tag. 16:17:42 (that's a wish) 16:17:49 #info STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures 16:17:54 (that's a formal ask) 16:18:15 next topic for the fun ? 16:18:23 one thing about CI 16:18:27 sure 16:19:00 maybe we should make an dedicated effort next cycle to fix up CI first before we jump on adding new features 16:19:19 maybe, asking people with feature proposals to take a gate bug first 16:19:20 gibi: that's litterally already in the PTG agenda :) 16:19:25 bauzas++ 16:19:42 well, I was less harsh 16:19:56 but I opened a bullet point about CI failures and I had some ideas 16:20:09 I wrote some email yesterday 16:20:26 if people want recognition, I offer them a Great Way to Be Recognized 16:20:35 cool 16:21:24 moving on then (fwiw, I like your idea to somehow ask people to show some dedication to upstream while they propose) 16:21:31 gibi: Fixed the thing in the above train backport too: https://review.opendev.org/c/openstack/nova/+/873722 16:21:35 this is actually a great jump to the next topic 16:21:36 (Err, sorry; there's a meeting going on) 16:21:41 kashyap: in a meeting 16:21:47 Yep, yep; saw that 16:21:55 moving on 16:22:00 #topic Release Planning 16:22:07 #link https://releases.openstack.org/antelope/schedule.html 16:22:10 #info Antelope-3 is in 2 days 16:22:26 #info FeatureFreeze is in 2 days 16:22:36 #link https://etherpad.opendev.org/p/nova-antelope-blueprint-status Blueprint status for 2023.1 16:22:44 here, I'm also a bit grumpy 16:23:04 we approved a couple of blueprints but despite this, a very few of them are actually reviewable 16:23:34 the os-bricks issue prevents one to correctly get reviewed, but alas, the series is even not fully complete 16:23:58 os-traits, not os-brick my bad 16:24:17 so, yeah, back to gibi's proposal, I think we may be harsher next cycle 16:24:32 don't forget this was a shorter cycle 16:24:35 and ask people to show some evidence of work 16:24:42 gibi: that's a valid point 16:24:46 I'm maybe overreacting 16:24:55 it is always emotional before FF 16:24:58 next cycle will be longer :) 16:25:12 28 weeks 16:25:22 compared to 24, correct ? 16:25:25 yepp 16:25:42 well, we'll see then 16:25:43 imageine how much recheck we could do in an extra month :D 16:25:44 Merged openstack/nova master: Add logging to find test cases leaking libvirt threads https://review.opendev.org/c/openstack/nova/+/872975 16:25:48 gibi: :D 16:25:52 oh wow ^ 16:26:07 \o/ 16:26:14 bauzas: now I need not to forget to check for that logs 16:26:16 in the coming days 16:26:20 gibi: (off-meeting, I'll write a revert patch ;) ) 16:26:26 bauzas: good point 16:26:26 yup 16:26:41 anyway, back to the release 16:26:56 I think we made good progress on reviews 16:27:09 if we missed something or some patch, feel free to amend the etherpad please 16:27:13 or comment it out 16:27:33 I did a bit of research and digging but I think I found all the open changes 16:28:12 moving on then, unless someone caring about an accepted blueprint makes to take the opportunity to raise a concern ? 16:28:17 yeah please cry out loudly if your series has a chance to land in the next two day and you lack reviews 16:29:24 ++ 16:30:03 ok, let's jump to the next one 16:30:06 #topic vPTG Planning 16:30:09 will be short 16:30:12 just a reminder 16:30:16 #link https://www.eventbrite.com/e/project-teams-gathering-march-2023-tickets-483971570997 Register your free ticket 16:30:21 #link https://etherpad.opendev.org/p/nova-bobcat-ptg Draft PTG etherpad 16:30:37 feel free to add the items you wanna discuss in ^ 16:30:45 #topic Review priorities 16:30:50 #link https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement+OR+project:openstack/os-traits+OR+project:openstack/os-resource-classes+OR+project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/osc-placement)+(label:Review-Priority%252B1+OR+label:Review-Priority%252B2) 16:30:58 I'll be honest, I lost my attention 16:31:18 but I'll try to look at those once we cut m-3 16:31:32 #info As a reminder, cores eager to review changes can +1 to indicate their interest, +2 for committing to the review 16:31:37 #topic Stable Branches 16:31:54 elodilles: showcase. 16:31:59 ~o~ 16:32:02 #info ussuri and train gates are fixed (ensure-rust role was added to grenade and tempest jobs) 16:32:17 #info stable/victoria gate is blocked (failing openstacksdk-functional-devstack job needs to be removed: https://review.opendev.org/c/openstack/nova/+/873295 similarly as in wallaby) 16:32:27 #info rest of the stable branches seem to be OK 16:32:32 or at least unblocked 16:32:45 #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci 16:32:59 i think that is all i can tell now 16:34:04 cool 16:34:18 I just rechecked the CVE fix for the ussuri branch 16:34:23 should land hopefully 16:34:32 fingers crossed 16:34:56 bauzas: do we have CVE fix for stable/train? 16:35:01 or we punted on that? 16:35:10 due to oslo 16:35:12 gibi: as I said last week, I loudly said no to it 16:35:16 OK 16:35:21 if someone wants to propose it, fair 16:35:23 thanks for the refrsh 16:35:37 but yeah, due to the oslo.utils dep, that's not gonna be a fun conversation 16:35:53 and most distros now include the fix in their own products 16:36:13 that's it. 16:36:40 thanks 16:36:53 #topic Open discussion 16:36:59 anything anyone ? 16:37:04 the agenda is empty 16:38:03 I assume that if there are no loud cries for review on the week of FF then we are done a good job :) 16:38:25 So I have a weird thing 16:38:30 https://opendev.org/openstack/nova/src/branch/master/nova/image/glance.py#L392 16:38:34 Count the length of that line 16:39:00 * bauzas calls len() 16:39:14 (We could also end the meeting and chat about that in "normal" IRC) 16:40:13 83? 16:40:13 artom: sure, that's a good point 16:40:17 I have 82 16:40:21 1116 16:40:32 Yep. So... what's our pep8 job doing? 16:40:40 but AFAIR, we only enforce line lengths on code 16:40:55 that has to be doublechecked 16:41:03 anyway 16:41:15 let's wrap it now and chase this question outside of the meeting 16:41:17 thanks all 16:41:22 #endmeeting