Bug 2283465 - os-net-config silently fails for ovs_extra in ovs_user_bridge
Summary: os-net-config silently fails for ovs_extra in ovs_user_bridge
Keywords:
Status: CLOSED DUPLICATE of bug 2283464
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: os-net-config
Version: 17.1 (Wallaby)
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: RHOSP:NFV_Eng
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-05-27 11:19 UTC by Ella Shulman
Modified: 2024-05-28 12:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-05-28 12:45:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-32161 0 None None None 2024-05-27 11:24:10 UTC

Description Ella Shulman 2024-05-27 11:19:40 UTC
Description of problem:
when running os-net-config with the following configuration it silently fails to create br-dpdk0/1:
- type: ovs_user_bridge
  name: br-dpdk0
  mtu: 9000
  use_dhcp: false
  ovs_extra:
    - set Interface dpdk2 options:n_rxq_desc=2048
    - set Interface dpdk2 options:n_txq_desc=2048
  members:
    - type: ovs_dpdk_port
      rx_queue: 1
      name: dpdk2
      mtu: 9000
      members:
        - type: interface
          name: nic5

- type: ovs_user_bridge
  name: br-dpdk1
  mtu: 9000
  use_dhcp: false
  ovs_extra:
    - set Interface dpdk3 options:n_rxq_desc=2048
    - set Interface dpdk3 options:n_txq_desc=2048
  members:
    - type: ovs_dpdk_port
      rx_queue: 1
      name: dpdk3
      mtu: 9000
      members:
        - type: interface
          name: nic6

[root@compute-0 ~]# os-net-config -c /etc/os-net-config/config.yaml -m /etc/os-net-config/mapping.yaml
[root@compute-0 ~]# ip a | grep dpdk
[root@compute-0 ~]#


although is is matching documentation, only when changing to the following config it is creating the expected bridges with the extra configuration:
- type: ovs_user_bridge
  name: br-dpdk0
  mtu: 9000
  use_dhcp: false
  members:
    - type: ovs_dpdk_port
      ovs_extra:
        - set Interface dpdk2 options:n_rxq_desc=2048
        - set Interface dpdk2 options:n_txq_desc=2048
      rx_queue: 1
      name: dpdk2
      mtu: 9000
      members:
        - type: interface
          name: nic5

- type: ovs_user_bridge
  name: br-dpdk1
  mtu: 9000
  use_dhcp: false
  members:
    - type: ovs_dpdk_port
      ovs_extra:
        - set Interface dpdk3 options:n_rxq_desc=2048
        - set Interface dpdk3 options:n_txq_desc=2048
      rx_queue: 1
      name: dpdk3
      mtu: 9000
      members:
        - type: interface
          name: nic6

[root@compute-0 ~]# os-net-config -c /etc/os-net-config/config.yaml -m /etc/os-net-config/mapping.yaml
[root@compute-0 ~]# ip a | grep dpdk
61: br-dpdk0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 9000 qdisc fq_codel state UNKNOWN group default qlen 1000
62: br-dpdk1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 9000 qdisc fq_codel state UNKNOWN group default qlen 1000
[root@compute-0 ~]# ovs-vsctl --columns=options list interface dpdk2
options : {dpdk-devargs="0000:82:00.2", n_rxq="1", n_rxq_desc="2048", n_txq_desc="2048"}
[root@compute-0 ~]# ovs-vsctl --columns=options list interface dpdk3
options : {dpdk-devargs="0000:82:00.3", n_rxq="1", n_rxq_desc="2048", n_txq_desc="2048"}


Version-Release number of selected component (if applicable):
[root@compute-0 ~]# os-net-config --version
14.2.1


How reproducible:
100%

Steps to Reproduce:
1. use the first configuration mentioned to run os-net-config
2. check if bridges are created
3.

Actual results:
os-net-config silently fails to create the expected bridges

Expected results:
bridges either created of failure doesn't go silently 

Additional info:
created the following lunchpad bug for the upstream docs https://bugs.launchpad.net/os-net-config/+bug/2067263

Comment 1 Juan Pablo Marti 2024-05-28 12:45:13 UTC

*** This bug has been marked as a duplicate of bug 2283464 ***


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