Bug 1807726
Summary: | Cannot set un-default mtu on ovs interface | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Mingyu Shi <mshi> | |
Component: | nmstate | Assignee: | Gris Ge <fge> | |
Status: | CLOSED ERRATA | QA Contact: | Mingyu Shi <mshi> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 8.2 | CC: | bgalvani, dholler, ferferna, fge, jiji, jishi, network-qe, till | |
Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
|
Target Release: | 8.3 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | nmstate-0.3.2-1.el8 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1820052 (view as bug list) | Environment: | ||
Last Closed: | 2020-11-04 03:08:25 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: | ||||
Bug Depends On: | 1820052 | |||
Bug Blocks: |
Comment 1
Gris Ge
2020-02-27 06:22:28 UTC
(In reply to Gris Ge from comment #1) > Hi Beniamino, > > Does NetworkManager OVS support MTU changes? Not yet, I'll implement it. Dominik, is this a problem for RHV? (In reply to Till Maas from comment #3) > Dominik, is this a problem for RHV? Not yet, RHV does not yet use nmstate/NetworkManager for OVS. I will come back if this bug becomes relevant for RHV. This is reported against nmstate but fixed in NetworkManager - is anything needed for this in Nmstate? (In reply to Till Maas from comment #6) > This is reported against nmstate but fixed in NetworkManager - is anything > needed for this in Nmstate? I intend to keep this bug as tracker of nmstate on this issue. Ideally, nothing need to be done by nmstate. Fixed in NM by: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/2da77547bafedd352d5c40f66ccd365c454c30d4 Gris, should I switch component of this bz to NM, or clone it? (In reply to Beniamino Galvani from comment #8) > Fixed in NM by: > > https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/ > 2da77547bafedd352d5c40f66ccd365c454c30d4 > > Gris, should I switch component of this bz to NM, or clone it? I don't think you need bz in NM as NM will rebase in 8.3. If you want it anyway, clone it. Okay, I'm going to clone it so that it gets verified by NM QA. It would be nice to have an integration test for this in nmstate. Issue: https://github.com/nmstate/nmstate/issues/1048 Verified with versions: nmstate-0.3.2-6.el8.noarch NetworkManager-1.26.0-0.2.el8.x86_64 DISTRO=RHEL-8.3.0-20200701.2 Linux ibm-x3650m4-01-vm-05.ibm2.lab.eng.bos.redhat.com 4.18.0-221.el8.x86_64 #1 SMP Thu Jun 25 20:58:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux [20:14:40@ibm-x3650m4-01-vm-05 ~]0# cat mtu-ovs.yaml interfaces: - name: ovs0 type: ovs-interface state: up mtu: 9600 - name: ovs-br0 type: ovs-bridge state: up bridge: port: - name: ovs0 [20:15:06@ibm-x3650m4-01-vm-05 ~]0# nmstatectl set mtu-ovs.yaml 2020-07-06 20:15:10,542 root DEBUG Async action: Create checkpoint started 2020-07-06 20:15:10,548 root DEBUG Checkpoint None created for all devices 2020-07-06 20:15:10,548 root DEBUG Async action: Create checkpoint finished 2020-07-06 20:15:10,552 root DEBUG Async action: Add profile: ovs0 started 2020-07-06 20:15:10,553 root DEBUG Async action: Add profile: ovs-br0 started 2020-07-06 20:15:10,554 root DEBUG Async action: Add profile: ovs-port-ovs0 started 2020-07-06 20:15:10,567 root DEBUG Async action: Add profile: ovs0 finished 2020-07-06 20:15:10,567 root DEBUG Async action: Add profile: ovs-br0 finished 2020-07-06 20:15:10,568 root DEBUG Async action: Add profile: ovs-port-ovs0 finished 2020-07-06 20:15:10,568 root DEBUG Async action: Activate profile: ovs-br0 started 2020-07-06 20:15:10,580 root DEBUG Connection activation initiated: dev=ovs-br0, con-state=<enum NM_ACTIVE_CONNECTION_STATE_ACTIVATING of type NM.ActiveConnectionState> 2020-07-06 20:15:10,607 root DEBUG Connection activation succeeded: dev=ovs-br0, con-state=<enum NM_ACTIVE_CONNECTION_STATE_ACTIVATING of type NM.ActiveConnectionState>, dev-state=<enum NM_DEVICE_STATE_IP_CONFIG of type NM.DeviceState>, state-flags=<flags NM_ACTIVATION_STATE_FLAG_IS_MASTER | NM_ACTIVATION_STATE_FLAG_LAYER2_READY | NM_ACTIVATION_STATE_FLAG_MASTER_HAS_SLAVES of type NM.ActivationStateFlags> 2020-07-06 20:15:10,608 root DEBUG Async action: Activate profile: ovs-br0 finished 2020-07-06 20:15:10,608 root DEBUG Async action: Activate profile: ovs-port-ovs0 started 2020-07-06 20:15:10,643 root DEBUG Connection activation initiated: dev=ovs-port-ovs0, con-state=<enum NM_ACTIVE_CONNECTION_STATE_ACTIVATING of type NM.ActiveConnectionState> 2020-07-06 20:15:10,700 root DEBUG Connection activation succeeded: dev=ovs-port-ovs0, con-state=<enum NM_ACTIVE_CONNECTION_STATE_ACTIVATING of type NM.ActiveConnectionState>, dev-state=<enum NM_DEVICE_STATE_IP_CONFIG of type NM.DeviceState>, state-flags=<flags NM_ACTIVATION_STATE_FLAG_IS_MASTER | NM_ACTIVATION_STATE_FLAG_IS_SLAVE | NM_ACTIVATION_STATE_FLAG_LAYER2_READY of type NM.ActivationStateFlags> 2020-07-06 20:15:10,701 root DEBUG Async action: Activate profile: ovs-port-ovs0 finished 2020-07-06 20:15:10,702 root DEBUG Async action: Activate profile: ovs0 started 2020-07-06 20:15:10,709 root DEBUG Connection activation initiated: dev=ovs0, con-state=<enum NM_ACTIVE_CONNECTION_STATE_ACTIVATING of type NM.ActiveConnectionState> 2020-07-06 20:15:16,774 root DEBUG Connection activation succeeded: dev=ovs0, con-state=<enum NM_ACTIVE_CONNECTION_STATE_ACTIVATED of type NM.ActiveConnectionState>, dev-state=<enum NM_DEVICE_STATE_ACTIVATED of type NM.DeviceState>, state-flags=<flags NM_ACTIVATION_STATE_FLAG_IS_SLAVE | NM_ACTIVATION_STATE_FLAG_LAYER2_READY | NM_ACTIVATION_STATE_FLAG_IP4_READY | NM_ACTIVATION_STATE_FLAG_IP6_READY of type NM.ActivationStateFlags> 2020-07-06 20:15:16,774 root DEBUG Async action: Activate profile: ovs0 finished 2020-07-06 20:15:16,841 root DEBUG Checkpoint /org/freedesktop/NetworkManager/Checkpoint/5 destroyed 2020-07-06 20:15:16,841 root DEBUG Async action: Destroy checkpoint /org/freedesktop/NetworkManager/Checkpoint/5 started 2020-07-06 20:15:16,844 root DEBUG Checkpoint /org/freedesktop/NetworkManager/Checkpoint/5 destroy executed 2020-07-06 20:15:16,844 root DEBUG Async action: Destroy checkpoint /org/freedesktop/NetworkManager/Checkpoint/5 finished Desired state applied: --- interfaces: - name: ovs0 type: ovs-interface state: up mtu: 9600 - name: ovs-br0 type: ovs-bridge state: up bridge: port: - name: ovs0 [20:15:16@ibm-x3650m4-01-vm-05 ~]0# nmstatectl show 'ovs*' --- dns-resolver: config: search: [] server: [] running: search: - ibm2.lab.eng.bos.redhat.com server: - 10.19.42.41 - 10.11.5.19 - 10.5.30.160 route-rules: config: [] routes: config: [] running: [] interfaces: - name: ovs-br0 type: ovs-bridge state: up bridge: options: fail-mode: '' mcast-snooping-enable: false rstp: false stp: false port: - name: ovs0 lldp: enabled: false - name: ovs0 type: ovs-interface state: up ipv4: enabled: false dhcp: false ipv6: enabled: false autoconf: false dhcp: false lldp: enabled: false mac-address: 6E:81:B6:57:71:7F mtu: 9600 [20:15:25@ibm-x3650m4-01-vm-05 ~]0# ip link show ovs0 16: ovs0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9600 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/ether 6e:81:b6:57:71:7f brd ff:ff:ff:ff:ff:ff 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 (nmstate 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-2020:4696 |