Bug 2001792
| Summary: | Unable to set ip address for the ovs-user-bridge | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Karthik Sundaravel <ksundara> |
| Component: | NetworkManager | Assignee: | Fernando F. Mancera <ferferna> |
| Status: | CLOSED ERRATA | QA Contact: | Matej Berezny <mberezny> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.4 | CC: | acabral, bgalvani, ferferna, fge, lrintel, mberezny, rkhan, sukulkar, thaller, till, vbenes |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | NetworkManager-1.39.0-1.el8 | Doc Type: | No Doc Update |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-11-08 10:07:31 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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. 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 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. Updated tests to check for such use-case as well (https://gitlab.freedesktop.org/NetworkManager/NetworkManager-ci/-/merge_requests/1024) 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 |
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