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 1668640 [details]
log

Description of problem:
If miimon is set, cannot add updelay anymore.

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

How reproducible:
100%

Steps to Reproduce:
# cat miimon-only.yml
interfaces:
- name: temp0
  type: bond
  state: up
  ipv4:
    address:
    - ip: 192.168.10.2
      prefix-length: 24
    dhcp: false
    enabled: true
  ipv6:
    enabled: true
  link-aggregation:
    mode: balance-rr
    options:
      miimon: '1000'
    slaves:
    - veth10_ep
    - veth3_ep

# cat miimon-and-updelay.yml
interfaces:
- name: temp0
  type: bond
  state: up
  ipv4:
    address:
    - ip: 192.168.10.2
      prefix-length: 24
    dhcp: false
    enabled: true
  ipv6:
    enabled: true
  link-aggregation:
    mode: balance-rr
    options:
      miimon: '1000'
      updelay: 1000
    slaves:
    - veth10_ep
    - veth3_ep

1. nmstatectl set miimon-only.yml
2. nmstatectl set miimon-and-updelay.yml
3.

Actual results:
Fail

Expected results:
No failure

Additional info:
If specify miimon and updelay when create a new bond interface, it can work then. Means you can make it work well by skipping step 1 and doing step 2 directly.

Move bond options related bugs to RHEL 8.3 as NetworkManager intend to change a lot in bond options related codes there.

It's a NetworkManager Bug 1847814 - Reapply does not update bond options

Verified with versions:
nmstate-1.0.0-1.el8.noarch
nispor-1.0.1-2.el8.x86_64
NetworkManager-1.30.0-0.4.el8.x86_64
DISTRO=RHEL-8.4.0-20201218.d.2
Linux dell-per730-20.rhts.eng.pek2.redhat.com 4.18.0-262.el8.dt3.x86_64 #1 SMP Tue Dec 15 04:28:42 EST 2020 x86_64 x86_64 x86_64 GNU/Linux

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-2021:1748