Earlier  
Posted Nick Remark
#openstack-nova - 2024-11-26
11:34:42 opendevreview Ivan Tkachuk proposed openstack/nova master: Reduce calls to qemu-img for disk_info https://review.opendev.org/c/openstack/nova/+/936246
12:33:42 opendevreview Balazs Gibizer proposed openstack/nova master: Show candidate combinatorial explosion by dev number https://review.opendev.org/c/openstack/nova/+/855885
13:08:16 opendevreview Rajesh Tailor proposed openstack/nova-specs master: Show finish_time field in instance action show https://review.opendev.org/c/openstack/nova-specs/+/929780
14:47:41 greatgatsby Good day. I think we've found a bug in os-brick fibre_channel.py and just looking to discuss quickly before I submit a ticket or even a PR (I have a working fix currently). Is this the best place to ask about it?
14:54:08 frickler greatgatsby: well technically os-brick belongs to the cinder team, but there might be some overlap. I'd still suggest to start in #openstack-cinder first
14:54:51 greatgatsby thanks, will do
15:41:01 sean-k-mooney gibi: when you have time would you mind reviewing this revert https://review.opendev.org/c/openstack/nova/+/909122
15:41:10 sean-k-mooney its related to our scp converstaion
15:45:42 gibi sean-k-mooney: good point. thanks. +A
15:46:04 sean-k-mooney gibi: that what requried to fix using ip adresses for migration indirectly
15:46:21 gibi I see
15:47:13 sean-k-mooney that is why we dotn need the bluepirnt for that feature
15:47:21 sean-k-mooney it was only failing because of this scp.
15:47:45 sean-k-mooney if you set the migration/live migration inbound adress to an ip it will work once this is reverted
15:48:13 sean-k-mooney that workaround is hardcoded to use instance.host as the source host to pull the file form
16:00:27 opendevmeet The meeting name has been set to 'nova'
16:00:27 opendevmeet Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:27 opendevmeet Meeting started Tue Nov 26 16:00:27 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:27 bauzas #startmeeting nova
16:01:18 bauzas #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
16:01:27 tkajinam o/
16:01:33 elodilles o/
16:01:48 s3rj1k hi all
16:02:27 Uggla o/
16:03:30 bauzas hey
16:04:22 bauzas starting slowly
16:04:31 bauzas #topic Bugs (stuck/critical)
16:04:49 bauzas #info No Critical bug
16:05:02 bauzas #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
16:05:08 bauzas any questions about bugs ?
16:07:06 bauzas ok moving on
16:07:35 bauzas #topic Gate status
16:07:43 bauzas #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:07:48 bauzas #link https://etherpad.opendev.org/p/nova-ci-failures-minimal
16:07:59 bauzas #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&branch=stable%2F*&branch=master&pipeline=periodic-weekly&skip=0
16:08:14 bauzas #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:08:19 bauzas #info Please try to provide meaningful comment when you recheck
16:08:29 bauzas I saw a couple of failures but those are known issues
16:08:40 bauzas anything about CI failures that is pretty new ?
16:08:52 bauzas (all periodics are green)
16:10:00 bauzas looks not, moving on
16:10:09 bauzas #topic Release Planning
16:10:15 bauzas #link https://releases.openstack.org/epoxy/schedule.html
16:10:20 bauzas #action bauzas to add Epoxy nova deadlines in the schedule
16:10:45 bauzas I'm pretty done with the patch proposal but I need to fix something before uploading it
16:11:03 bauzas #topic Review priorities
16:11:10 bauzas #link https://etherpad.opendev.org/p/nova-2025.1-status
16:11:28 bauzas the page should be up to date, feel free to use it and amend it
16:12:46 bauzas anything about that ?
16:13:15 gibi o/
16:13:24 sean-k-mooney o/ nothing from me on that topic
16:13:33 bauzas cool
16:13:41 bauzas #topic Stable Branches
16:13:49 bauzas elodilles: shoor
16:14:02 elodilles #info stable/2024.2 gate seem to be OK
16:14:12 elodilles #info stable/2024.1 gate is blocked on grenade-skip-level & stable/203.2 is blocked on nova-grenade-multinode
16:14:21 elodilles failure is due to stable/2023.1->unmaintained/2023.1 transition, devstack and grenade fixes are proposed
16:14:52 elodilles and actually the 2024.1 branch fix (grenade) patch is already in the gate queue
16:15:05 elodilles though: other workaround is to set these jobs as non-voting - given that gate should not rely on an unmaintained branch
16:15:21 elodilles see further details:
16:15:28 elodilles #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci
16:15:59 elodilles and that's all from me about stable branches now
16:16:09 bauzas thanks
16:16:13 elodilles np
16:16:30 bauzas #topic vmwareapi 3rd-party CI efforts Highlights
16:16:33 bauzas fwiesel: around ?
16:17:20 bauzas looks he's AFK
16:17:24 bauzas no worries, moving on
16:17:28 fwiesel Sorry , I am here
16:17:31 bauzas ah
16:17:41 bauzas anything to raise from your side ?
16:17:59 fwiesel There was a regression in oslo.utils (master) and I have created a change to fix it: https://review.opendev.org/c/openstack/oslo.utils/+/936247
16:18:23 fwiesel Hopefully the builds will back to the two failures and I will tackle these then.
16:18:26 fwiesel That's from my side
16:18:28 sean-k-mooney ah is that related to removign netifaces
16:18:55 bauzas okay, gtk
16:18:57 bauzas thanks
16:19:16 tkajinam get that in
16:19:23 bauzas nice, thanks tkajinam
16:19:24 tkajinam fwiesel, if you need a new release with the fix early then ping me
16:19:36 tkajinam once that is merged
16:20:01 fwiesel tkajinam: Thanks, I'll let you know
16:20:39 bauzas cool
16:20:47 bauzas then moving to the last item from the agenda
16:20:54 bauzas #topic Open discussion
16:21:01 bauzas anything in the agenda, so anything anyone ?
16:21:11 s3rj1k there is this https://bugs.launchpad.net/nova/+bug/2089386
16:21:34 sean-k-mooney i have one followup form last week too
16:21:48 sean-k-mooney lets start with s3rj1k topic
16:22:29 bauzas ok, s3rj1k, shoot
16:23:30 s3rj1k idea is to allow for host discovery to be concurrent, both cli and internal using distributed locking
16:24:25 sean-k-mooney so perhaps i can provide some context
16:24:46 s3rj1k thi mostly needed for k8s like envs where discovery is run in multiple places
16:24:47 sean-k-mooney s3rj1k is interested in using the discover hsost perodic in a ha env
16:25:09 bauzas s3rj1k: I think that topic requires a proper discussion that can't be done during a meeting
16:25:18 sean-k-mooney currently we require that if you use the perodic its enabled on at most one host
16:25:29 sean-k-mooney they would like to adress that pain point
16:25:35 bauzas if we want to discuss about the design, it has to be an async conversation that has to be in a proper formatted document
16:26:04 bauzas that's the reason why we introduced our specification program for those kind of feature requests
16:26:14 s3rj1k bauzas: spec? or rfe is enough for this time?

Earlier   Later