RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 1669143 [details]
reproducer.log

Description of problem:
Once you set 'arp_ip_target'(arp_interval is required meanwhile), you cannot empty it anymore. It means we can't set back 'arp_ip_target' and 'arp_interval' options to default value

Version-Release number of selected component (if applicable):
nmstate-0.2.6-3.8.el8.noarch
NetworkManager-1.22.8-4.el8.x86_64


How reproducible:
100%

Steps to Reproduce:
1. Set a bond with 'arp_ip_target' and 'arp_interval'
2. Try to remove these two options
3.
See the attachment for the details.

Actual results:
Fail

Expected results:
No failure

Additional info:
Now you have to change 'arp_interval' and 'arp_ip_target' at the same time:
2020-03-11 11:01:39,011 root         ERROR    NM main-loop aborted: Connection adding failed: error=nm-connection-error-quark: bond.options: 'arp_interval' option requires 'arp_ip_target' option to be set (7)
2020-03-11 10:59:47,438 root         ERROR    NM main-loop aborted: Connection update failed: error=nm-connection-error-quark: bond.options: 'arp_ip_target' option requires 'arp_interval' option to be set (7), dev=temp3/<enum NM_DEVICE_STATE_ACTIVATED of type NM.DeviceState>

*** Bug 1828302 has been marked as a duplicate of this bug. ***

Created attachment 1698029 [details]
verified.log

verified:
nmstate-0.3.2-1.el8.noarch
NetworkManager-1.26.0-0.1.el8.x86_64
DISTRO=RHEL-8.3.0-20200616.0
Linux hp-dl388g8-08.rhts.eng.pek2.redhat.com 4.18.0-214.el8.x86_64 #1 SMP Fri Jun 12 08:55:08 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

See the attachment for details.

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 (nmstate 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-2020:4696