16:01:09 <bauzas> #startmeeting nova
16:01:09 <opendevmeet> Meeting started Tue Mar 12 16:01:09 2024 UTC and is due to finish in 60 minutes.  The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:09 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:09 <opendevmeet> The meeting name has been set to 'nova'
16:01:12 <elodilles> o/
16:01:13 <bauzas> hey folks
16:01:16 <dansmith> o/
16:01:17 <bauzas> #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
16:01:28 <fwiesel> o/
16:02:13 <auniyal> o/
16:02:22 <gibi> o/
16:02:39 <bauzas> okay, let's start
16:03:00 <bauzas> #topic Bugs (stuck/critical)
16:03:06 <bauzas> #info Two Critical bugs
16:03:11 <bauzas> #link https://bugs.launchpad.net/nova/+bug/2052915
16:03:15 <bauzas> #link https://bugs.launchpad.net/nova/+bug/2056613
16:03:45 <bauzas> for the first one, AFAIK, we no longer have a problem
16:03:52 <bauzas> so we could close it
16:04:13 <bauzas> elodilles: ^
16:04:54 <elodilles> well nova-grenade-multinode is not failing
16:05:21 <elodilles> but that's not neutron-ovs-grenade-*
16:06:05 <bauzas> are we running those jobs in Nova ? I don't find so
16:06:15 <elodilles> so if nova was linked due to nova-grenade-multinode then we can close
16:06:24 <elodilles> otherwise we don't even run those jobs
16:06:32 <bauzas> OK, I'll close this for nova
16:06:37 <elodilles> +1
16:07:54 <bauzas> okay, next one https://bugs.launchpad.net/nova/+bug/2056613
16:08:41 <bauzas> that one is not really a Critical bug
16:09:13 <bauzas> if it's because we want to make sure we can merge the changes before rc1, we'll discuss this later in the meeting
16:09:43 <bauzas> so I'll move that bug to High and we'll add that bug report to the new rc etherpad I just created
16:09:59 <gibi> If we merge it for rc1 regardless of the priorityh then Im OK to drop the priority
16:10:59 <bauzas> in general, Critical priority for bugs are for either gate failures or if the issue is related to some API that everyone uses, say an user
16:11:13 <bauzas> for example, some bug with the create API
16:11:38 <bauzas> so moving it down to High and adding it to the etherpad
16:13:00 <bauzas> #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 65 new untriaged bugs (-10 since the last meeting)
16:13:13 <bauzas> I did a bit of triage for some
16:14:02 <bauzas> gibi: would you be okay to triage some bugs for next week ?
16:14:26 <gibi> I don't feel the power sorryj
16:14:44 <Uggla> o/
16:14:54 <gibi> but you can ping me with specific questions
16:15:38 <bauzas> okay, then I'll continue to use the baton for next week
16:15:50 <bauzas> #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
16:15:57 <bauzas> #info bug baton is bauzas
16:16:13 <bauzas> #topic Gate status
16:16:17 <bauzas> #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:16:22 <bauzas> #link https://etherpad.opendev.org/p/nova-ci-failures-minimal
16:16:29 <bauzas> #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status
16:16:36 <bauzas> #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:16:45 <bauzas> all periodics are green
16:16:57 <bauzas> anything people want to discuss about gate failures ?
16:16:59 <sean-k-mooney> cool including the ironic one
16:17:36 <sean-k-mooney> yep https://zuul.openstack.org/build/429f833ce05748d0a840d0c8ac18b726
16:17:49 <bauzas> yup I was about to reply
16:18:32 <bauzas> anything else to talk about CI ?
16:19:19 <bauzas> looks not, moving on then
16:19:26 <bauzas> #topic Release Planning
16:19:30 <bauzas> some important notes
16:19:36 <bauzas> #link https://releases.openstack.org/caracal/schedule.html#nova
16:19:41 <bauzas> #info RC1 planned this week
16:20:03 <bauzas> and then, the magic etherpad I just created :
16:20:09 <bauzas> #link https://etherpad.opendev.org/p/nova-caracal-rc-potential
16:20:31 <bauzas> as you can see, there is a long list of TODOs against patches we need to merge before RC1
16:20:53 <bauzas> that's my duty, I'll ensure either we already have them or I'll create them
16:21:03 <dansmith> um,
16:21:11 <bauzas> and then I'll ping some folks to make sure we can merge them before RC1
16:21:14 <dansmith> not just patches to review, but patches to *write* yeah?
16:21:30 <dansmith> unless I'm looking at the wrong "long list" :)
16:21:35 <bauzas> dansmith: yup, but if they don't exist, I'll create them tonight
16:21:43 <dansmith> okay
16:21:56 <bauzas> TODOs are mostly "I don't know if takashi created them yet"
16:22:08 <bauzas> if we want to be honest :D
16:22:38 <bauzas> those are quite simple to do, we have some pattern for every of them
16:22:58 <bauzas> so, yeah, cores, please understand that if I ping you for RC1 changes, those are a bit important
16:23:14 <bauzas> about one
16:23:23 <bauzas> #link https://review.opendev.org/c/openstack/releases/+/912480 Cycle highlights
16:23:37 <gibi> feel free to ping
16:23:38 <bauzas> cores and others, feel free to review that patch today if you can
16:24:05 <bauzas> that's the cycle highlights, I'll copy them to the prelude as soon as we merge the highlights
16:24:35 <elodilles> bauzas: i can approve it, unless you want to fix the nits
16:24:43 <bauzas> elodilles: I'll do the nits
16:24:47 <elodilles> +1
16:24:54 <elodilles> then i'll wait :]
16:24:58 <bauzas> it's quite a marketing document
16:25:23 <elodilles> indeed
16:25:54 <bauzas> that's why I'd appreciate if sean-k-mooney, dansmith, auniyal and a few others could review the highlights
16:26:15 <dansmith> yep, but it would help if you'd fix the nits so we can review the actual version proposed
16:26:27 <bauzas> cool, then I'll do it in a couple of seconds
16:26:43 <bauzas> moving
16:26:44 <sean-k-mooney> ack i can try an take a look today
16:26:51 <bauzas> #topic Review priorities
16:27:00 <bauzas> #link https://etherpad.opendev.org/p/nova-caracal-status
16:27:08 <bauzas> I'll add a link to the rc etherpad in the status etherpadf
16:27:22 <bauzas> but I think we're pretty done with that etherpad for now
16:27:48 <bauzas> I'll create another dalmatian status etherpad as soon as we branch RC1
16:28:35 <bauzas> if people are a bit confused by the difference between etherpads and what to look, as a reminder, the rc etherpad is prioritary until RC1
16:29:35 <bauzas> after RC1, we'll have a dalmatian status etherpad for tracking bugs and blueprints we approve for D, while we'll continue to have a RC etherpad for tracking Caracal RC2 and later (if we need so)
16:29:51 * gibi left two nits in the highlightsj
16:30:07 <bauzas> don't hesitate to bug me on IRC if you are lost in translation
16:30:23 <bauzas> gibi: thanks, will rebase then
16:30:23 <Uggla> fyi I have updated https://review.opendev.org/c/openstack/nova/+/877773/9, I think sean-k-mooney will review it, it will be great to have another core looking at it.
16:31:12 <bauzas> Uggla: I just added it in the rc etherpad https://etherpad.opendev.org/p/nova-caracal-rc-potential#L29*
16:31:18 <Uggla> I understand it is also required to fix another bug with power mgmt.
16:31:21 <bauzas> moving on
16:31:31 <Uggla> bauzas, thx
16:31:44 <bauzas> #topic Stable Branches
16:31:47 <bauzas> elodilles: your time now
16:31:59 <elodilles> ACK
16:32:07 <elodilles> #info stable gates seem to be OK
16:32:15 <elodilles> #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci
16:32:26 <bauzas> \o/
16:32:40 <elodilles> and maybe these two more sentence:
16:32:42 <elodilles> #info stable/yoga, stable/xena, stable/wallaby, stable/victoria branches are now replaced by unmaintained/yoga, unmaintained/xena, unmaintained/wallaby, unmaintained/victoria
16:32:47 <elodilles> #info patches proposed on stable/yoga..victoria branches now abandoned, cherry pick them to unmaintained/yoga..victoria if you want to work on them
16:33:11 <elodilles> that's all
16:33:33 <auniyal> elodilles stable/2023.1 nova-ceph-multistore failed few times for me
16:33:57 <bauzas> auniyal: like master
16:33:59 <bauzas> elodilles: thanks
16:34:13 <elodilles> auniyal: oh, good to know. afair it sometimes fails, but not constantly
16:34:23 <auniyal> bauzas stable/2023.1 - antelope branch
16:34:34 <elodilles> but i'll keep an eye on it
16:35:03 <auniyal> ack, just want to inform
16:35:08 <elodilles> +1
16:35:08 <bauzas> auniyal: I meant I know that nova-ceph-multistore also fails on master
16:35:09 <elodilles> thx
16:35:16 <auniyal> oh okay
16:35:22 <bauzas> anyway, cool thanks guys
16:35:39 <bauzas> #topic vmwareapi 3rd-party CI efforts Highlights
16:35:43 <bauzas> fwiesel: floor is yours
16:35:48 <fwiesel> #info Onboarding two colleagues to take over operations of the CI, as soon as it is "productive"
16:35:55 <bauzas> ++
16:36:15 <fwiesel> Which is hopefully rather sooner than later, still trying to find out why the FIPS are unreliable.
16:36:22 <fwiesel> #info Tested automated commenting on https://review.opendev.org/c/opendev/ci-sandbox/+/901942
16:36:49 <fwiesel> So, in principle, the CI should be able to comment on the change requests.
16:36:55 <fwiesel> #info Enabled commenting also on openstack/nova just before the meeting. With some luck, it works.
16:37:12 <fwiesel> If that works, we will now in roughly 25minutes.
16:37:39 <fwiesel> That's it from my side. Any questions?
16:37:47 <bauzas> not from me, thanks
16:38:11 <fwiesel> bauzas: Then back to you.
16:38:15 <bauzas> ack
16:38:29 <bauzas> I'll be short
16:38:31 <bauzas> #topic Open discussion
16:38:38 <bauzas> (nothing in the agenda)
16:38:41 <bauzas> anything anyone ?
16:39:19 <bauzas> okay, then I'll give you back 20 mins
16:39:22 <bauzas> thanks all
16:39:25 <bauzas> #endmeeting