Earlier  
Posted Nick Remark
#openstack-nova - 2025-08-01
12:48:25 Uggla gibi, 👍
12:48:47 gibi pinged #openstack-qa about it
13:54:44 dansmith gibi: got it
13:55:50 gibi dansmith: thanks
13:56:00 gibi Uggla: https://review.opendev.org/c/openstack/openstacksdk/+/956369 is unblocking the gate hopefully
14:14:37 opendevreview Merged openstack/nova master: Document native threading mode and tuneables https://review.opendev.org/c/openstack/nova/+/949364
14:24:00 opendevreview Lajos Katona proposed openstack/nova master: WIP Use SDK for Neutron https://review.opendev.org/c/openstack/nova/+/928022
14:24:42 stephenfin oooh
14:48:18 opendevreview Artem Vasilyev proposed openstack/nova master: Fix functional tests and mypy linter on macOS https://review.opendev.org/c/openstack/nova/+/937727
14:48:34 opendevreview Artem Vasilyev proposed openstack/nova master: mypy: fix type annotations for PciDevicePoolList and NUMATopologyLimits https://review.opendev.org/c/openstack/nova/+/955792
15:13:55 sean-k-mooney not sure how folks feel about modifyign code to allw the test to run on macos
15:13:57 sean-k-mooney https://review.opendev.org/c/openstack/nova/+/937727
15:14:38 sean-k-mooney i vagly recall doign somethign similar for arm/riscv and or cygwin in the past
15:14:57 sean-k-mooney mainly fixing mock to make tests pass where we assume the architecutre
15:20:09 dansmith I'm okay with changes to make unit (and functional?) tests run on macos
15:20:21 dansmith not okay with making runtime changes
15:20:45 dansmith the check for ty,TYPE_CHECKING seems really weird and like probably some sort of hack that could end up affecting runtime in some weird scenario
15:59:01 sean-k-mooney dansmith: ya that the bit that i was unsure about
15:59:25 sean-k-mooney so thats a standard thing that is ues for doign thing like optional inporitng for type hint
15:59:51 sean-k-mooney but it normally not used in if statement like that
16:00:45 sean-k-mooney i flipped beteen +2 -1 liek 3 or 4 times and then decied i woudl jsut ask everyone
16:01:23 sean-k-mooney places where we are actully reading /proc or /sys are obvioulsy wrong and we shoudl fix the missing mocks
16:01:55 sean-k-mooney that what i recall fixing for arm or cygwin in the past
16:43:07 stephenfin left a comment on the change by mypy lets you configure the platform
16:43:11 stephenfin *but
17:29:27 melwitt cool thanks gmaan
17:32:32 melwitt ++ gibi I see it is merged now :)
17:53:37 melwitt dansmith: just checking, you aren't waiting on me for anything on the vtpm live migration series are you?
17:53:56 dansmith no, sorry I need to circle back
17:54:23 dansmith kinda was trying to get as much eventlet done before gibi left for two weeks, but also got roped into some glance stuff
17:54:43 melwitt ok no worries, I was second guessing myself :)
22:11:59 mikal sean-k-mooney: I realised this morning I was forgetting something last night. I think the next Nova patch would be to support secure TLS in the HTML5 SPICE client, but I won't look at that until Kolla is working. So probably no earlier than G?
#openstack-nova - 2025-08-02
02:12:26 opendevreview melanie witt proposed openstack/nova master: libvirt: Get info with abs path, rebase with rel path https://review.opendev.org/c/openstack/nova/+/955039
18:49:18 opendevreview Takashi Kajinami proposed openstack/nova master: Enable E711 consistently https://review.opendev.org/c/openstack/nova/+/956436
#openstack-nova - 2025-08-04
13:11:35 opendevreview Dmitriy Rabotyagov proposed openstack/nova master: Allow to perform parallel live migrations https://review.opendev.org/c/openstack/nova/+/955784
13:49:58 NicolaiRuckel I tried to implement some changes in Nova's libvirt.driver and now some test cases fail with "nova.exception.ObjectActionError: Object action obj_load_attr failed because: attribute system_metadata not lazy-loadable". Does anyone have an idea where to look for debugging? I couldn't figure out where this would be set yet.
#openstack-nova - 2025-08-05
02:56:18 cardoe Hey all. I've brought this spec up before and folks have said they're good with it. There's a number of operators that are patching the nova code with patches to achieve this. I'm trying to advocate for these downstream operators to engage more with upstream OpenStack projects with my TC member hat on. https://review.opendev.org/c/openstack/nova-specs/+/471815
02:56:48 cardoe We're now seeing associated projects (neutron) marking the patches as abandoned because they don't believe it'll go anywhere.
02:57:31 cardoe Please help me folks.
06:17:07 jkulik NicolaiRuckel: sounds to me like you're using system_metadata in your patches, but the object doesn't have that loaded - and can't load it later on. system_metadata would have to get queried out (or set, since we're talking about tests) when the Instance is fetched from the DB/created in the tests.
09:27:36 opendevreview Stephen Finucane proposed openstack/nova master: tests: Replace keystoneclient with keystoneauth1 https://review.opendev.org/c/openstack/nova/+/951744
09:27:38 NicolaiRuckel jkulik: The weird thing is that I didn't knowingly touch system_metadata at all.
09:42:20 jkulik NicolaiRuckel: then maybe your patch calls some function that does consume it? little hard to tell ;)
09:52:24 NicolaiRuckel What surprised me is that the tests (for example functional.libvirt.test_uefi:test_create_server) always had the assertion `self.assertIn('image_hw_machine_type', instance.system_metadata)` and used to pass but somehow I managed to make it not lazy-loadable anymore. Is there any documentation on how system_metadata gets set/defined?
09:53:39 jkulik afaik, there's just code.
09:54:10 NicolaiRuckel I was afraid that this would be the answer. :D
09:54:28 jssfr NicolaiRuckel, maybe you can link / paste the specific patch you're looking at?
09:59:06 NicolaiRuckel one second, I need to make the repository public first
10:05:52 NicolaiRuckel This seems to be the commit that breaks the test: https://gitlab.com/NicolaiRuckel/nova/-/commit/9d6e6f44d5129a9de3c7f4a636e82411a711e3e3
10:15:23 jkulik Your use of `objects.Intance` looks weird. If I understand it right, you're assigning the `uuid` to the class - not an individual Instance instance. Maybe that breaks stuff.
10:31:09 NicolaiRuckel That sounds reasonable. I'll look into that. Thanks!
11:24:37 darkhackernc https://bugs.launchpad.net/nova/+bug/2119126 team can someone look into this
11:32:29 mohsen__ cpu_dedicated_set = 18-35,54-71
11:32:29 mohsen__ cpu_shared_set = 0-17,36-53
11:32:29 mohsen__ [compute]
11:32:29 mohsen__ I have set the following configs in my nova compute nova.conf file:
11:32:29 mohsen__ hello everyone. I have an issue with resource tracking in openstack.
11:32:30 mohsen__ The issue is that the placement service periodically adds the specified set of dedicated cpus to the inventory as PCPU section, and after a while, it removes the PCPU section of the inventory unexpectedly. which results to not being able to delete instances and getting the following error:
11:32:30 mohsen__ and I enabled the NUMATopologyFilter and AggregateInstanceExtraSpecsFilter filters so that I can schedule cpu-pinned instances on my desired aggregate of compute hosts.
11:32:32 mohsen__ Error during ComputeManager.update_available_resource: nova.exception.ReshapeNeeded: Virt driver indicates that provider inventories need to be moved.
11:32:34 mohsen__ I appreciate your ideas in advance
11:57:24 sean-k-mooney mohsen__: is this an existign deployment with workload?
11:57:53 sean-k-mooney modifyign the legacy vcpu_pin_set and newer cpu_*_sets shoudl only be done on empty hosts
12:00:28 sean-k-mooney im not aware of a bug that would cause the issue you describe but it sound like the "reshape" code that is run when upgrading to a release that supprot pinned and unpined guests on the same host is trying to fix the allocations/inventories. i dont know what woudl cause the pcpu invetoies to be removed other hten perhaps if the resouce tracker was broken by vms running on the
12:00:30 sean-k-mooney wrong cores. that can happen if you defiend or modifed those values when vms were on the hosts
12:02:42 sean-k-mooney darkhackernc: if the compute service is down the instance is not expected to be manageable via the nova api
12:06:14 mohsen__ Thank you for your helpful response
12:06:14 mohsen__ sean-k-mooney: Yes. My OpenStack environment already has a couple of instances up and running on it.
12:13:16 sean-k-mooney darkhackernc: this looks like a masikari issue so i marked the bug as invliad for nova.
12:26:13 NicolaiRuckel jkulik: That really helped. I was able to fix the problem now.
12:31:37 jkulik NicolaiRuckel: nice!
12:36:21 opendevreview Lajos Katona proposed openstack/nova master: WIP Use SDK for Neutron https://review.opendev.org/c/openstack/nova/+/928022
13:09:25 mohsen__ sean-k-mooney: I migrated all the instances from one compute node to another computes. then reconfigured nova with the mentioned config above on the compute host where there aren't any instances no longer. then I ran "openstack resource provider inventory list <compute-host-uuid>" command and find out that the same issue still exists. what could be the root cause?
13:10:34 sean-k-mooney mohsen__: you have restared the compute agent on the host since it was drained?
13:11:49 mohsen__ sean-k-mooney: since I used kolla-ansible to reconfigure it, it has a handler which do the restart task after modification. I didn't do it manually but I can test it.
13:12:01 sean-k-mooney if so and the issue still happens i think your going to have to file a bug with some logs. i.e. the full error message or warning form the reouce tracker and or perodic task related to the createion or update of the resouce provider
13:12:44 sean-k-mooney mohsen__: you did the reconfiugre while there were isntances on the host correct
13:12:54 sean-k-mooney have you restarted it since it was empty
13:14:25 mohsen__ sean-k-mooney: I evacuated all the instances and then ran the kolla-ansible to reconfigure it. the restart task had been run after all the instances were evacuated.
13:18:04 mohsen__ sean-k-mooney: After evacuating all the instances and after reconfiguration, I manually restarted it and the issue still persist. sounds like there is no way unless reporting a bug🤔
13:18:15 sean-k-mooney ack, without inspecigng the logs and or error i cant really advise more. i likely wont have time to dig much deeper in the short term unfortunetly. i woudl suggeset filing a bug and trying to extract any relevent log messages (ideally at debug level) that are related to teh execution of the update_aviable_resouce provider perodic and the intiall startup of the agent related to
13:18:17 sean-k-mooney when it initally created teh RP invetories with the PCPUs inventory. you mentioned it initally was created and then lost correct? it would be good to try and capture the relevent logs showing both
13:21:16 mohsen__ sean-k-mooney: Thank you for your guidance
14:58:27 cardoe I know the nova meeting is coming up and I just want to ping on https://review.opendev.org/c/openstack/nova-specs/+/471815 I pinged earlier.
15:30:42 Uggla Nova meeting in ~30mn
16:01:39 opendevmeet The meeting name has been set to 'nova'
16:01:39 opendevmeet Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:39 opendevmeet Meeting started Tue Aug 5 16:01:39 2025 UTC and is due to finish in 60 minutes. The chair is Uggla. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:39 Uggla #startmeeting nova
16:01:51 Uggla Hello everyone
16:02:02 jssfr o/
16:02:04 jssfr NicolaiRuckel and me would like to bring up a topic in the "Open Discussion" slot
16:02:08 jssfr (jfyi)
16:02:29 fwiesel o/
16:02:44 Uggla jssfr, no pb but this week few people are available.
16:03:01 jssfr thanks for the heads up :)
16:03:08 gmaan o/
16:04:04 Uggla awaiting people to join, but I'm pretty sure we will not have quorum.
16:04:36 Uggla Please raise your hand for showing you are part of the meeting.
16:05:07 NicolaiRuckel o/

Earlier   Later