diff options
| author | Antonio Cardace <acardace@redhat.com> | 2020-02-27 17:20:09 +0100 |
|---|---|---|
| committer | Antonio Cardace <acardace@redhat.com> | 2020-02-28 15:45:34 +0100 |
| commit | 50da785be14ac976f909b29766195baaa49e1934 (patch) | |
| tree | 596f0843d69371855d38291fde2d1a14420edca6 /RELICENSE.md | |
| parent | 7625e2483f1925eb3d5d50bfe05c94281f75a408 (diff) | |
| download | NetworkManager-50da785be14ac976f909b29766195baaa49e1934.tar.gz | |
nm-setting-bond: fix '[up|down]delay', 'miimon' validation
Just looking at the hashtable entry of 'updelay' and 'downdelay' options
is wrong, we have to inspect their values to check if they're
actually enabled or not.
Otherwise bond connections with valid settings will fail
when created:
$ nmcli c add type bond ifname bond99 bond.options miimon=0,updelay=0,mode=0
Error: Failed to add 'bond-bond99' connection: bond.options: 'updelay' option requires 'miimon' option to be set
Also add unit tests.
https://bugzilla.redhat.com/show_bug.cgi?id=1805184
Fixes: d595f7843e31 ('libnm: add libnm/libnm-core (part 1)')
Diffstat (limited to 'RELICENSE.md')
0 files changed, 0 insertions, 0 deletions