| ralonsoh | ok folks, nova-ovs-hybrid-plug is green again: https://zuul.opendev.org/t/openstack/builds?job_name=nova-ovs-hybrid-plug&skip=0 | 08:18 |
|---|---|---|
| ralonsoh | sorry for the inconveniences | 08:18 |
| gibi | ralonsoh: thanks for the quick fix1 | 08:32 |
| opendevreview | Balazs Gibizer proposed openstack/nova master: Add spawn_on https://review.opendev.org/c/openstack/nova/+/948079 | 09:13 |
| opendevreview | Balazs Gibizer proposed openstack/nova master: Move ComputeManager to use spawn_on https://review.opendev.org/c/openstack/nova/+/948186 | 09:13 |
| opendevreview | Balazs Gibizer proposed openstack/nova master: Move ConductorManager to use spawn_on https://review.opendev.org/c/openstack/nova/+/948187 | 09:13 |
| opendevreview | Balazs Gibizer proposed openstack/nova master: Make nova.utils.pass_context private https://review.opendev.org/c/openstack/nova/+/948188 | 09:13 |
| opendevreview | Balazs Gibizer proposed openstack/nova master: Rename DEFAULT_GREEN_POOL to DEFAULT_EXECUTOR https://review.opendev.org/c/openstack/nova/+/948086 | 09:13 |
| opendevreview | Balazs Gibizer proposed openstack/nova master: Make the default executor configurable https://review.opendev.org/c/openstack/nova/+/948087 | 09:13 |
| opendevreview | Balazs Gibizer proposed openstack/nova master: Print ThreadPool statistics https://review.opendev.org/c/openstack/nova/+/948340 | 09:13 |
| opendevreview | Balazs Gibizer proposed openstack/nova master: Document threading mode and tuneables https://review.opendev.org/c/openstack/nova/+/949364 | 09:13 |
| opendevreview | Balazs Gibizer proposed openstack/nova master: Allow services to start with threading https://review.opendev.org/c/openstack/nova/+/948311 | 09:13 |
| opendevreview | Balazs Gibizer proposed openstack/nova master: Run nova-next with n-sch in threading mode https://review.opendev.org/c/openstack/nova/+/948450 | 09:13 |
| opendevreview | Balazs Gibizer proposed openstack/nova master: Do not yield in threading mode https://review.opendev.org/c/openstack/nova/+/950994 | 09:13 |
| opendevreview | Balazs Gibizer proposed openstack/nova master: Run nova-api and -metadata in threaded mode https://review.opendev.org/c/openstack/nova/+/951957 | 09:13 |
| opendevreview | Balazs Gibizer proposed openstack/nova master: Allow to start unit test without eventlet https://review.opendev.org/c/openstack/nova/+/953436 | 09:13 |
| opendevreview | Balazs Gibizer proposed openstack/nova master: Run unit test with threading mode https://review.opendev.org/c/openstack/nova/+/953475 | 09:13 |
| opendevreview | Balazs Gibizer proposed openstack/nova master: [test]RPC using threading or eventlet selectively https://review.opendev.org/c/openstack/nova/+/953815 | 09:13 |
| * gibi is sorry for spamming the CI | 09:14 | |
| opendevreview | Balazs Gibizer proposed openstack/nova master: Warn on long task wait time for executor https://review.opendev.org/c/openstack/nova/+/952666 | 09:17 |
| mikal | Herm, now the ceph CI test appears broken? | 10:04 |
| mikal | Some packages could not be installed. This may mean that you have | 10:04 |
| mikal | requested an impossible situation or if you are using the unstable | 10:04 |
| mikal | distribution that some required packages have not yet been created | 10:04 |
| mikal | or been moved out of Incoming. | 10:04 |
| mikal | The following information may help to resolve the situation: | 10:04 |
| mikal | The following packages have unmet dependencies: | 10:04 |
| mikal | qemu-block-extra : Depends: librbd1 (>= 19.2.1-0ubuntu0.24.04.1) but 19.2.0-0ubuntu0.24.04.2 is to be installed | 10:04 |
| mikal | E: Unable to correct problems, you have held broken packages. | 10:04 |
| mikal | + functions-common:apt_get:1 : exit_trap | 10:04 |
| mikal | + ./stack.sh:exit_trap:543 : local r=100 | 10:04 |
| mikal | ++ ./stack.sh:exit_trap:544 : jobs -p | 10:04 |
| mikal | + ./stack.sh:exit_trap:544 : jobs= | 10:04 |
| mikal | + ./stack.sh:exit_trap:547 : [[ -n '' ]] | 10:04 |
| mikal | + ./stack.sh:exit_trap:553 : '[' -f '' ']' | 10:04 |
| mikal | + ./stack.sh:exit_trap:558 : kill_spinner | 10:04 |
| mikal | + ./stack.sh:kill_spinner:453 : '[' '!' -z '' ']' | 10:04 |
| mikal | + ./stack.sh:exit_trap:560 : [[ 100 -ne 0 ]] | 10:04 |
| mikal | + ./stack.sh:exit_trap:561 : echo 'Error on exit' | 10:04 |
| mikal | Error on exit | 10:04 |
| mikal | + ./stack.sh:exit_trap:563 : type -p generate-subunit | 10:04 |
| mikal | + ./stack.sh:exit_trap:566 : [[ -z /opt/stack/logs ]] | 10:04 |
| mikal | + ./stack.sh:exit_trap:569 : /usr/bin/python3.12 /opt/stack/devstack/tools/worlddump.py -d /opt/stack/logs | 10:04 |
| mikal | + ./stack.sh:exit_trap:578 : exit 100 | 10:04 |
| mikal | *** FINISHED *** | 10:04 |
| sean-k-mooney | that sound like a mirror issue | 10:05 |
| sean-k-mooney | i suspect that will resolve quickly | 10:06 |
| mikal | Yeah, I just feel bad mashing retry over and over, but damn these releasenotes are hard to get through CI this week. | 10:07 |
| sean-k-mooney | so lookging at https://packages.ubuntu.com/noble-updates/qemu-block-extra | 10:09 |
| sean-k-mooney | it has librbd1 (>= 19.2.0-0ubuntu0.24.04.2) [not armhf] | 10:10 |
| sean-k-mooney | so im wondering what verion of qemu you have | 10:10 |
| sean-k-mooney | mikal: do you have a link to the job | 10:11 |
| mikal | https://zuul.opendev.org/t/openstack/build/8d3bacc67bf5473993c8123ea03e969a | 10:11 |
| sean-k-mooney | for some reasons its askign for a newer dep then is enabled in the noble and noble-updates | 10:12 |
| mikal | And we're confident that job uses Ubuntu Noble? | 10:13 |
| sean-k-mooney | they all do on nova except the nova-hybrid-plug job | 10:13 |
| sean-k-mooney | but ya htis sjob is also noble | 10:13 |
| mikal | Yeah, I agree that the Ubuntu packages shouldn't need 19.2.1 as best as I can tell. | 10:14 |
| mikal | Plucky and Questing has 19.2.1... | 10:15 |
| sean-k-mooney | so the question is has a ppa or repo been enable dhat is messing that up | 10:16 |
| sean-k-mooney | so we dont have the apt config and i cant see why it failed so i would say recheck it once and see if it happens again | 10:18 |
| mikal | I'd already done that, the previous failure was https://zuul.opendev.org/t/openstack/build/92953a7b8ed64aad84423567eab627b6 from 4.5 hours ago. | 10:21 |
| mikal | And https://zuul.opendev.org/t/openstack/build/02ab3d4b300d40b68effc5b19fdfcb21 from 7 hours ago | 10:22 |
| mikal | So this started happening sometime in the last 13 hours, but more than 8 or so hours ago. | 10:22 |
| frickler | I saw the same issue in the osa channel. looks like ubuntu messed up some packaging and reverted/fixed some hours ago, need to wait for our mirrors to catch up I guess | 11:42 |
| jrosser | frickler: I was waiting until later in my day so ask if there was anything could be done to preempt the mirror update | 11:55 |
| jrosser | *to ask | 11:55 |
| cardoe | Did I mess up my calendar reminder for nova meeting? | 15:00 |
| cardoe | I'm really just looking to understand what else we need to do to get https://review.opendev.org/c/openstack/nova-specs/+/471815 to land? | 15:01 |
| cardoe | Landing that is the blocker for coordinating multiple projects to land the tests and the implementations. | 15:02 |
| Uggla | Nova meeting in ~50mn | 15:11 |
| Uggla | cardoe, I think you can join to discuss it in the open discussion topic. | 15:12 |
| Uggla | From what I see the patch seems in a good shape. | 15:13 |
| cardoe | okay thanks | 15:28 |
| Uggla | Nova meeting in around 10mn | 15:49 |
| zigo | Under Python 3.13, nova-scheduler.log spits many of these: https://paste.opendev.org/show/bLJRfWD6kJr07tgShen2/ | 15:54 |
| zigo | Does anyone have a clue what's going on ? | 15:54 |
| zigo | FYI, this is with eventlet 0.40.0+2025.06.18.e470c1f493 (ie: master branch up to commit e470c1f493). | 15:56 |
| zigo | It's doing this in loop. | 15:57 |
| zigo | nova-conductor too. | 15:57 |
| zigo | Should I open a new bug? | 15:58 |
| gibi | zigo: I can only add that I haven't seen similar in py312 | 15:58 |
| Uggla | #startmeeting nova | 16:00 |
| opendevmeet | Meeting started Tue Jul 1 16:00:24 2025 UTC and is due to finish in 60 minutes. The chair is Uggla. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
| opendevmeet | The meeting name has been set to 'nova' | 16:00 |
| Uggla | Hello everyone | 16:00 |
| gibi | o/ | 16:01 |
| bauzas | o/ | 16:01 |
| bauzas | (I'll need to leave a bit early, like 15 mins before the end) | 16:01 |
| masahito | o/ | 16:02 |
| Uggla | #topic Bugs (stuck/critical) | 16:02 |
| Uggla | #info No Critical bug | 16:02 |
| Uggla | #topic Gate status | 16:03 |
| Uggla | #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs | 16:03 |
| Uggla | #link https://etherpad.opendev.org/p/nova-ci-failures-minimal | 16:03 |
| 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:03 |
| Uggla | #info Please look at the gate failures and file a bug report with the gate-failure tag. | 16:03 |
| Uggla | #info Please try to provide a meaningful comment when you recheck | 16:03 |
| Uggla | #topic tempest-with-latest-microversion job status | 16:04 |
| Uggla | #link https://zuul.opendev.org/t/openstack/builds?job_name=tempest-with-latest-microversion&skip=0 | 16:04 |
| Uggla | gmaan, something you'd like to tell us ? | 16:04 |
| fwiesel | o/ | 16:04 |
| Uggla | not sut gmaan is available today, so I'm gonna move on. | 16:05 |
| Uggla | #topic Release Planning | 16:06 |
| Uggla | #link https://releases.openstack.org/flamingo/schedule.html | 16:06 |
| Uggla | #info Nova deadlines are set in the above schedule | 16:06 |
| Uggla | #info Nova spec freeze is Thursday. | 16:06 |
| Uggla | ⚠️ ^ | 16:06 |
| Uggla | FYI, I have discussed with masahito about https://review.opendev.org/c/openstack/nova-specs/+/951636 and if he will be able to submit an update. So it will give us a chance to approve this one. | 16:08 |
| opendevreview | Stephen Finucane proposed openstack/nova master: api: Correct expected errors https://review.opendev.org/c/openstack/nova/+/951640 | 16:08 |
| Uggla | #topic Review priorities | 16:08 |
| masahito | yup. let me focus on updating my specs tomorrow. | 16:08 |
| Uggla | masahito 👍 | 16:09 |
| Uggla | #link https://etherpad.opendev.org/p/nova-2025.2-status | 16:09 |
| Uggla | I have updated the doc and updated launchpad accordingly. So blueprints, SL blueprints should be all in the correct status. | 16:10 |
| Uggla | If you see something wrong in the doc, please let me know. | 16:10 |
| Uggla | #topic OpenAPI | 16:11 |
| Uggla | #link: https://review.opendev.org/q/topic:%22openapi%22+(project:openstack/nova+OR+project:openstack/placement)+-status:merged+-status:abandoned | 16:11 |
| Uggla | #info 19 decrease -6. \o/ | 16:11 |
| Uggla | elodilles is not available so I'll skip the stable branch topic. | 16:12 |
| Uggla | #topic vmwareapi 3rd-party CI efforts Highlights | 16:12 |
| Uggla | fwiesel do you have something to share ? | 16:12 |
| Uggla | fwiesel ? | 16:14 |
| fwiesel | Uggla: No, nothing from my side | 16:14 |
| Uggla | fwiesel ok thx | 16:14 |
| Uggla | #topic Gibi's news about eventlet removal. | 16:14 |
| Uggla | #link Blog: https://gibizer.github.io/categories/eventlet/ | 16:15 |
| Uggla | #link nova-scheduler series is ready for core review, starting at https://review.opendev.org/c/openstack/nova/+/947966 | 16:15 |
| gibi | o/ | 16:15 |
| Uggla | gibi the mic is yours | 16:15 |
| gibi | so the scatter gather refactor patch has been landed | 16:15 |
| gibi | thanks for the reviews | 16:15 |
| Uggla | \o/ | 16:15 |
| gibi | the next two patches are also approved but the gate was / is pretty flaky in the recent days so they are not landed yet | 16:16 |
| gibi | (hybrid-plug and ceph issuees) | 16:16 |
| gibi | I fixed the comments form bauzas on the next patch in the series about a possible race condition. Please take a look | 16:16 |
| gibi | On the top of the series I started an effor to run unit tests without eventlet | 16:17 |
| gibi | the effort starts here https://review.opendev.org/c/openstack/nova/+/953436/5 | 16:17 |
| gibi | couple of patches later in that series we have a job that runs most of our unit tests without monkey patching and with threading oslo.service and oslo.messaging backend | 16:18 |
| gibi | there is a list of excluded test I have to work through | 16:18 |
| gibi | I'm tracking to type of problems. Sqlaclhemy nonsense errors and simple test case hangs | 16:18 |
| gibi | s/to/two/ | 16:19 |
| gibi | you can see them noted in the test exclude list | 16:19 |
| gibi | I think we can make the new zuul job voting pretty soon | 16:19 |
| gibi | (while keeping some excludes) | 16:19 |
| gibi | that is it from me | 16:20 |
| sean-k-mooney | o/ sorry had this behind anohter window | 16:20 |
| Uggla | gibi do you have some kind of "urgent" review anymore ? | 16:21 |
| bauzas | I'll continue to review the series for sure | 16:22 |
| gibi | Uggla: the bottom of the series is as urgent as the eventlet removal :) | 16:22 |
| gibi | bauzas: hanks | 16:22 |
| gibi | thanks | 16:22 |
| gibi | I think we can move on :) | 16:24 |
| Uggla | BTW we have Nova Eventlet removal sync tomorrow too. | 16:24 |
| Uggla | 14:30 UTC | 16:25 |
| gibi | yepp we have the call | 16:25 |
| gibi | as planned | 16:25 |
| Uggla | thanks gibi, next topic | 16:25 |
| Uggla | #topic Open discussion | 16:25 |
| Uggla | #topic (fwiesel) Evacuate Action & InstanceInvalidState | 16:25 |
| Uggla | fwiesel please go ahead. | 16:26 |
| fwiesel | So, we are currently looking into doing HA by using the evacuate action on instances, and were running into various states, where it was not possible. | 16:26 |
| fwiesel | From our side, evacuation usually happens when the host is down so can happen at any time. | 16:27 |
| fwiesel | And I was wondering, if it wouldn't make sense to adjust the code so it can evacuate an instance in as many sitations as possible. | 16:27 |
| fwiesel | So, raising an InstanceInvalidState is merely a reflection of what has been implemented. What do you say? | 16:28 |
| gibi | do you have specific examples of states you want to evacuate from? | 16:29 |
| cardoe | So I'll say internally we've got extra stuff which we don't see nova ever being able to handle. | 16:29 |
| cardoe | Like even human involved state | 16:29 |
| fwiesel | Let me think. For starters: Verify-Resize. | 16:30 |
| fwiesel | But let's say, we have a live-migration, and that host falls down. I still would like to do a failover | 16:31 |
| gibi | verify-resize: so while you could evacuate from that state you also need to implement a proper cleanup in the nova-compute coming up in the source node of the original resize | 16:31 |
| sean-k-mooney | so evacuate requires you the admin | 16:32 |
| sean-k-mooney | to assert that the vm is not running on any host | 16:32 |
| sean-k-mooney | so allowing it in verify resize and othe rstates is questionable | 16:32 |
| sean-k-mooney | espically since in that state your in the middle of an ongoing migration | 16:32 |
| cardoe | Yeah there's a lot of squirrely cases there which need to be monitored for. | 16:32 |
| sean-k-mooney | and the flavor that is in use is kind of ill defiend | 16:33 |
| sean-k-mooney | its technialy the new one in a real reaise but it has nto beeen confirm so you woudl want ot evacuate to the old one, but hte numa toplogy and ohter things are all in a weird hybrid state | 16:33 |
| sean-k-mooney | what you likely should be able to do is revert the resize in verify-resize | 16:34 |
| gibi | so in general it would be nice to support these but in practic it seems like a bunch of cans of worms | 16:34 |
| sean-k-mooney | even if the dest host is down | 16:34 |
| sean-k-mooney | then evacuate it | 16:34 |
| sean-k-mooney | if needed | 16:34 |
| cardoe | We've got a whole thing out of band that's specific to the hypervisor in use for these items. | 16:35 |
| gibi | yeah allowing revert-resize in souce host down is one way, even though a weird one. Who wants to revert a resize that will lead to the VM runing nowhere :) | 16:35 |
| fwiesel | But technically, an evacuate is practically a rebuild. So, I can start from "scratch" (nova wise) | 16:35 |
| sean-k-mooney | gibi: well it would revert reisze when dest down and conrim resize when source down | 16:35 |
| fwiesel | I just have to build the VM up somewhere fitting the spec | 16:35 |
| gibi | yeah starting is easy, cleaning up the remnants is messy | 16:36 |
| sean-k-mooney | fwiesel: yes and no | 16:36 |
| cardoe | yeah but you need to make sure that gets fully cleaned up. | 16:36 |
| fwiesel | Of course | 16:36 |
| sean-k-mooney | we have some api contract about preserving storage in some cases | 16:36 |
| sean-k-mooney | please there are the neutorn/cidner state clean up that we need to do | 16:36 |
| fwiesel | Exactly | 16:36 |
| gibi | sean-k-mooney: revert-resize: ahh right | 16:36 |
| fwiesel | Right now, I have the choice to implement all that outside of nova. Or within nova | 16:37 |
| sean-k-mooney | to do this in nova woudl need a very detailed spec | 16:37 |
| fwiesel | Well, I would not tackle all cases in one go. | 16:37 |
| sean-k-mooney | and you woudl have to consier things liek cross cell resize | 16:37 |
| fwiesel | And maybe then not resize :) | 16:38 |
| cardoe | its a worthy goal | 16:38 |
| sean-k-mooney | right but even if you take an incremntal approch you need to have each incremantal chagne be valid | 16:38 |
| sean-k-mooney | i think for rezie it woubld be siiler to allwo the migration to compelte or revert based on which end is alive | 16:38 |
| cardoe | I'll say when I did this with xen it was much easier because xapi had an object version field so I used that as a monotonic number which also then was stored in the nova DB | 16:38 |
| sean-k-mooney | and if they are both dead well your kind of out of luck | 16:39 |
| fwiesel | Of course. I was more fearing that it will be difficult to test that in the CI, and adds complexity. Which might be areason you might not want it at all. | 16:39 |
| cardoe | So each time the instance got updated the monotonic number increased and that got pushed down into xapi | 16:39 |
| gibi | fwiesel: start with a simpler state first, write up a spec how would you make sure we end up in the consistent state after the a successful evac and a recovered compute (or an failed evac and a recovered compute, of a failed evac and a retried evac and recovered compute, ...) | 16:39 |
| cardoe | But libvirt doesn't have that | 16:39 |
| cardoe | So when we'd go to clean up, anything that wasn't at the current version could get nuked. | 16:39 |
| sean-k-mooney | fwiesel: so testing that in tempest would be hard, but it would be more doable in the functional suite | 16:39 |
| cardoe | But there's all kinds of dangling references to storage and what not that really are a pain to fix | 16:40 |
| gibi | yepp use functional test for sure | 16:40 |
| fwiesel | Okay, I'll take that with me. Thanks. | 16:40 |
| gibi | we have a limited evact test somewhere after tempest | 16:40 |
| sean-k-mooney | cardoe: so we dont need montic object version in general becasue we assocate the instance with the comptue service that is currently manging it | 16:40 |
| gibi | in a palybook | 16:40 |
| sean-k-mooney | in the post test hook in nova-next | 16:41 |
| cardoe | For us we implemented this more as monitoring that an unexpected object was on a host. | 16:41 |
| sean-k-mooney | and i think the cepch job? | 16:41 |
| sean-k-mooney | cardoe: ya so that kind of approch is not very comaptible with the nova desing although we do have some per host perodic that are intened ot clean up these types of issues | 16:42 |
| cardoe | sean-k-mooney: when you perform a live migrate and the dest goes down at the very end during the resume | 16:42 |
| sean-k-mooney | esplcially on compute agent start up | 16:42 |
| sean-k-mooney | cardoe: if the vm dies before resume libvirt will abort the migraiot | 16:42 |
| sean-k-mooney | if we got to post live migrate | 16:43 |
| sean-k-mooney | its too late to abort but we will update the instance hsot to point to the dest | 16:43 |
| gibi | this is the evac testing in devstack https://github.com/openstack/nova/blob/master/roles/run-evacuate-hook/tasks/main.yaml | 16:43 |
| Uggla | guys is it ok to move to the second point ? | 16:43 |
| gibi | OK for me | 16:44 |
| cardoe | I'm just saying it wasn't a simple problem when I was working in the VM world because hardware dies at the worst possible times and nova can be in many different code calls when that happens. | 16:44 |
| sean-k-mooney | yep lets move on for now. | 16:44 |
| Uggla | #topic (jonnyb) Blueprint for new compute created weigher (https://blueprints.launchpad.net/nova/+spec/node-uptime-weigher) | 16:44 |
| Uggla | jonnyb wants to discuss about this weigher | 16:44 |
| Uggla | jonnyb please go ahead. | 16:45 |
| jonnyb | so I propose a scheduler weigher based on creation date of the compute service | 16:45 |
| jonnyb | the initial idea was to use uptime but this is too dependend on the hypervisor and its driver | 16:45 |
| jonnyb | for us the creation is good enough and we use it since we migrate and deploy a lot of servers | 16:46 |
| gibi | do you have the service creation time as part of the HostState the weigher running on? | 16:46 |
| sean-k-mooney | i belive we do | 16:46 |
| dansmith | that surprises me | 16:46 |
| sean-k-mooney | we have it form the compute node object i belive | 16:46 |
| dansmith | sure, but in hoststate? | 16:47 |
| sean-k-mooney | so this is the poc https://review.opendev.org/c/openstack/nova/+/947503/9/nova/scheduler/weights/compute_created.py | 16:47 |
| dansmith | we have an object, but I didn't think it was queried from the db and thus not complete, but maybe that's not right | 16:48 |
| sean-k-mooney | so yes https://github.com/openstack/nova/blob/master/nova/scheduler/host_manager.py#L176 | 16:49 |
| sean-k-mooney | you could be correct about it being a partial object | 16:49 |
| gibi | based on the poc we have HostState.service.created_at as created_at does not expect to change it is fair to assume it is up to date | 16:49 |
| gibi | isn't expected to change | 16:49 |
| sean-k-mooney | so it looks like this is only populated via update its not populated iva __init__ | 16:50 |
| sean-k-mooney | so im not sure if its there if you disatble the track_isntace_state notifications stuff | 16:51 |
| dansmith | okay we are doing a scatter to gather nodes and hosts from cells | 16:51 |
| sean-k-mooney | we woudl have to confirm that its always present in both confiugrations | 16:51 |
| dansmith | I was thinking we did an optimized construction from a list there | 16:51 |
| dansmith | sean-k-mooney: yeah, good point | 16:51 |
| sean-k-mooney | i think that config only affect the instnace object and how those are populated | 16:52 |
| dansmith | because this could also be triggering massive lazy loads, which would be bad | 16:52 |
| sean-k-mooney | but assuming we have that alwasy | 16:52 |
| sean-k-mooney | i think it would be ok to use it in the weigher provide ya we are not lazy loading this | 16:52 |
| dansmith | we need to make sure this is run in CI at least once so we can examine logs for lazy loads | 16:53 |
| sean-k-mooney | ya we can turn this on in one fo the jobs | 16:56 |
| sean-k-mooney | it wont really have much of an effect with only 1-2 nodes | 16:57 |
| dansmith | we don't have to permanently, but just a DNM on top of this to get a run and make sure we don't see "lazy loading service.created_at" :) | 16:57 |
| sean-k-mooney | we are wrappign the sercie in a readonly dict class that i have not really seen before. i would assume that shoudl also block lazyloading? | 16:58 |
| sean-k-mooney | goign back on topic | 16:58 |
| sean-k-mooney | are we ok with appvoing this as a specless blueprint | 16:58 |
| sean-k-mooney | and continuing to review | 16:58 |
| dansmith | idk | 16:59 |
| Uggla | :+1 for me it looks an interesting weigher. | 16:59 |
| Uggla | gibi, ok for you ? | 17:00 |
| gibi | I'm fine | 17:00 |
| sean-k-mooney | i dont nessiarly have an objection just note that if there are lazy loadign issues they will need to be resolved ebfore we can merge it | 17:00 |
| dansmith | same | 17:00 |
| sean-k-mooney | so it might not be ready before FF | 17:00 |
| sean-k-mooney | but im ok to move to the review and take a look a ci logs ectra | 17:01 |
| Uggla | jonnyb is that ok for you ? | 17:01 |
| jonnyb | thats fine with me, i wasnt aware that lazy loading could be an issue. but good point | 17:01 |
| sean-k-mooney | you defaulted to 1.0 so in theroy its enabled by default | 17:02 |
| sean-k-mooney | so we should b eable to look at any of the current ci logs | 17:02 |
| Uggla | ok last topic: | 17:02 |
| Uggla | #topic (gibi) Workaround for cpython3.13 GC bug needs review https://review.opendev.org/c/openstack/nova/+/952966 | 17:02 |
| dansmith | oh, definitely seems like it should be disabled by default | 17:02 |
| dansmith | that's merged? | 17:02 |
| sean-k-mooney | well we can defintly change that. in the review and ya the gc thing is merged | 17:03 |
| gibi | yepp it is merged | 17:03 |
| Uggla | dansmith yes it seems | 17:03 |
| gibi | I proposed the backport to Epoxy as I know debian want it there | 17:03 |
| gibi | (the cpython bug fixing effort is progressing in the background) | 17:04 |
| gibi | so other than the backport there is nothing else left here | 17:05 |
| gibi | we can move on | 17:05 |
| sean-k-mooney | jonnyb: so without diging deeply https://zuul.opendev.org/t/openstack/build/8a9b0a0404034a79a95621b18e16534b/log/controller/logs/screen-n-sch.txt#1017 you schduler was enabeld and i dont see lazy loadign but we need to look at that properly after the meeting | 17:05 |
| Uggla | ok cardoe, wants to discuss about a patch | 17:05 |
| Uggla | cardoe please go ahead, and then we will close. | 17:06 |
| cardoe | https://review.opendev.org/c/openstack/nova-specs/+/471815 | 17:06 |
| cardoe | It is a proposed spec change to add trunk ports with their vlan tags to the network_data.json | 17:06 |
| sean-k-mooney | ya im +2 on that gibi is +1 because they wont have review bandwith i belvie | 17:06 |
| gibi | I'm +2-1=+1 signalling review bandwidth yes | 17:07 |
| cardoe | It's something written originally by someone not involved in the effort currently. | 17:07 |
| cardoe | But neutron supports defining ports like that. | 17:07 |
| cardoe | There have been a few patches floating around from different operators that are using that functionality as a downstream patch. | 17:07 |
| dansmith | sean-k-mooney: jonnyb: agree, I see the weigher being weighed and no lazy loads in that log, so seems fine | 17:07 |
| gibi | having +1 from rubasov (Bence) is a good sign, he was involved in the original work of trunk | 17:08 |
| cardoe | I've been working to consolidate the downstream operators around a single implementation and wanting to get it upstreamed. | 17:08 |
| sean-k-mooney | yep | 17:08 |
| cardoe | We've got temptest tests written and an implementation. | 17:08 |
| sean-k-mooney | there is code for noav and tempest test too | 17:08 |
| sean-k-mooney | ya https://review.opendev.org/q/topic:%22bp/expose-vlan-trunking%22 | 17:09 |
| sean-k-mooney | this is useful for both vms adn for ironic | 17:09 |
| cardoe | This is just part of my TC work to try and get downstream operators to push back to the community. | 17:09 |
| sean-k-mooney | so the requwst is bascily for another core to sponsor/review this before spec freeze on thruday | 17:10 |
| sean-k-mooney | and then to review the actul pactchs before m3 | 17:10 |
| sean-k-mooney | the one thing i will say is i think we only have turnks in one job | 17:11 |
| sean-k-mooney | so we will need to confirm that this si properly tested in our ci and that that job passes | 17:12 |
| sean-k-mooney | the logs have rotated and the one nova patch that is requried https://review.opendev.org/c/openstack/nova/+/941227 is in merge conflict if i ty an rebase | 17:13 |
| cardoe | I'll work to get folks to update things based on feedback. | 17:13 |
| sean-k-mooney | oh its just missign isnged off by | 17:13 |
| Uggla | cardoe something else you want to ask ? | 17:14 |
| cardoe | No my only question is how can I get this on the roadmap | 17:15 |
| Uggla | We are overtime, so we should close. | 17:18 |
| Uggla | Thanks all | 17:18 |
| Uggla | #endmeeting | 17:18 |
| opendevmeet | Meeting ended Tue Jul 1 17:18:25 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 17:18 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/nova/2025/nova.2025-07-01-16.00.html | 17:18 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/nova/2025/nova.2025-07-01-16.00.txt | 17:18 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/nova/2025/nova.2025-07-01-16.00.log.html | 17:18 |
| sean-k-mooney | cardoe: if we cant proceed with it this cycle i woudl say its still wroth rebaseign for next cycle | 17:21 |
| sean-k-mooney | over all i think geting this in to upstream is a good thing | 17:22 |
| sean-k-mooney | and we shoud encurrage upstream operator change like this when they are in scope of nova ot address | 17:22 |
| Uggla | sean-k-mooney, if you have a min, what do you think of this bug: https://bugs.launchpad.net/nova/+bug/2115116 to my mind it is out of our scope but I'd like your feelings. | 17:23 |
| sean-k-mooney | so i have been kind fo frustrated with some of the install guid work that has been sumited lately | 17:24 |
| cardoe | It's this constant catch-22. The core teams have their own workloads and aren't there to respond to the whims of the operators. So the operators need to contribute more from a review standpoint. But then the operators are all counting spend and wanting to equate their return on investment. | 17:24 |
| sean-k-mooney | Uggla: i see where they are coming form but personlly i dont think the mysql info should be in the install guide either | 17:25 |
| gibi | the core team are basically employed by a company which is also counting profit, so operators could do the same, i.e. paying contributors to become cores | 17:25 |
| sean-k-mooney | beyound a very high level over view of how to use teh config option ectra | 17:25 |
| Uggla | sean-k-mooney, btw there is so many ways to install it. | 17:26 |
| sean-k-mooney | Uggla: i personaly woudl mark it opipion | 17:26 |
| sean-k-mooney | its not invalid i just think we would be better limiting the scope of the doc | 17:27 |
| sean-k-mooney | we do not incldue it in the ubuntu ones either for what its worht | 17:28 |
| sean-k-mooney | so it not a disto specific gap | 17:28 |
| sean-k-mooney | we just doing docuemtn how to install rabbit in the nvoa guide | 17:28 |
| sean-k-mooney | we tell you to configure the transport url transport_url = rabbit://openstack:RABBIT_PASS@controller:5672/ | 17:29 |
| sean-k-mooney | but that is reaonable | 17:29 |
| sean-k-mooney | we coudl add a note to the prequistit section to say that rabbit must be installed adn aviable | 17:29 |
| sean-k-mooney | but i would not say how to do that | 17:29 |
| Uggla | ok I will try to answer in this way tomorrow morning. | 17:31 |
| sean-k-mooney | so i mentioned im furstrated, there has been a number of new contiubotrs filing lots of small bugs for the install guide and submiting pathce for them | 17:32 |
| sean-k-mooney | whil that is not a bad thign persay there has been no dicussion or cordiantion about this effort in genral | 17:32 |
| sean-k-mooney | so it kind of feels lke some owne said to a bunch of interns ehre is a good way to do a first patch | 17:33 |
| sean-k-mooney | but didnt actully talk to use about it first | 17:33 |
| sean-k-mooney | im exagreating a bit | 17:33 |
| sean-k-mooney | but that sort of how it feels, a buch of lower pririty bugs were created and folks are fixign them but no dicsussion of do we have time to review it | 17:34 |
| Uggla | ok but in this case there is no patch attached too. Or I miss something. | 17:37 |
| sean-k-mooney | no i just went out of my way to do some reviews in this area a while ago and sort of got burt out on it | 17:38 |
| Uggla | ok | 17:39 |
| sean-k-mooney | im fine with fixing the docs in general and if they want to add a patch to add it as a preqeusit for all distos then ok but i dont wnat to need to keep updating how to install rabbit if we can avoid it | 17:39 |
| sean-k-mooney | https://review.opendev.org/c/openstack/nova/+/938702 | 17:40 |
| sean-k-mooney | so there is a patch for it a diffent bug https://bugs.launchpad.net/nova/+bug/2091585 | 17:41 |
| sean-k-mooney | so we proably shoudl clsoe the new one as a duplicate of that one | 17:41 |
| sean-k-mooney | ill just do that now if there is no objetion we do not need two bugs for that | 17:42 |
| sean-k-mooney | there is apprenly a commen guide that covers the install we can just link too https://docs.openstack.org/install-guide/environment-messaging-rdo.html | 17:44 |
| sean-k-mooney | there is a ubuntu version too https://docs.openstack.org/install-guide/environment-messaging-ubuntu.html | 17:44 |
| mikal | At least the ceph CI error has changed this morning? | 21:55 |
| mikal | The following packages have unmet dependencies: | 21:55 |
| mikal | qemu-block-extra : Depends: qemu-system-any (= 1:8.2.2+ds-0ubuntu1.7) or | 21:55 |
| mikal | qemu-utils (= 1:8.2.2+ds-0ubuntu1.7) but 1:8.2.2+ds-0ubuntu1.8 is to be installed | 21:55 |
| mikal | E: Unable to correct problems, you have held broken packages. | 21:55 |
| opendevreview | Merged openstack/nova master: doc: Adding link for RabbitMQ installation during nova deployment on controller node. https://review.opendev.org/c/openstack/nova/+/938702 | 22:33 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!