-
Bug
-
Resolution: Unresolved
-
Normal
-
rhel-9.6
-
No
-
Moderate
-
1
-
rhel-net-mgmt
-
ssg_networking
-
3
-
False
-
False
-
-
No
-
NMT SST - 2025Q2
-
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
Attempting to set multiple IP addresses in the arp_ip_target bonding option using the documented dracut syntax (semicolon-separated IPs). This is initially created from https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1731
What is the impact of this issue to you?
nm-initrd-generator correctly accepts multiple IP addresses separated by semicolons in the arp_ip_target bonding option, as specified by the dracut documentation.
Please provide the package NVR for which the bug is seen:
How reproducible is this bug?:
Always
Steps to reproduce
Configure bonding via kernel cmdline using dracut with multiple arp_ip_target addresses separated by semicolons:
bond=bond0:eth0,eth1:mode=active-backup,arp_ip_target=1.2.3.4;5.6.7.8,arp_interval=200
Check logs for errors from NetworkManager (nm-initrd-generator).
Expected results
nm-initrd-generator successfully parses the bonding option:
arp_ip_target=1.2.3.4;5.6.7.8
without errors.
Actual results
Error message occurs, and the bonding configuration is not correctly parsed:
<warn> [1741272519.7582] cmdline-reader: Ignoring invalid bond option: "arp_ip_target" = "1.2.3.4;5.6.7.8": '1.2.3.4;5.6.7.8' is not a valid IPv4 address for 'arp_ip_target' option