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 930450 [details]
Run this script to reproduce bug

Description of problem:
Bonding mode does not accept numeric values, only strings.

Version-Release number of selected component (if applicable):
0.9.9.1-13.git20140326.4dba720.el7

How reproducible:
When defining bond, put numeric value in bond-mode.

Steps to Reproduce:
1. Run attached bonding.py

Actual results:
Traceback (most recent call last):
  File "bonding.py", line 54, in <module>
    main()
  File "bonding.py", line 36, in main
    con_obj_path = settings_if.AddConnection(connection)
  File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 70, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.GLib.UnmappedError.NmSettingBondErrorQuark.Code3: bond.options: '1' is not a valid value for 'mode'


Expected results:
Bond should be created no matter whether it's defined by string or numeric value.

Additional info:
https://bugzilla.gnome.org/show_bug.cgi?id=704666

Fixes are in upstream NetworkManager branch jk/numeric-bond-modes.

It looks like you never use nm_utils_bond_mode_string_to_int() and nm_utils_bond_mode_int_to_string() independently of each other; you could just replace them with a single

  const char *nm_utils_bond_mode_normalize (const char *mode);


"ifcfg-rh: accept numeric bonding mode values in BONDING_OPTS" should not actually be needed after the normalization patch. ifcfg-rh can just set the option as the numeric string, and it will get normalized to the string value later on.

The code has been merged to master. See upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=704666#c2.

Jiri, we missed the timeframe when exceptions could go in and now I would need blocker+ to put the change into RHEL 7.1. Would you request blocker flag if you want to push this into RHEL 7.1.

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://rhn.redhat.com/errata/RHBA-2015-0311.html