Description of problem:
When nmstate try to apply bonding options to connection profile,
nm-connection-error-quark: bond.options: 'updelay' option requires 'miimon' option to be set (7)
But in kernel, its default value for a bond is updelay=0 miimon=0 which is legal.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. nmcli c add type bond ifname bond99 bond.options updelay=0,miimon=0,mode=0
Error: Failed to add 'bond-bond99' connection: bond.options: 'updelay' option requires 'miimon' option to be set
I think NM is overkill on this bond option check. It's hard for NM to track the
restrictions of kernel.
MR with the fix waiting for review: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/424
Fixed upstream with commit 50da785be14ac976f909b29766195baaa49e1934 and backported to branch nm-1-22
nmstate has workaround in upstream master branch: https://github.com/nmstate/nmstate/pull/839
test case added:
test case added (correct link):
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.