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 interface without attached network the GUI stack and the BOND interface not created.
Version-Release number of selected component (if applicable):
vdsm-4.9.6-16.0.el6.x86_64
rhevm-3.1.0_0001-14.el6ev.noarch
How reproducible:
Always
Steps to Reproduce:
1.Open SetupNetwork and create BOND (Do not attach any network to the BOND)
2.Apply
Actual results:
BOND not created and GUI stack (Need to refresh)
Expected results:
BOND should be created.
logical networks or physical networks.
assuming the latter, i'd say correct behavior is to not allow creating the bond without specifying at least two physical networks it bonds.
(In reply to comment #3)
> logical networks or physical networks.
> assuming the latter, i'd say correct behavior is to not allow creating the
> bond without specifying at least two physical networks it bonds.
Create BOND using physical networks and do not attached logical networks to it.
If we must attached logical network to the BOND the 'OK' button should be grayed out if we didn't attached any logical network to the BOND.
(In reply to comment #5)
> Create BOND using physical networks and do not attached logical networks to
> it.
> If we must attached logical network to the BOND the 'OK' button should be
> grayed out if we didn't attached any logical network to the BOND.
No need to gray out, this is a VDSM side bug so please update product/component.
(In reply to comment #6)
> No need to gray out, this is a VDSM side bug so please update
> product/component.
Mike, I fully trust your ability to do it
all important files is attached in attached logs.tar.gz
With vdsm-4.9.6-17.0.el6.x86_64 it is possible to create empty bond. However the bond is started in wrong mode. I selected bond mode1 (active-backup), but bond starts with mode0 (round-robin).
in vdsm.log it is visible that bondmode=1 is sent
Thread-62::DEBUG::2012-07-11 11:27:32,047::BindingXMLRPC::864::vds::(wrapper) client [10.34.63.65]::call setupNetworks with ({}, {'bond1': {'nics': ['p1p1', 'p1p2'], 'options': 'mode=1 miimon=100'}}, {'connectivityCheck': 'true', 'connectivityTimeout': 60000}) {} flowID [1472104]
ifcfg file is created correctly
[root@dell-r210ii-05 ~]# cat /etc/sysconfig/network-scripts/ifcfg-bond1
DEVICE=bond1
ONBOOT=yes
BOOTPROTO=none
BONDING_OPTS='mode=1 miimon=100'
NM_CONTROLLED=no
but bond is running in mode 0 (roun-robin)
[root@dell-r210ii-05 ~]# cat /proc/net/bonding/bond1
Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
Bonding Mode: load balancing (round-robin)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: p1p1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 1
Permanent HW addr: 90:e2:ba:04:2d:74
Slave queue ID: 0
Slave Interface: p1p2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 1
Permanent HW addr: 90:e2:ba:04:2d:75
Slave queue ID: 0
Maybe this is related to following WARNING from vdsm.log
MainProcess|Thread-62::WARNING::2012-07-11 11:27:32,508::configNetwork::83::root::(ifup) /etc/sysconfig/network-scripts/ifup-eth: line 136: echo: write error: Operation not permitted