RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2001792 - Unable to set ip address for the ovs-user-bridge
Summary: Unable to set ip address for the ovs-user-bridge
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Fernando F. Mancera
QA Contact: Matej Berezny
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-07 08:06 UTC by Karthik Sundaravel
Modified: 2022-11-08 11:15 UTC (History)
11 users (show)

Fixed In Version: NetworkManager-1.39.0-1.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-08 10:07:31 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-96376 0 None None None 2021-09-07 08:08:05 UTC
Red Hat Product Errata RHBA-2022:7680 0 None None None 2022-11-08 10:08:04 UTC
freedesktop.org Gitlab NetworkManager NetworkManager-ci merge_requests 1024 0 None merged ovs: modified @add_dpdk_port_with_mtu test to check for ip addr 2022-06-10 12:01:06 UTC
freedesktop.org Gitlab NetworkManager NetworkManager merge_requests 1169 0 None closed ovs, dpdk: ignore ovs-netdev tun interface 2022-06-10 12:01:02 UTC
freedesktop.org Gitlab NetworkManager NetworkManager merge_requests 1179 0 None closed ovs, dpdk: fix creating ovs-interface when the ovs-bridge is netdev 2022-06-10 12:00:56 UTC

Internal Links: 1645689

Description Karthik Sundaravel 2021-09-07 08:06:53 UTC 
Description of problem:

In a OVS-DPDK setup, using NM the ipaddress could not be configured on a ovs-user-bridge


Version-Release number of selected component (if applicable):
ovs 2.15-4, nmcli 1.30.0

How reproducible:

nmcli con add type ovs-bridge conn.interface ovsbridge0 con-name ovs-bridge0 ovs-bridge.datapath-type netdev
nmcli con add type ovs-port conn.interface dpdkbond0 conn.master ovsbridge0 con-name ovs-dpdkbond0 ovs-port.bond-mode balance-slb 
nmcli c add type ovs-port conn.interface ovsbridge-port0 master ovsbridge0 con-name ovs-port-br
nmcli c add type ovs-interface slave-type ovs-port conn.interface ovsbridge-port0 master ovs-port-br  con-name  ovs-if-br-house 802-3-ethernet.mtu 9000
nmcli con add type ovs-interface conn.interface iface0 conn.master dpdkbond0 con-name ovs-iface0 ovs-dpdk.devargs 000:18:00.2 ovs-interface.type dpdk 802-3-ethernet.mtu 9000
nmcli con add type ovs-interface conn.interface iface1 conn.master dpdkbond0 con-name ovs-iface1 ovs-dpdk.devargs 000:18:00.3 ovs-interface.type dpdk 802-3-ethernet.mtu 9000
sudo nmcli con modify ovs-if-br-house ipv4.method static ipv4.address 192.168.123.100/24



Actual results:
    [root@dell-r640-oss-03 ~]# ip a
	10: ovsbridge-port0: <BROADCAST,MULTICAST,PROMISC> mtu 9000 qdisc noop state DOWN group default qlen 1000
    link/ether 8a:32:ce:b4:76:1d brd ff:ff:ff:ff:ff:ff


Expected results:

Ip address shall be set on the ovs-user-bridge
Comment 1 Thomas Haller 2021-09-07 08:35:15 UTC 
Sidenote1: when reporting a bug against NetworkManager, always consider first to collect a complete level=TRACE log. Read https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/contrib/fedora/rpm/NetworkManager.conf#n28 for hints about that.





> nmcli con add type ovs-bridge conn.interface ovsbridge0 con-name ovs-bridge0 ovs-bridge.datapath-type netdev
> nmcli con add type ovs-port conn.interface dpdkbond0 conn.master ovsbridge0 con-name ovs-dpdkbond0 ovs-port.bond-mode balance-slb 
> nmcli c add type ovs-port conn.interface ovsbridge-port0 master ovsbridge0 con-name ovs-port-br
> nmcli c add type ovs-interface slave-type ovs-port conn.interface ovsbridge-port0 master ovs-port-br  con-name  ovs-if-br-house 802-3-ethernet.mtu 9000
> nmcli con add type ovs-interface conn.interface iface0 conn.master dpdkbond0 con-name ovs-iface0 ovs-dpdk.devargs 000:18:00.2 ovs-interface.type dpdk 802-3-ethernet.mtu 9000
> nmcli con add type ovs-interface conn.interface iface1 conn.master dpdkbond0 con-name ovs-iface1 ovs-dpdk.devargs 000:18:00.3 ovs-interface.type dpdk 802-3-ethernet.mtu 9000
> sudo nmcli con modify ovs-if-br-house ipv4.method static ipv4.address 192.168.123.100/24

First you create 6 profiles. These profiles are all set to autoconnect. If the conditions are suitable, then they will autoconnect right away. From the provided information it's not possible to say, but it's fair to assume that they did autoconnect.


the final `nmcli con modify` then modifies a profile that is already active. The modification of a profile that is currently active, does not affect the current configuration of the device. That would only happen after you (re)activate the profile the next time.


Please be aware of the difference between a connection profile (`nmcli connection`) and the runtime configuration/network interfaces (`nmcli device`).



From the provided information, it would seem the solution is to `nmcli connection up ovs-if-br-house` after modifying the profile. Or simply set all parameters during "add", like

  nmcli c add type ovs-interface slave-type ovs-port conn.interface ovsbridge-port0 master ovs-port-br  con-name  ovs-if-br-house 802-3-ethernet.mtu 9000 ipv4.method static ipv4.address 192.168.123.100/24



Does this help? If not, please provide a full logfile. Thank you.
Comment 3 Karthik Sundaravel 2021-09-13 06:01:34 UTC 
With the below commands, the IP is still not set. Attached the logs in comment#2

nmcli con add type ovs-bridge conn.interface ovsbridge0 con-name ovs-bridge0 ovs-bridge.datapath-type netdev
nmcli con add type ovs-port conn.interface dpdkbond0 conn.master ovsbridge0 con-name ovs-dpdkbond0 ovs-port.bond-mode balance-slb 
nmcli c add type ovs-port conn.interface ovsbridge-port0 master ovsbridge0 con-name ovs-port-br
nmcli c add type ovs-interface slave-type ovs-port conn.interface ovsbridge-port0 master ovs-port-br  con-name  ovs-if-br-house 802-3-ethernet.mtu 9000 ipv4.method static ipv4.address 192.168.123.100/24
nmcli con add type ovs-interface conn.interface iface0 conn.master dpdkbond0 con-name ovs-iface0 ovs-dpdk.devargs 000:18:00.2 ovs-interface.type dpdk 802-3-ethernet.mtu 9000
nmcli con add type ovs-interface conn.interface iface1 conn.master dpdkbond0 con-name ovs-iface1 ovs-dpdk.devargs 000:18:00.3 ovs-interface.type dpdk 802-3-ethernet.mtu 9000


[root@dell-r640-oss-03 ~]# ip a

12: ovsbridge-port0: <BROADCAST,MULTICAST,PROMISC> mtu 9000 qdisc noop state DOWN group default qlen 1000
    link/ether 2e:28:aa:b9:c5:41 brd ff:ff:ff:ff:ff:ff
Comment 7 Fernando F. Mancera 2022-03-30 15:54:57 UTC 
There are two problems when managing internal interfaces for a ovs-bridge with netdev datatype.

1. ovs-netdev interface is not being ignored by NetworkManager, this interface is for openvSwitch and no one should touch it. Fix (https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1169)

2. When attaching an internal interface to a ovs-bridge it is creating a tun device instead so NetworkManager is not noticing that the link is present and therefore not configuring the IP address. 

I am still investigating the problem 2.

Thanks,
Fernando.
Comment 10 Matej Berezny 2022-04-20 22:17:23 UTC 
Updated tests to check for such use-case as well (https://gitlab.freedesktop.org/NetworkManager/NetworkManager-ci/-/merge_requests/1024)
Comment 13 errata-xmlrpc 2022-11-08 10:07:31 UTC 
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 (NetworkManager bug fix and enhancement update), 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/RHBA-2022:7680
Note You need to log in before you can comment on or make changes to this bug.