Bug 2117202

Summary: Regression: Cannot set 2+ ip addresses for bond arp_ip_target option
Product: Red Hat Enterprise Linux 9 Reporter: Gris Ge <fge>
Component: NetworkManagerAssignee: Fernando F. Mancera <ferferna>
Status: CLOSED ERRATA QA Contact: Matej Berezny <mberezny>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 9.1CC: acabral, bgalvani, ferferna, lrintel, rkhan, sukulkar, till, vbenes
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: NetworkManager-1.39.90-1.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-15 10:50:05 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:
Attachments:
Description Flags
NetworkManager trace log none

Description Gris Ge 2022-08-10 10:02:31 UTC 
Description of problem:


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


How reproducible:


Steps to Reproduce:
1. sudo nmcli c add type bond ifname bond0 connection.id bond0 bond.options arp_ip_target="192.0.2.1 192.0.2.2",mode=active-backup,arp_interval=10
2. cat /sys/class/net/bond0/bonding/arp_ip_target
3.

Actual results:
Empty arp_ip_target in sysfs.

Expected results:
192.0.2.1 192.0.2.2

Additional info:

This is found by tier1 test case of nmstate CI, hence it is used by layer products. Please fix it ASAP.
Comment 1 Gris Ge 2022-08-10 10:08:53 UTC 
Created attachment 1904677 [details]
NetworkManager trace log
Comment 5 errata-xmlrpc 2022-11-15 10:50:05 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 (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.

https://access.redhat.com/errata/RHBA-2022:8265