Bug 1883554
| Summary: | [RFE] `socket` PCI NUMA affinity policy | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Erwan Gallen <egallen> | |
| Component: | openstack-nova | Assignee: | Artom Lifshitz <alifshit> | |
| Status: | CLOSED ERRATA | QA Contact: | James Parker <jparker> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | high | |||
| Version: | 17.0 (Wallaby) | CC: | alifshit, cfontain, chrisw, dasmith, eglynn, hakhande, igallagh, jelynch, jgrosso, jhakimra, jparker, jschluet, kchamart, mariel, mburns, nlevinki, oblaut, pgrist, sbauza, scohen, sgordon, smooney, spower, stephenfin, supadhya, vromanso, yrachman | |
| Target Milestone: | ga | Keywords: | FutureFeature, Patch, Triaged | |
| Target Release: | 17.1 | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | openstack-nova-23.2.3-1.20230518170958.7e3a8a1.el9ost | Doc Type: | Enhancement | |
| Doc Text: |
With this update, a RHOSP administrator can create a flavor that has a `socket` PCI NUMA affinity policy. You can use this policy to create an instance that requests a PCI device only when at least one of the instance NUMA nodes has affinity with a NUMA node in the same host socket as the PCI device.
|
Story Points: | --- | |
| Clone Of: | 1827283 | |||
| : | 1905209 (view as bug list) | Environment: | ||
| Last Closed: | 2023-08-16 01:09:23 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | Wallaby | |
| Embargoed: | ||||
| Bug Depends On: | 1827283 | |||
| Bug Blocks: | 1820742, 1880120, 1905209 | |||
Could you provide a DB dump of the deployment? Specifically, I'm looking for the the numa_topology JSON blob column in the compute_node row. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2023:4577 |
I wonder if you're seeing: LOG.warning('This host appears to have multiple sockets per ' 'NUMA node. The `socket` PCI NUMA affinity ' 'will not be supported.') In the logs at libvirt drive init time, given that this is an AMD EPYC system. It would make sense for `socket` to not work on these, but we should definitely handle the failure better. If you do see it, I think we can verify the feature, but file a new bug to track the more graceful failure.