1807726 – Cannot set un-default mtu on ovs interface

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 1807726 - Cannot set un-default mtu on ovs interface

Summary: Cannot set un-default mtu on ovs interface

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 8
Classification:	Red Hat
Component:	nmstate
Sub Component:
Version:	8.2
Hardware:	Unspecified
OS:	Unspecified
Priority:	high
Severity:	high
Target Milestone:	rc
Target Release:	8.3
Assignee:	Gris Ge
QA Contact:	Mingyu Shi
Docs Contact:
URL:
Whiteboard:
Depends On:	1820052
Blocks:
TreeView+	depends on / blocked

Reported:	2020-02-27 04:16 UTC by Mingyu Shi
Modified:	2020-11-04 03:10 UTC (History)
CC List:	8 users (show)
Fixed In Version:	nmstate-0.3.2-1.el8
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Clones:	1820052 (view as bug list)
Environment:
Last Closed:	2020-11-04 03:08:25 UTC
Type:	Bug
Target Upstream Version:
Embargoed:
Dependent Products:
Flags:	pm-rhel: mirror+

Attachments	(Terms of Use)

Links
System	ID	Priority	Status	Summary	Last Updated
Github	nmstate nmstate issues 1048	None	closed	Add "set un-default mtu on ovs interface" test	2020-12-10 14:18:47 UTC
Red Hat Product Errata	RHBA-2020:4696	None	None	None	2020-11-04 03:08:48 UTC
freedesktop.org Gitlab	NetworkManager NetworkManager merge_requests 433	None	None	None	2020-03-11 07:04:14 UTC

Comment 1 Gris Ge 2020-02-27 06:22:28 UTC

Hi Beniamino,

Does NetworkManager OVS support MTU changes?

Comment 2 Beniamino Galvani 2020-02-27 08:22:20 UTC

(In reply to Gris Ge from comment #1)
> Hi Beniamino,
> 
> Does NetworkManager OVS support MTU changes?

Not yet, I'll implement it.

Comment 3 Till Maas 2020-02-27 09:17:54 UTC

Dominik, is this a problem for RHV?

Comment 4 Dominik Holler 2020-02-27 09:26:16 UTC

(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.

Comment 5 Beniamino Galvani 2020-03-09 15:46:19 UTC

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/433

Comment 6 Till Maas 2020-03-13 07:21:53 UTC

This is reported against nmstate but fixed in NetworkManager - is anything needed for this in Nmstate?

Comment 7 Gris Ge 2020-03-13 09:19:34 UTC

(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.

Comment 8 Beniamino Galvani 2020-03-26 20:58:59 UTC

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?

Comment 9 Gris Ge 2020-04-02 05:15:51 UTC

(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.

Comment 10 Beniamino Galvani 2020-04-02 07:21:02 UTC

Okay, I'm going to clone it so that it gets verified by NM QA.

Comment 11 Fernando F. Mancera 2020-04-26 22:09:59 UTC

It would be nice to have an integration test for this in nmstate. Issue: https://github.com/nmstate/nmstate/issues/1048

Comment 14 Mingyu Shi 2020-07-06 12:17:12 UTC

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

Comment 17 errata-xmlrpc 2020-11-04 03:08:25 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 (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

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