16:00:02 <bauzas> #startmeeting nova
16:00:02 <opendevmeet> Meeting started Tue Sep  5 16:00:02 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:02 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:02 <opendevmeet> The meeting name has been set to 'nova'
16:00:07 <bauzas> welcome folks
16:00:08 <gibi> o/
16:00:11 <sean-k-mooney> o/
16:00:11 <Uggla> o/
16:00:14 <elodilles> o/
16:00:15 <auniyal> o/
16:00:15 <bauzas> #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
16:00:36 <dansmith> o/
16:00:47 <bauzas> cool, people arriving fast, lovin'
16:00:50 <bauzas> let's start
16:00:57 <bauzas> #topic Bugs (stuck/critical)
16:01:02 <bauzas> #info No Critical bug
16:01:06 <bauzas> whoops
16:01:08 <bauzas> #info No Critical bug
16:01:14 <bauzas> #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 49 new untriaged bugs (+0 since the last meeting)
16:01:18 <bauzas> #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
16:01:23 <bauzas> #info bug baton is bauzas
16:01:34 <auniyal> bauzas, I have few bugs to discuss
16:01:36 <bauzas> auniyal: any questions you have ?
16:01:40 <bauzas> cool, shoot
16:02:01 <auniyal> actully this : https://etherpad.opendev.org/p/nova-bug-triage-20230902
16:02:21 <bauzas> ack, looking
16:02:27 <auniyal> https://bugs.launchpad.net/nova/+bug/2031635:
16:02:42 <auniyal> ack
16:03:50 <bauzas> I'm not expert, I can't tell
16:04:20 <auniyal> I'll paste the quick ones here
16:04:29 <auniyal> https://bugs.launchpad.net/nova/+bug/2033393: Xena:  server name is not updated in guest xml after rename ?
16:04:42 <gmann> o/
16:04:53 <gibi> so for 2031635 we need to check if https://review.opendev.org/c/openstack/nova/+/867788 is backported to stables or not
16:05:01 <auniyal> is it known ? does it does affect an operation
16:05:35 <bauzas> let's not discuss the resolution here
16:05:49 <auniyal> gibi, its not backported
16:06:00 <gibi> auniyal: then I guess we need to backport it
16:06:05 <gibi> as we need to support py3.8
16:06:13 <auniyal> ack,
16:06:16 <bauzas> ok, resolution set, Valid then
16:06:24 <bauzas> we can look at the other ones next week
16:07:01 <dansmith> auniyal: the instance name one is invalid, I just updated
16:07:32 <auniyal> ack, thanks dansmith
16:07:48 <bauzas> ok, let's move on then
16:08:42 <bauzas> #topic Gate status
16:08:47 <bauzas> #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:08:59 <bauzas> #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status
16:09:04 <bauzas> #info nova-emulation is still b0rked
16:09:09 <bauzas> chateaulav: are you around ?
16:09:23 <sean-k-mooney> oh really
16:09:27 <sean-k-mooney> i was not aware of that
16:09:44 <sean-k-mooney> whats broken
16:10:13 <sean-k-mooney> test_resize_volume_backed_server_confirm
16:10:20 <sean-k-mooney> so that might not be related to emulation
16:10:24 <sean-k-mooney> the other tests passed
16:10:28 <dansmith> yeah not sure why that would be emulation related
16:10:31 <dansmith> other than that it can be slow
16:11:09 <sean-k-mooney> ill quickly take a look async
16:11:27 <bauzas> yeah probably unrelated, but alas this is the only one which fails every week
16:11:37 <sean-k-mooney> no obvious error in the nova log
16:11:44 <gmann> and a few of the fixes are merged related to this test but yes it can fail on slow maybe
16:12:50 <bauzas> okay, so we'll see if next round it fails again
16:13:11 <bauzas> any other gate information to share ?
16:14:25 <dansmith> otherwise I think the gate is doing better than it has in a while
16:14:37 <dansmith> we still need volume test attention like we have for many years
16:14:45 <dansmith> but life isn't as terrible as it has been
16:15:20 <bauzas> glad to hear such good news
16:15:45 <bauzas> which weren't arriving just because of luck
16:15:58 <bauzas> so kudos to those who worked hard on chasing
16:16:21 <bauzas> moving on then
16:16:23 <bauzas> #topic Release Planning
16:16:28 <bauzas> #link https://releases.openstack.org/bobcat/schedule.html
16:16:32 <bauzas> #info Nova deadlines are set in the above schedule
16:16:47 <bauzas> #link https://etherpad.opendev.org/p/nova-bobcat-blueprint-status Etherpad for tracking blueprints status
16:16:51 <bauzas> #info 9 blueprints were implemented this cycle, 8 got deferred (5 of them were awaiting rebases from owner)
16:17:04 <bauzas> thanks folks who reviewed features
16:17:23 <sean-k-mooney> just on last thing on nova-emulation. we didn not pin that job to < 6 concurancy so maybe we need to drop that back to 4
16:17:33 <bauzas> despite a very few of happy reviewers, we were able to merge a quite decent number of reviews
16:17:50 <bauzas> s/reviews/changes
16:17:52 <gmann> sean-k-mooney: but is it oom issue happening there?
16:18:08 <sean-k-mooney> i dont think so ill look after the meeting
16:18:26 <sean-k-mooney> i just assume since this is testing qemu with emulation of arm it might be slower
16:18:54 <sean-k-mooney> anyway we can go back to the release topic
16:19:05 <gmann> ack
16:19:14 <bauzas> sean-k-mooney: thanks
16:19:23 <bauzas> so, I was just saying thanks
16:20:03 <bauzas> we still have a couple of series that missed the target, but most of them were mostly due to merge conflicts or other states that aren't "shit, we missed to review that"
16:20:29 <sean-k-mooney> there was one that kind fo fell in that camp
16:20:33 <bauzas> we still have two long series that require proper attention next cycle if they're reproposed, as those series are very long and hard to review
16:20:36 <sean-k-mooney> the virtio-packed ring format
16:21:11 <bauzas> it was in merge conflict until last week
16:21:25 <bauzas> actually, until today
16:21:36 <sean-k-mooney> no it ws mergable a mount ago
16:21:36 <bauzas> so no, it was still on the camp "the owner has to do things"
16:21:43 <sean-k-mooney> and then went int merge conflcit in between
16:21:47 <bauzas> sure
16:22:10 <sean-k-mooney> i had tought we merged it
16:22:11 <bauzas> but I raised a couple of times the fact that we are requiring a correct state of a patch for being reviewed
16:22:25 <sean-k-mooney> it was kasyaps min version bump that caused the merge conflict
16:22:31 <bauzas> and it was correctly tracked in the etherpad as being 'in merge conflict'
16:22:52 <bauzas> sean-k-mooney: I bet no, since it was on merge conflict *before* we merged the min version bump
16:23:13 <bauzas> but I can doublecheck the timings based on the etherpad history
16:23:13 <sean-k-mooney> anyway im sad that missed but  it is what it is
16:23:27 <dansmith> yeah I think it was in merge conflict before
16:23:40 <bauzas> again, that one was correctly tracked and marked as not reviewable yet
16:23:59 <sean-k-mooney> i had put review priorty +2 on it for what its worth
16:24:16 <sean-k-mooney> i think part of the miss there may have been pto related
16:24:22 <bauzas> so, I 'm against granting an exception for it (and even not considering the object version change, which is kinda huge to consider)
16:24:37 <sean-k-mooney> im not asking for one
16:25:00 <sean-k-mooney> but i i had realised it was not merged last week i would he pinned them to update it
16:25:18 <bauzas> we're providing weekly meeting updates for such concerns
16:25:31 <bauzas> I can't just ping every single owner to ask him or her to update
16:25:47 <bauzas> it was tracked, an action was awaited
16:26:36 <bauzas> anyway, like I said a couple of hours before, a reproposal is surely acceptable for 2024.1 and can be reviewed in 2 weeks, once master becomes Caracal
16:26:51 <sean-k-mooney> yep
16:27:21 <sean-k-mooney> we also shoudl have landed https://review.opendev.org/c/openstack/nova/+/860829 by the way
16:28:00 <sean-k-mooney> that is needed for the swithc to sqlalchme 2
16:28:05 <bauzas> this isn't a feature, and according isn't impacted by FF
16:28:17 <bauzas> so it can be reviewed now until RC1
16:28:18 <dansmith> it's also not release critical for 2023.2 AFAIK
16:28:32 <bauzas> and which gives me the right opportunity to jump to the next item
16:28:43 <bauzas> #info 1 week before RC1
16:28:49 <bauzas> #link https://etherpad.opendev.org/p/nova-bobcat-rc-potential Etherpad for tracking RCs
16:29:24 <bauzas> if people would enjoy clicking on such link (exactly like they hopefully did for the feature tracking etherpad just before),
16:29:51 <bauzas> they'll see that there are a couple of paperwork-ish but important changes to deliver before RC1
16:30:17 <bauzas> mostly for upgrade concerns (rpc aliases and object version tagging)
16:30:48 <bauzas> in that etherpad, people are fancy adding patches if they feel that require to be merged before RC1
16:32:42 <bauzas> but, I'll ping people anyway asking for reviews
16:33:05 <bauzas> I haven't yet prepared a bobcat tag for bug reports, I'm just doing it now
16:34:02 <bauzas> there
16:34:23 <bauzas> #link https://bugs.launchpad.net/nova/+bugs?field.tag=bobcat-rc-potential feel free to tag any bug report with this tag in order to have it tracked for RC1 and post-RCs
16:34:24 <opendevreview> Jay Faulkner proposed openstack/nova master: [FUP] [ironic] Fix for mutable nova-cpu configs  https://review.opendev.org/c/openstack/nova/+/893790
16:35:03 <bauzas> moving on
16:35:07 <bauzas> #topic Review priorities
16:35:16 <bauzas> #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:35:20 <bauzas> #info As a reminder, people eager to review changes can +1 to indicate their interest, +2 for asking cores to also review
16:35:27 <bauzas> #topic Stable Branches
16:35:35 <bauzas> elodilles: tell the good news
16:35:38 <elodilles> o7
16:35:41 <elodilles> #info stable/train is marked as End of Life and branch is deleted
16:35:46 <bauzas> \o/
16:35:52 <elodilles> #info all stable gates should be OK
16:36:00 <bauzas> \o/
16:36:02 <elodilles> #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci
16:36:26 <elodilles> please add there gate issues if you encounter one ^^^
16:36:32 <elodilles> and that's all from me
16:36:37 <sean-k-mooney> elodilles: what was the result of testing os-vif stable
16:36:48 <bauzas> thanks elodilles
16:37:01 <sean-k-mooney> did the job fail? i.e. should i look at why or did it pass on your DNM patch
16:37:04 <elodilles> sean-k-mooney: let me check it quickly
16:37:11 <sean-k-mooney> no rush
16:37:19 <sean-k-mooney> if it failed i can try and take a look at why later
16:37:41 <bauzas> auniyal: you had other items to mention
16:37:47 <elodilles> sean-k-mooney: gate tests have passed
16:37:52 <sean-k-mooney> sweet
16:38:02 <auniyal> #info Please{10} *review* these backport patches of stable 2023.1, zed and yoga for next minor release
16:38:09 <auniyal> #info most of these already have one +2.
16:38:09 <auniyal> #link https://etherpad.opendev.org/p/release-liaison-PatchesToReview
16:38:15 <auniyal> thanks
16:38:43 <bauzas> cool, will try a round tomorrow
16:39:11 <bauzas> sounds to me it's important to deliver a 2023.1 release shortly
16:39:34 <bauzas> #topic Open discussion
16:39:45 <bauzas> nothing on the agenda, anything anyone ?
16:42:01 <bauzas> ok, looks not
16:42:05 <bauzas> thanks everyone
16:42:09 <bauzas> see you next week
16:42:12 <bauzas> #endmeeting