April 2025 - openstack-discuss - lists.openstack.org

[neutron] Neutron sriov vf-lag port binding
by Serhat Rıfat Demircan 07 Apr '25

07 Apr '25

Hello everyone, I have tested sriov with Connectx-5 cards, it works well but I also want to try ovs with hardware offload feature. I believe I have properly configured pf, vfs and bonding :). PF’s are working in switchdev mode (I have followed stackhpcs article[1]). Unfortunately, I see port binding errors when creating instances. I have created a vlan provider network and a port with vnic_type=direct under that network. I am trying to create instance with that port. nova-compute.log > 2025-04-04 17:37:28.014 7 ERROR nova.compute.manager [instance: > bf8408e8-20a9-4963-9e50-033e54aba9fe] nova.exception.PortBindingFailed: > Binding failed for port 6cbd8181-5707-4349-9fa0-c35e7370bfcd, please check > neutron logs for more information. neutron-server.log > 025-04-04 17:37:27.000 25 DEBUG > neutron.plugins.ml2.drivers.mech_sriov.mech_driver.mech_driver > [req-ff074be0-e410-4df8-8938-7e2b59a84bfd > req-d9bffb08-7e74-4976-b3ae-8cb544ec71f5 fbbdf9e30cad498180c3b637d1bba6d9 > 3e7a1867f1c24a158b4bb2d2f3f68b9c - - default default] Refusing to bind due > to unsupported vnic_type: direct with switchdev capability bind_port > /var/lib/kolla/venv/lib/python3.10/site-packages/neutron/plugins/ml2/drivers/mech_sriov/mech_driver/mech_driver.py:130 neutron/plugins/ml2/drivers/mech_sriov/mech_driver/mech_driver.py > if (vnic_type == portbindings.VNIC_DIRECT and > 'switchdev' in capabilities): > LOG.debug("Refusing to bind due to unsupported vnic_type: %s " > "with switchdev capability", > portbindings.VNIC_DIRECT) nova.conf > [pci] > passthrough_whitelist = [{"physical_network": "physnet5", "devname": > "ens10f0"},{"physical_network": "physnet6", "devname": "ens10f1"}] [sriov_nic] physical_device_mappings = physnet5:ens10f0,physnet6:ens10f1 Is vnic_type=direct wrong if switchdev in capabilities or is this a configuration issue? Environment: Openstack version: Caracal Operating System: Ubuntu 22.04 Thanks, Serhat [1] - https://www.stackhpc.com/vflag-kayobe.html

3 3

[Octavia][Load Balancer][2023.1] Amphora Fails Health Check – “No Route to Host” & Timeout Errors
by Thamanna Farhath 07 Apr '25

07 Apr '25

Hi OpenStack Community, I am currently facing an issue with the Load Balancer (Octavia) service in my OpenStack deployment and would appreciate your guidance or suggestions on how to troubleshoot and resolve it. Environment Details: OpenStack Version: 2023.1 (Antelope) Operating System: Ubuntu 22.04 Octavia Backend: Amphora Network Type: VXLAN Deployment Tool: Kolla Ansible Issue Summary: After creating a Load Balancer, the Amphora instance is successfully launched. However, approximately 18 minutes later, the Load Balancer transitions to an ERROR state. Error Observed: octavia.common.exceptions.ComputeWaitTimeoutException: Waiting for compute id a222527f-8336-4fb1-8e9e-0e3ac6e8d580 to go active timeout. octavia.amphorae.driver_exceptions.exceptions.AmpConnectionRetry: Could not connect to amphora, exception caught: HTTPSConnectionPool(host='192.168.200.247', port=9443): Max retries exceeded with url: // (Caused by NewConnectionError: Failed to establish a new connection: [Errno 113] No route to host) What I’ve Tried: Created a VXLAN-based internal network: openstack subnet create --network octavia-mgmt-net --subnet-range 192.168.200.0/24 octavia-mgmt-subnet openstack router create octavia-router openstack router add subnet octavia-router octavia-mgmt-subnet openstack router set octavia-router --external-gateway <public-network-id> Manually configured OVS interface: ovs-vsctl add-port br-int octavia-mgmt -- set interface octavia-mgmt type=internal ip addr add 192.168.200.1/24 dev octavia-mgmt ip link set octavia-mgmt up Security groups are open (allowing all ingress and egress). Verified OVS bridge setup – interface appears correctly on br-int. Behavior Noticed: Amphora instance gets created but fails to communicate with the controller after a while,so health checks fails. The controller cannot reach the Amphora management IP (192.168.200.x). Logs show heartbeat/connection issues (No route to host, timeouts). Request for Help: I would appreciate any of the following: Suggestions to verify if the management network is properly routed from controller to Amphora. Best practices for setting up the Octavia management network using VXLAN. Troubleshooting steps for verifying health manager connectivity to Amphora. Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender. E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."

2 1

[neutron] Bug deputy week 14 (March 31 - April 6)
by Rodolfo Alonso Hernandez 07 Apr '25

07 Apr '25

Hello Neutrinos: This is the bug list of week 14 (March 31 - April 6). HIGH: * https://bugs.launchpad.net/neutron/+bug/2105977 Random error in ``test_packets_of_any_connection_state_can_reach_dest`` test. Not assigned yet. * https://bugs.launchpad.net/neutron/+bug/2105502 service role permissions not enough for octavia allowed address pair driver. Assigned. Two patches proposed: https://review.opendev.org/c/openstack/neutron/+/861169 and https://review.opendev.org/c/openstack/neutron/+/945329. MEDIUM: * https://bugs.launchpad.net/neutron/+bug/2106231 [OVN][QoS] The Logical_Swith_Port QoS options are removed when the port is updated. Assigned. Patch proposed: https://review.opendev.org/c/openstack/neutron/+/946542 RFE: * https://bugs.launchpad.net/neutron/+bug/2105855 [RFE] VXLAN physical_networks or new network type Regards.

1 0

[manila]NFS-Ganesha exports
by Mikhail Okhrimenko 07 Apr '25

07 Apr '25

Hello community, Trying to setup the Manila version of Caracal with NFS-Ganesha backend. Ganesha version 4.0 is deployed using ceph orch in a ceph cluster version 17. Backend configuration in manila.conf [ganesha_nfs] driver_handles_share_servers = False share_backend_name = ganesha_nfs Share_driver = manila.share.drivers.cephfs.driver.CephFSDriver cephfs_protocol_helper_type = NFS cephfs_conf_path = /etc/ceph/ceph.conf cephfs_auth_id = manila cephfs_cluster_name = ceph cephfs_filesystem_name = {{ cephfs_filesystem_name }} cephfs_nfs_cluster_id = {{ cephfs_nfs_cluster_id }} I see the subvolume being created in ceph ceph fs subvolume ls <volume_name> but no export ceph nfs export ls <cluster_id> what am I doing wrong? what am I missing? in the manila-share logs I see a request to create a subvolume, but I don't see a request to create an export, for some reason manila doesn't even try to create an export

3 6

bug report
by Xavier Benjamin 05 Apr '25

05 Apr '25

whenever i try to connect to trove pts servers it would usually say fails to authenticate or something. Can you fix that please?

2 2

[blazar] Blazar-dashboard contains non-free files (ie: minified Javascripts)
by Thomas Goirand 05 Apr '25

05 Apr '25

Hi, I've been trying to package Blazar, all is already in Debian, but I can't get blazar-dashboard in, because upstream source contains non-free files. Namely: https://github.com/openstack/blazar-dashboard/blob/master/blazar_dashboard/… is a minifed version of a much more complex package: https://github.com/apexcharts/apexcharts.js/tree/v3.31.0 Reminder: minified Javascripts are considered by most distributions (this includes Red Hat, Ubuntu, and in my case Debian) as non-free files that cannot be shipped in the distribution without the underlying source code, and packages must build from the not minified version. Could the Blazar team work on un-vendoring apexcharts.min.js, possibly removing it completely, or replacing it with a source-full version? Cheers, Thomas Goirand (zigo)

4 5

[all][tc][ptg] OpenStack TC Flamingo PTG Schedule, Etherpad and Weekly Meeting updates
by Goutham Pacha Ravi 05 Apr '25

05 Apr '25

Hello Stackers, The OpenStack Technical Committee has scheduled discussions at the following time slots next week: - April 7 2025: 1300 UTC to 1500 UTC - April 11 2025: 1500 UTC to 1700 UTC You can find the discussion times and meeting details on this etherpad: https://etherpad.opendev.org/p/apr2025-ptg-os-tc Of special importance is the TC/Community Leaders forum session on 2025-04-11 at 1500 UTC. The list of topics for this forum session can expand over the week. If you're a maintainer on any OpenStack repository, or an aspiring maintainer, please do join us there. The etherpad, the schedule and a link to the meeting room can also be found on the PTG website [1]. At this time, if you'd like to add more topics, please reach out to me, or chime-in on the #openstack-tc channel on OFTC. In lieu of the PTG, we'll not have the regular weekly IRC meeting next week. The IRC meeting will be back on 2025-04-15 [2]. Thank you, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] https://ptg.opendev.org/ptg.html [2] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee

1 0

[nova] vGPU not attached to VM using Cyborg with OpenStack Caracal
by ts.jung＠okestro.com 04 Apr '25

04 Apr '25

Hello, I'm facing an issue with vGPU assignment through Cyborg in OpenStack Caracal. Although Cyborg reports that the ARQ is bound successfully, the vGPU device is not attached to the VM in Nova. - Environment: OS: Ubuntu 22.04.3 LTS Kernel: 5.15.0-78-generic Nova API: 29.2.0 Cyborg API: 14.1.0.dev1 GPU: NVIDIA A100 PCIe 40GB - Device Profile: openstack accelerator device profile list +--------------------------------------+------+-----------------------------------------------------------------------------+ | uuid | name | groups | +--------------------------------------+------+-----------------------------------------------------------------------------+ | 8425925f-7a3c-4336-8a1c-270f481a28ae | vgpu | [{'resources:VGPU': '1', 'trait:CUSTOM_NVIDIA_20F1_A100_1_5C': 'required'}] | +--------------------------------------+------+-----------------------------------------------------------------------------+ Flavor: openstack flavor show vgpu --column properties +------------+-----------------------------+ | Field | Value | +------------+-----------------------------+ | properties | accel:device_profile='vgpu' | +------------+-----------------------------+ Result After VM Creation: openstack accelerator arq list +--------------------------------------+------+-----------------------------------------------------------------------------+ | uuid | name | groups | +--------------------------------------+------+-----------------------------------------------------------------------------+ | 8425925f-7a3c-4336-8a1c-270f481a28ae | vgpu | [{'resources:VGPU': '1', 'trait:CUSTOM_NVIDIA_20F1_A100_1_5C': 'required'}] | +--------------------------------------+------+-----------------------------------------------------------------------------+ ARQ shows Bound with an attach_handle_type of MDEV, but the GPU device is not visible inside the VM. mdevctl list # Shows UUID and mdev type virsh dumpxml instance-xxxx # No mdev device listed Logs (Summary) Cyborg logs indicate ARQ binding was successful and attach handle allocated (MDEV). Nova-compute logs show: Ignoring accelerator requests for instance ... Supported Attach handle types: {'PCI'}. But got these unsupported types: {'MDEV'}. Question. Is there something I’m missing in the integration between Cyborg and Nova for MDEV attach_handle_type? It seems like Nova is not yet supporting MDEV, even though Cyborg bound the ARQ correctly. Any suggestions or known workarounds would be appreciated. Thank you!

2 1

[i18n] i18n SIG - 2025.2 (Flamingo) Virtual PTG Schedule
by Ian Y. Choi 04 Apr '25

04 Apr '25

Hi, I would like to share the i18n SIG schedule for the upcoming PTG. Dates and locations are: • April 9th, 1400 ~ 1500 UTC at kilo-WedB2 (Please find https://ptg.opendev.org/ptg.html for real time information) Note that I18n PTG Etherpad link is: https://etherpad.opendev.org/p/apr2025-ptg-i18n . Looking forward to the meeting and interactions during the PTG! Thank you, /Ian

1 0

[Octavia] Active/Standby with AZ
by Vincent Godin 04 Apr '25

04 Apr '25

Hello, To address the Octavia and Cinder backend mismatch, I'm going to temporarily create a Cinder backend stretched across all three AZs. Now I have another question: is it possible to use Octavia AZs to set up an active/standby load balancer so that the active load balancer is on one AZ and the standby load balancer is on another one ? Of course, the network is stretched across all three AZs, so the VRRP mechanism is possible. Vincent

3 2