Earlier  
Posted Nick Remark
#openstack-nova - 2025-10-21
14:13:28 bauzas don't be afraid of harassing me :)
14:14:05 Uggla elodilles, o/ I'm gonna have a look either later or tomorrow morning, thanks!
14:15:41 elodilles bauzas Uggla : thanks both of you o:) and sorry for already harassing you, but the releases should merge soon, well, the sooner the better, as we should move Caracal to unmaintained in less than a week o:)
14:17:16 elodilles (sorry for not proposing the release patches last week, in that way, i could have harass you IRL at the Summit o:))
14:17:53 Uggla elodilles 👍
14:36:36 bauzas elodilles: physical harassment is not accepted by the Summit Code of Conduct unfortunately
14:36:59 bauzas but you could have bribed with beers
14:38:22 opendevreview Balazs Gibizer proposed openstack/nova master: Rally job for eventlet-removal https://review.opendev.org/c/openstack/nova/+/960130
14:43:16 opendevreview Balazs Gibizer proposed openstack/nova master: Rally job for eventlet-removal https://review.opendev.org/c/openstack/nova/+/960130
14:48:22 opendevreview Yateesh Kumar MN proposed openstack/nova master: Don't destroy TPM during hard reboot https://review.opendev.org/c/openstack/nova/+/964475
15:02:14 elodilles bauzas: ahh, i've missed the bribe :/ maybe next time then! ;)
15:20:52 Uggla Nova meeting in ~40mn
15:33:24 ali I have a question.
15:33:24 ali I have two aggregates named general and dedicated. The availability zone of general is nova, and the zone of dedicated is another one.
15:33:24 ali I wanted to live migrate an instance from the nova zone to the other zone.
15:33:24 ali To do this, I removed the host from the dedicated aggregate and added it to the general aggregate. After the live migration completed, I moved the compute host back to the dedicated aggregate.
15:33:25 ali After that, I tried to resize the instance to its own flavor, but I got an error related to FilterScheduler and zone specifications. I found that in the nova_api database, the availability_zone was updated correctly, but in the nova database, the availability_zone was not updated.
15:33:30 ali Why did this happen?
16:00:31 Uggla #startmeeting nova
16:00:31 opendevmeet Meeting started Tue Oct 21 16:00:31 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:31 opendevmeet Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:31 opendevmeet The meeting name has been set to 'nova'
16:00:40 fwiesel o/
16:00:49 r-taketn hello
16:01:22 nicolairuckel o/
16:01:23 Uggla Hello everyone
16:01:36 gmaan o/
16:01:39 gibi o/
16:02:17 elodilles o/
16:03:02 Uggla Let's start
16:03:12 Uggla #topic Bugs (stuck/critical)
16:03:21 Uggla #info No Critical bug
16:03:30 Uggla #topic Gate status
16:03:34 bauzas \o
16:03:43 Uggla #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:03:53 Uggla #link https://etherpad.opendev.org/p/nova-ci-failures-minimal
16:04:00 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:04:05 Uggla #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:04:11 Uggla #info Please try to provide a meaningful comment when you recheck
16:04:58 Uggla I have not seen something special about it, unless I miss something.
16:06:41 gibi o/
16:06:47 Uggla gibi, bauzas something to say about the gate ?
16:06:58 bauzas nothing on my radar
16:07:10 gibi there was issues with the wsgi package in the jobs using debian
16:07:23 gibi causign python3.11 crashes on the gate mostly in keystone service
16:07:38 gibi I don't have a tracker for it but it was discussed on -qa
16:08:12 gibi I did not see it today yet but I did not dig for it either
16:08:56 Uggla ok thanks gibi
16:09:06 Uggla moving on to next topic
16:09:09 gmaan one other thing related to gate. grenade jobs settings are updated and now grenade on master will be testing the correct branches upgrade
16:09:25 Uggla thx gmaan
16:09:28 gmaan stable/2025.2 change still in gate but will be merging soon
16:09:34 gmaan #link https://review.opendev.org/c/openstack/grenade/+/961914
16:10:43 gmaan that's all, we can move to next topic
16:10:51 Uggla #topic tempest-with-latest-microversion job status
16:11:17 Uggla gmaan anything you want to say about it ?
16:11:21 gmaan no, did not get chance to look into it.
16:11:51 Uggla no worries, thx gmaan
16:12:11 Uggla #topic Release Planning
16:12:19 Uggla #link https://releases.openstack.org/gazpacho/schedule.html
16:12:57 Uggla ^ dates will be discussed and refined during the PTG.
16:13:12 Uggla #info PTG etherpad for 2026.1 is available: https://etherpad.opendev.org/p/nova-2026.1-ptg
16:13:21 Uggla #info Please add the topics you would like to discuss in the above document.
16:13:29 Uggla #info Take care EU daylight time change this Sunday (26 Oct).
16:14:00 Uggla ^ confused me last week, so here are the expected timelines
16:14:07 Uggla #info PTG meetings (to be confirmed) will happen room grizzly 14:00UTC (start) -> 17:00UTC (end) 4H from Tuesday to Friday.
16:14:21 Uggla #info Please enter your review comments (what was ok, what is not working...)
16:14:41 Uggla I mean comments for the retro
16:14:46 Uggla #info Please update the courtesy ping list, if you want me to notify you about a particular topic.
16:15:00 Uggla #info You might have a earlier session next week for our contributors from Japan (compute graceful shutdown)
16:15:22 bauzas yeah, not only that
16:15:23 Uggla #info the upstream meeting (this one) will be canceled
16:16:00 bauzas we had hallway discussions with some of the Japan contributors, they had a couple of topics to discuss at the PTG
16:16:20 Uggla oh yes, the metadata protection too.
16:16:27 bauzas so it would be nice if we could book some timeslot earlier in the day that's more asian-friendly
16:16:34 bauzas 1 hour should be enough
16:16:51 Uggla 1h for the 2 topics ?
16:17:03 bauzas 1 hour for *any* topic
16:17:10 gmaan early sessions you mean during allocated slots right? from 14 UTC onwards or some other time whihc is more close to japan?
16:17:37 bauzas as soon as you open the possibility for folks to join, please don't expect them to not use that possibility for discussing more
16:17:59 Uggla gmaan no I have not requested the timeslot.
16:18:02 bauzas gmaan: 14UTC is already very late for many of them
16:18:16 bauzas JST is UTC+8 I believe
16:18:17 gmaan yeah, it seems 1 AM
16:18:39 gmaan I want to know if something early than 14 UTC we want to schedule
16:18:56 bauzas well, that's why we have a conversation now
16:18:56 gmaan not later than 14 UTC
16:19:11 bauzas having it earlier would mean that we wouldn't have a solid quorum
16:19:35 bauzas so I need to know who could join something earlier
16:20:36 bauzas another possibility is a very late slot for European, I could try to make it, but again, I'm not sure we would have quorum
16:20:53 gibi I rather be early from EU than late
16:22:17 Uggla Yep I think around 9 or 10 UTC.
16:22:26 bauzas we would miss gmaan, dansmith and melwitt if so
16:22:31 gibi I can join any day on those times
16:22:53 bauzas here is one thought
16:22:59 gmaan yeah, it will be 3 AM in PST
16:23:00 gibi we can have a discussion and have a recap session during the normal hours so other cores get updated
16:23:03 dansmith yeah 10UTC is pretty early for us
16:23:15 Uggla I just expect gibi, bauzas, sean-k-mooney.
16:23:31 bauzas let's try to make it at Thursday or Friday EU mornings

Earlier   Later