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.

Description of problem:

The kernel default options for bond is:
updelay=0,miimon=0,mode=0

But nmstate does not allow setting this option.

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

How reproducible:
100%

Steps to Reproduce:
1. echo +bond0 |sudo tee /sys/class/net/bonding_masters
2. 
echo '---
interfaces:
- name: bond0
  type: bond
  state: up
  link-aggregation:
    mode: balance-rr' | nmstatectl set -
3.

Actual results:


Expected results:


Additional info:

Hopefully, this can be fixed in NetworkManager by being more flexible about the settings. A workaround in Nmstate will have shortcommings in case a system is rebooted because then Nmstate cannot restore the settings but only NetworkManager can.

Gris, can we close this, attach this to the erratum or change this to ON_QA or does this require changes in Nmstate?

The use case is fixed in nmstate-0.2.6-1.el8.

But user still cannot set `updelay=0,miimon=0,mode=0` explicitly which is a bug of NetworkManager: bug https://bugzilla.redhat.com/show_bug.cgi?id=1805184

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-2020:3052