Bug 1718173

Summary:	Normalization of bond connection fails in some cases
Product:	Red Hat Enterprise Linux 8	Reporter:	Beniamino Galvani <bgalvani>
Component:	NetworkManager	Assignee:	sushil kulkarni <sukulkar>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.1	CC:	atragler, bgalvani, fgiudici, lrintel, rkhan, sukulkar, thaller, vbenes
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	NetworkManager-1.18.0-2.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-05 22:30:06 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:

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 1 Beniamino Galvani 2019-06-10 13:45:35 UTC

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/179

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.

Comment 5 errata-xmlrpc 2019-11-05 22:30:06 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-2019:3623