This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2040554 - netdev_dpdk logged "Failed to create memory pool for netdev with MTU 1500" even though MTUs of all DPDK NICs were configured as 9000.
Summary: netdev_dpdk logged "Failed to create memory pool for netdev with MTU 1500" ev...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-os-vif
Version: 13.0 (Queens)
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: Rajesh Tailor
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks: 2048574 2281859
TreeView+ depends on / blocked
 
Reported: 2022-01-14 04:32 UTC by Ryo Hayakawa
Modified: 2024-05-20 16:06 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2048574 2281859 (view as bug list)
Environment:
Last Closed: 2024-01-10 20:21:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1959586 0 None None None 2022-01-31 14:16:03 UTC
OpenStack gerrit 857868 0 None MERGED Move mtu update request into ovsdb transaction 2022-11-15 11:56:33 UTC
Red Hat Issue Tracker NFV-2398 0 None None None 2022-01-25 14:08:25 UTC
Red Hat Issue Tracker OSP-12131 0 None None None 2022-01-14 04:38:34 UTC
Red Hat Issue Tracker   OSP-18756 0 None None None 2024-01-10 20:21:08 UTC
Red Hat Issue Tracker OSP-18878 0 None None None 2022-11-15 13:04:10 UTC
Red Hat Issue Tracker OSP-31118 0 None None None 2024-01-10 20:42:17 UTC

Comment 13 smooney 2022-01-31 14:16:04 UTC
i have filed an upstream bug to track eventually optimising os-vif to set the port mtu atomically as part of the port creation to avoid this error message.
https://bugs.launchpad.net/os-vif/+bug/1959586

for now however I will not have time to work on this.


Note You need to log in before you can comment on or make changes to this bug.