Earlier  
Posted Nick Remark
#openstack-nova - 2026-08-03
16:35:27 opendevmeet Meeting ended Mon Aug 3 16:35:27 2026 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
16:35:27 Uggla #endmeeting
16:35:36 elodilles thanks o/
16:35:51 Leo[m] thank you o/
16:35:52 lajoskatona o/
16:36:05 tkajinam thanks
18:11:11 opendevreview Goutham Pacha Ravi proposed openstack/nova master: Extract share management from ComputeManager https://review.opendev.org/c/openstack/nova/+/999349
18:11:11 opendevreview Goutham Pacha Ravi proposed openstack/nova master: Fix deny_share host locality for NFS https://review.opendev.org/c/openstack/nova/+/998752
18:11:12 opendevreview Goutham Pacha Ravi proposed openstack/nova master: Support cold migration with virtiofs shares https://review.opendev.org/c/openstack/nova/+/989633
19:54:21 clif I'm trying to run py3 tox target locally on latest master but I'm getting a lot (217) failed unit tests. Is there something I'm supposed to do besides git clone and then tox -epy3?
19:54:38 clif I've made sure I have a completely clean tree
19:55:02 clif One message I'm seeing a lot of in failures: "Exception: This test invokes builtins.open on /sys/module/kvm_amd/parameters/sev. It is bad, you should mock it."
20:22:46 dansmith clif: are you on something other than linux? although from the look of that, I'd guess maybe even being on linux but without SEV support you might hit that
20:22:50 dansmith I'd think the latter would affect CI though
20:23:36 clif linux, fedora specifically
20:24:33 dansmith ack, should work of course.. maybe hit tkajinam knows if something merged recently for the CC stuff that might be related
20:25:33 clif Is there a way to turn off or skip sev specific tests? I'm not familiar with the feature, I *am* running an AMD cpu
20:25:57 clif but a desktop chip, not EPYC
20:28:06 JayF I don't know if practices in Nova are different, but we'd also generally treat a non-mocked read of stuff outta /sys (or proc, or dev, or anything-local) in unit tests as a bug
20:28:10 JayF (in Ironic)
20:37:10 dansmith yep for sure, hence why I'm suggesting it might be a recent merge and the CC people might know of something obvious
23:20:58 tkajinam clif, which commit hash are you using ?
23:27:09 clif 39dc667a1f9a7c12814f5892b900462560b1a229 as of last attemp
23:35:42 opendevreview Seyeong Kim proposed openstack/nova stable/2026.1: Restore 'fork' start method for daemon mode on Python 3.14 https://review.opendev.org/c/openstack/nova/+/999667
23:36:09 opendevreview Seyeong Kim proposed openstack/nova stable/2025.2: Restore 'fork' start method for daemon mode on Python 3.14 https://review.opendev.org/c/openstack/nova/+/999668
23:36:53 opendevreview Seyeong Kim proposed openstack/nova stable/2025.1: Restore 'fork' start method for daemon mode on Python 3.14 https://review.opendev.org/c/openstack/nova/+/999669
#openstack-nova - 2026-08-04
00:20:10 opendevreview Seyeong Kim proposed openstack/nova stable/2026.1: Restore 'fork' start method for daemon mode on Python 3.14 https://review.opendev.org/c/openstack/nova/+/999667
00:20:18 opendevreview Seyeong Kim proposed openstack/nova stable/2025.2: Restore 'fork' start method for daemon mode on Python 3.14 https://review.opendev.org/c/openstack/nova/+/999668
00:20:25 opendevreview Seyeong Kim proposed openstack/nova stable/2025.1: Restore 'fork' start method for daemon mode on Python 3.14 https://review.opendev.org/c/openstack/nova/+/999669
00:41:00 opendevreview Seyeong Kim proposed openstack/nova stable/2026.1: Restore 'fork' start method for daemon mode on Python 3.14 https://review.opendev.org/c/openstack/nova/+/999667
00:41:13 opendevreview Seyeong Kim proposed openstack/nova stable/2025.2: Restore 'fork' start method for daemon mode on Python 3.14 https://review.opendev.org/c/openstack/nova/+/999668
00:41:21 opendevreview Seyeong Kim proposed openstack/nova stable/2025.1: Restore 'fork' start method for daemon mode on Python 3.14 https://review.opendev.org/c/openstack/nova/+/999669
00:41:49 opendevreview Seyeong Kim proposed openstack/nova master: Avoid serializing orphaned instance in log https://review.opendev.org/c/openstack/nova/+/992574
00:42:44 opendevreview Seyeong Kim proposed openstack/nova master: Avoid serializing orphaned instance in log https://review.opendev.org/c/openstack/nova/+/992574
00:46:14 opendevreview Seyeong Kim proposed openstack/nova master: Avoid serializing orphaned instance in log https://review.opendev.org/c/openstack/nova/+/992574
00:47:03 opendevreview Seyeong Kim proposed openstack/nova stable/2026.1: Restore 'fork' start method for daemon mode on Python 3.14 https://review.opendev.org/c/openstack/nova/+/999667
00:47:04 opendevreview Seyeong Kim proposed openstack/nova stable/2025.2: Restore 'fork' start method for daemon mode on Python 3.14 https://review.opendev.org/c/openstack/nova/+/999668
00:47:11 opendevreview Seyeong Kim proposed openstack/nova stable/2025.1: Restore 'fork' start method for daemon mode on Python 3.14 https://review.opendev.org/c/openstack/nova/+/999669
07:48:26 opendevreview Joan Gilabert proposed openstack/nova master: Add libvirt driver MDEV ARQ support for Cyborg https://review.opendev.org/c/openstack/nova/+/995840
07:48:26 opendevreview Joan Gilabert proposed openstack/nova master: Report OWNER_NOVA trait on resource providers https://review.opendev.org/c/openstack/nova/+/994299
08:07:33 opendevreview Joan Gilabert proposed openstack/nova master: Report OWNER_NOVA trait on resource providers https://review.opendev.org/c/openstack/nova/+/994299
08:07:34 opendevreview Joan Gilabert proposed openstack/nova master: Add libvirt driver MDEV ARQ support for Cyborg https://review.opendev.org/c/openstack/nova/+/995840
08:36:44 gibi bauzas: could you look back at you gpu doc patch we have some question there https://review.opendev.org/c/openstack/nova/+/999607
08:37:52 bauzas gibi: you're making a great point, this is not only for vfio-mdev but also for vfio-pci variant driver migrations
08:38:33 bauzas I'll amend the doc patch to mention vfio-pci too
09:19:31 opendevreview Sylvain Bauza proposed openstack/nova master: doc: Document postcopy incompatibility with vGPU live migration https://review.opendev.org/c/openstack/nova/+/999607
09:45:16 sean-k-mooney bauzas: you or cursor added "Co-authored-by: Cursor <cursoragent@cursor.com>" that wrong, but otherwise the commit looks fine to me
09:45:27 bauzas doh
09:45:35 bauzas I'll change that
09:46:28 opendevreview Sylvain Bauza proposed openstack/nova master: doc: Document postcopy incompatibility with vGPU live migration https://review.opendev.org/c/openstack/nova/+/999607
09:46:46 sean-k-mooney thanks
09:48:35 sean-k-mooney bauzas: speaking of gpus i have some cyborg related gpu patches that i would like to progress on the nova side.
09:49:09 sean-k-mooney if i can find them again :)
09:49:36 sean-k-mooney ah yes https://review.opendev.org/q/topic:%22bp/support-vfio-variant-driver-managed-mode-via-cyborg%22
09:49:52 bauzas no promises I can review them but I'll try
09:49:55 sean-k-mooney im going to be rebasing those later today
09:51:03 sean-k-mooney i basically have 6 patches in nova that i want to try an land this cycle, those 2 for vfio-varitnt driver suport via cybrog
09:51:25 sean-k-mooney 2 patches that jgilaber is creating for time sliced gpus (vfio-mdev)
09:51:38 sean-k-mooney and then 2 for ironci start up time
09:52:11 sean-k-mooney if you have time to look at any of those that woudl be great if not i will try and follow up with other to land them in time
09:52:12 bauzas okay, I'm pretty busy before my two-week PTO which will be on next Tuesday but I'll definitely try
09:52:29 bauzas thanks for the effortd
09:54:41 sean-k-mooney as an fyi we are also seting up devstack based nightly ci to test as much of this as possible with real hardware internally (we cant currentl report the logs externally due to internal info in the job) but on the cybrog side we have been developing a kernel module to emulsate gpus, nvme devices and eventually nics
09:55:07 sean-k-mooney so we will have a mix of 1st party ci and internal coverage in the next few months for this
09:56:38 sean-k-mooney joan will be on pto startign tomorrow for the next 3 weeks so we likey will continue the 1st party testign efforts into the start of next cycle
09:56:40 sean-k-mooney https://review.opendev.org/q/topic:%22cyborg-vgpu-support%22
09:56:51 sean-k-mooney that is the timesliced cybrog vgpu nova patch series
09:57:09 sean-k-mooney again just general context for everyone
10:22:16 opendevreview Kamil Sambor proposed openstack/nova master: Replace StaticallyDelayingWrapper with futurist DelayingExecutor https://review.opendev.org/c/openstack/nova/+/997410
11:05:44 opendevreview Balazs Gibizer proposed openstack/nova master: DNM: check tempest for instability https://review.opendev.org/c/openstack/nova/+/999378
11:46:39 opendevreview Stephen Finucane proposed openstack/nova master: Add ruff-check https://review.opendev.org/c/openstack/nova/+/974441
11:46:39 opendevreview Stephen Finucane proposed openstack/nova master: Replace use of datetime.timezone.UTC https://review.opendev.org/c/openstack/nova/+/989515
11:46:40 opendevreview Stephen Finucane proposed openstack/nova master: trivial: Fix outstanding flake8 issues https://review.opendev.org/c/openstack/nova/+/999714
13:07:54 tkajinam clif, hm the failure is not reproduced in my local env (and in CI, either)
13:08:25 tkajinam clif, do you mind reporting a bug with a few examples of the failing tests ?
13:56:00 sean-k-mooney tkajinam: are you runing on an mad cpu
13:56:04 sean-k-mooney *amd
14:00:37 sean-k-mooney im running the test now locally to confirm but i also didnt see the failures on my intel cpu
14:01:37 sean-k-mooney and if i cat the file
14:01:39 sean-k-mooney [15:01:17]> cat /sys/module/kvm_amd/parameters/sev
14:01:41 sean-k-mooney [bat error]: '/sys/module/kvm_amd/parameters/sev': No such file or directory (os error 2)
14:02:20 sean-k-mooney i get an error so it would fail on this laptop if the mock didnt work
14:02:22 sean-k-mooney Ran: 17007 tests in 214.5597 sec.
14:02:24 sean-k-mooney - Passed: 16940
14:02:26 sean-k-mooney - Skipped: 65
14:02:28 sean-k-mooney - Expected Fail: 2
14:02:30 sean-k-mooney - Unexpected Success: 0
14:02:32 sean-k-mooney - Failed: 0
14:02:34 sean-k-mooney Sum of execute time for each test: 3262.8758 sec.
14:02:43 sean-k-mooney ill try recreating the env just to make sure but on py 3.14 it seams to be working
14:03:29 sean-k-mooney oh
14:03:45 sean-k-mooney maybe this only fails on amd cpus
14:04:06 sean-k-mooney because we may be skiping earlier on intel before we try and read the path
14:10:03 dansmith succeeds on macos arm64, FWIW, so it'd have to be AMD_specific
14:10:04 frickler I have an VM on amd where I can reproduce this, I can give you access if that helps
14:16:10 frickler does this imply that all of our zuul nodes are on intel?
14:17:10 frickler oh, or does it need kvm enabled? maybe we can try running a tox job on a big kvm node
14:19:23 sean-k-mooney frickler: thre are a couple of diffent checks for sev supprot so i would not be surprised if we side step the fialign check on the amd vms as well
14:19:47 sean-k-mooney from pi
14:19:49 sean-k-mooney I found no unpatched access to /sys/module/kvm_amd/parameters/sev in the current checkout.

Earlier   Later