Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2025-09-09
15:51:27 sean-k-mooney i.e. before the sabel tbranch is created
15:51:29 elodilles bauzas: that means, that teams can backport bug fixes and if those are release critical, then further RCs can be proposed
15:51:36 opendevreview Nell Jerram proposed openstack/nova master: Add managed='no' flag to libvirt XML definition for VIF type TAP https://review.opendev.org/c/openstack/nova/+/960284
15:51:54 elodilles bauzas: until Final RC deadline -> https://releases.openstack.org/flamingo/schedule.html
15:52:07 bauzas elodilles: my question is specifically about https://review.opendev.org/c/openstack/nova/+/960242
15:52:08 elodilles i.e. until week R-1
15:52:41 bauzas elodilles: the master patch was merged in master which was Flamingo, this was proposed against Epoxy, can I +W it once we're past RC1 ?
15:52:48 sean-k-mooney thats already merged in master before rc1 is created
15:52:54 bauzas correct
15:53:02 sean-k-mooney so it will be in stable/2025.2
15:53:10 sean-k-mooney so i dont see why that cant proceed
15:53:21 sean-k-mooney there is no chach of a regression
15:53:41 bauzas I was thinking we were holding stable approvals on /any/ stable branch during the RC phases, but that's probably me who's overthinking
15:53:53 sean-k-mooney going form 2025.1 to 2025.2
15:54:15 sean-k-mooney unless it has teh poteial to impact grenade i dont hink we need too
15:54:32 sean-k-mooney so older banches like 2024.2 i think does not require any freeze
15:54:43 elodilles bauzas: you can, but the question is whether it is RC critical, and if not, will it cause trouble when an RC critical issue comes up and an RC2 needs to be proposed
15:54:46 bauzas of course once we branch 2025.2 with RC1, any master patch merged after couldn't be backported to 2025.1 as it would require to be merged first on 2025.2 which is only accepting regression fixes
15:55:21 sean-k-mooney elodilles: the patch in question was merged on master 4 days ago
15:55:24 sean-k-mooney https://review.opendev.org/c/openstack/nova/+/954613
15:55:41 elodilles sean-k-mooney: yes, but i guess bauzas just used it as an example :)
15:55:42 sean-k-mooney so in this specific example it will be included in rc1 anyway
15:56:03 sean-k-mooney ack
15:56:31 bauzas elodilles: not exactly an example, I'm a stable core and I was about to review that 2025.1 proposal, so I was wondering whether I should/could +W it after Thursday
15:56:33 elodilles sean-k-mooney: and of course, as you wrote, too, until RC1 is not merged, and stable/2025.2 branch is not cut, everything will be included from 'master'
15:58:02 elodilles bauzas: i see. so the question is then, if we see that too risky to merge now, just before the flamingo release. we can postpone the backport for later time, when we are over the 2025.2 Flamingo coordinated release
15:58:41 elodilles bauzas: so yes, the best is to keep master (and then stable/2025.2) as stable as possible, and maybe postpone every (risky) backports
15:59:32 sean-k-mooney im not sure if this woudl be condiered risky for what its worth at least when it comes to posibel impact on the 2025.2 release
15:59:45 elodilles bauzas: as far as i remember you usually said that after RC1 cut stable backports to stable/<current_series> should be avoided to merge, unless they are release critical o:)
16:00:09 sean-k-mooney yep ^
16:00:15 elodilles so that is a nice and safe approach :)
16:00:15 sean-k-mooney and the bot patches
16:01:18 sean-k-mooney its imporant to merge the bot patches including any translation patches that might be propsoed once the stable branhc is created
16:01:35 bauzas elodilles: that's correct yes, that was my thinking but maybe I was overthinking it
16:02:35 elodilles sean-k-mooney: yes. as those should be pretty harmless and in fact, needed (but no need for an RC2 if those are the only merged patches on the stable branch)
16:03:25 elodilles bauzas: it's better to be safe than sorry o:)
16:03:44 opendevmeet The meeting name has been set to 'nova'
16:03:44 opendevmeet Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:03:44 opendevmeet Meeting started Tue Sep 9 16:03:44 2025 UTC and is due to finish in 60 minutes. The chair is Uggla. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:03:44 Uggla #startmeeting nova
16:03:53 Uggla Hello everyone
16:03:56 sean-k-mooney o/
16:04:00 ratailor o/
16:04:04 elodilles o/
16:04:53 dansmith o/
16:05:24 Uggla Let's start
16:05:31 fwiesel o/
16:05:36 Uggla #topic Bugs (stuck/critical)
16:05:43 Uggla #info No Critical bug
16:05:43 bauzas \o
16:05:54 Uggla #topic Gate status
16:06:00 Uggla #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:06:07 gibi o/
16:06:10 Uggla #link https://etherpad.opendev.org/p/nova-ci-failures-minimal
16:06:20 Uggla #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&branch=stable%2F*&branch=master&pipeline=periodic-weekly&skip=0 Nova&Placement periodic jobs status
16:06:28 Uggla #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:06:37 Uggla #info Please try to provide a meaningful comment when you recheck
16:07:39 Uggla I'm not aware of any issue on the upstream CI. Am I right ?
16:08:03 elodilles maybe worth to mention osc-placement
16:08:20 sean-k-mooney oh?
16:08:26 sean-k-mooney is there somethign we need to adress
16:08:30 elodilles tox-functional-py39 job is failing on its master and stable/2025.2 branch
16:08:36 sean-k-mooney oh
16:08:39 sean-k-mooney so we shoudl delete that
16:08:43 elodilles i've prepared a patch for that: https://review.opendev.org/q/I7726c99961ef41c7cf5ec71bf28df15eee191877
16:08:48 sean-k-mooney and make suer we have a 3.12 job instead
16:09:10 sean-k-mooney ah the clinet branches were cut last week
16:09:17 sean-k-mooney so we need to backport it to 2025.2 as well
16:09:21 elodilles sean-k-mooney: exactly
16:09:23 sean-k-mooney since hte branch already exists
16:09:28 elodilles yes
16:09:53 sean-k-mooney we already have a 3.12 version fo the job so +2
16:10:00 elodilles yes, that too
16:10:03 gibi I'm +2
16:10:07 elodilles thanks o/
16:10:16 elodilles then it should be fine now :]
16:10:21 sean-k-mooney this is a test only chnage so i dont thinkw e need to do another release right
16:10:42 elodilles sean-k-mooney: yes. no need for another release
16:10:47 sean-k-mooney +1
16:11:11 sean-k-mooney anything else for ci?
16:11:20 elodilles nothing from me
16:11:24 sean-k-mooney gibi: you mentioned there was a pyroute2 issues
16:11:57 sean-k-mooney has the bump been reverted/capped
16:12:10 sean-k-mooney or are we waiting on anohter release by the pyroute2 maintainer
16:13:17 sean-k-mooney ah no worries we can move on
16:13:29 sean-k-mooney https://review.opendev.org/c/openstack/requirements/+/957657 might have been the patch
16:13:48 tkajinam o/
16:13:48 Uggla maybe, we can come back later to that point later
16:14:13 Uggla skiping next point because gmaan is on pto.
16:14:21 Uggla #topic Release Planning
16:14:30 Uggla #link https://releases.openstack.org/flamingo/schedule.html
16:14:37 Uggla #info Nova deadlines are set in the above schedule
16:14:43 Uggla #info RC1 target is Thursday.
16:14:49 Uggla #info PTG etherpad for 2026.1 is available: https://etherpad.opendev.org/p/nova-2026.1-ptg
16:15:02 elodilles and we have the RC1 release patches proposed ;)
16:15:23 Uggla thx elodilles !
16:15:24 elodilles nova: https://review.opendev.org/960103 and placement: https://review.opendev.org/960108
16:15:35 gibi (lets get back to pyroute2 at the end of the meeting)h
16:15:46 Uggla gibi 👍
16:16:04 Uggla Do not forget to register to PTG

Earlier   Later