Bug 1718173 - Normalization of bond connection fails in some cases
Summary: Normalization of bond connection fails in some cases
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: sushil kulkarni
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-07 07:59 UTC by Beniamino Galvani
Modified: 2019-08-26 09:15 UTC (History)
8 users (show)

Fixed In Version: NetworkManager-1.18.0-2.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)

Description Beniamino Galvani 2019-06-07 07:59:33 UTC
When adding or modifying a bond connection, we first check that
constraints between options are met and then we normalize the
connection. During normalization we remove options that are not
compatible with the selected bond mode. This step can remove an option
that was needed by another one, making the connection invalid.

Reproducer:

 # nmcli connection add type bond bond.options mode=4,arp_interval=2,arp_ip_target=1.1.1.1
 (process:18007): libnm-WARNING **: 09:33:48.816: connection did not verify after normalization: ??
 (process:18007): libnm-CRITICAL **: 09:33:48.816: file ../libnm-core/nm-connection.c: line 1684 (nm_connection_normalize): should not be reached
 Error: Failed to add 'bond' connection: bond.options: 'arp_ip_target' option requires 'arp_interval' option to be set

NM version: 1.14.0-14.el8 (master is affected as well)

Comment 3 Vladimir Benes 2019-08-26 09:15:35 UTC
nmcli connection add type bond bond.options mode=4,arp_interval=2,arp_ip_target=1.1.1.1 sets 802.3ad mode bond correctly and arp values are thrown away.


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