Bug 1805205

Summary: Cannot set bond option updelay=0,miimon=0
Product: Red Hat Enterprise Linux 8 Reporter: Gris Ge <fge>
Component: nmstateAssignee: Gris Ge <fge>
Status: CLOSED CURRENTRELEASE QA Contact: Mingyu Shi <mshi>
Severity: low Docs Contact:
Priority: low    
Version: 8.2CC: ferferna, jiji, jishi, network-qe, till
Target Milestone: rc   
Target Release: 8.2   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: nmstate-0.2.6-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-21 05:29:44 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: 1805184    
Bug Blocks:    

Description Gris Ge 2020-02-20 13:42:04 UTC
Description of problem:

The kernel default options for bond is:
updelay=0,miimon=0,mode=0

But nmstate does not allow setting this option.

Version-Release number of selected component (if applicable):
nmstate-0.2.5-1

How reproducible:
100%

Steps to Reproduce:
1. echo +bond0 |sudo tee /sys/class/net/bonding_masters
2. 
echo '---
interfaces:
- name: bond0
  type: bond
  state: up
  link-aggregation:
    mode: balance-rr' | nmstatectl set -
3.

Actual results:


Expected results:


Additional info:

Comment 1 Till Maas 2020-02-20 14:55:51 UTC
Hopefully, this can be fixed in NetworkManager by being more flexible about the settings. A workaround in Nmstate will have shortcommings in case a system is rebooted because then Nmstate cannot restore the settings but only NetworkManager can.

Comment 2 Till Maas 2020-02-24 20:16:14 UTC
Gris, can we close this, attach this to the erratum or change this to ON_QA or does this require changes in Nmstate?

Comment 4 Gris Ge 2020-02-25 08:19:47 UTC
The use case is fixed in nmstate-0.2.6-1.el8.

But user still cannot set `updelay=0,miimon=0,mode=0` explicitly which is a bug of NetworkManager: bug https://bugzilla.redhat.com/show_bug.cgi?id=1805184

Comment 7 Gris Ge 2020-08-21 05:29:44 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, 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:3052