Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
When creating bond via cockpit, in the "Bond Settings" page, the default value for "Mode" drop-down list is "Active backup". If keep this default value, in the generated bond, the bond mode is "Round Robin".
Version-Release number of selected component (if applicable):
cockpit-system-211.3-1.el8.noarch
cockpit-ws-211.3-1.el8.x86_64
cockpit-ovirt-dashboard-0.14.3-1.el8ev.noarch
cockpit-211.3-1.el8.x86_64
cockpit-bridge-211.3-1.el8.x86_64
cockpit-dashboard-211.3-1.el8.noarch
cockpit-storaged-211.3-1.el8.noarch
How reproducible:
100%
Steps to Reproduce:
1. Install "redhat-virtualization-host-4.4.0-20200325.0.el8_2"
2. Login to cockpit
3. Click "Networking" -> "Add Bond", in the "Bond Settings" page, select 2 NICs from the "Interfaces" check-box
4. Keep the default value of "Mode" as "Active backup", click the "Apply" button
5. Enter "Networking" -> "bond0" page, focus on the value of the "Bond" item in bond0
6. Login RHVH, check the configuration file "ifcfg-bond0"
# cat /etc/sysconfig/network-scripts/ifcfg-bond0
Actual results:
In the "Networking" -> "bond0" page, the value of "Bond" is "Round Robin" and in the generated "ifcfg-bond0" file, the mode is "balance-rr"
~~~
BONDING_OPTS="downdelay=0 miimon=100 mode=balance-rr updelay=0"
TYPE=Bond
BONDING_MASTER=yes
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=bond0
UUID=a42cb335-2b3b-4c7c-8212-421f2000dbc4
DEVICE=bond0
ONBOOT=yes
AUTOCONNECT_SLAVES=yes
~~~
Expected results:
In the "Bond Settings" page, if the default value of "Mode" is "Active backup", the "Primary" drop-down list should be visible by default and the created bond mode should be "Active backup"
Additional info:
In the "Bond Settings" page, from the "Mode" drop-down list, if select an other mode before clicking the "Active Backup" mode, then click the "Active backup" mode, the result will be correct.
Fix here: https://github.com/cockpit-project/cockpit/pull/13866
Thus, this is a problem with our UI logic. Programmatically selecting from a drop down menu did change how it looks, but didn't actually change the value of the drop down that the program sees. Changes to a drop down by the user work as expected.
As a workaround, you can explicitly switch to "Round Robin" (or any other choice) and then back to "Active Backup". Then the UI logic will correctly create a bond with mode Active Backup.
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 (cockpit 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:4511