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.
Created attachment 601222[details]
vdsm log
rhevm-3.1.0-9.el6ev.noarch (on cluster 3.1)
vdsm-4.9.6-24.0.el6_3.x86_64
Description of problem:
running addNetwork directly on host or using old REST API to attach bond interface to host leads to nicless bridge
running:
# vdsClient 0 addNetwork bridge=sw2 bond=bond0 nics=eth2,eth3
result:
# brctl show
bridge name bridge id STP enabled interfaces
rhevm 8000.001517a76a4c no eth0
sw2 8000.000000000000 no
note: this problem directly affect the creation of bond0 on sw2 via REST old API
POST url: /api/hosts/ae11957e-d98d-11e1-b2c5-001a4a169763/nics
body:
<host_nic>
<name>bond0</name>
<network>
<name>sw2</name>
</network>
<bonding>
<slaves>
<host_nic>
<name>eth2</name>
</host_nic>
<host_nic>
<name>eth3</name>
</host_nic>
</slaves>
</bonding>
</host_nic>
I believe the error is due to premature ifup'ing of the bonding device:
::(ifup) can't add bond0 to bridge test-network: Invalid argument
which has been caused by the fix http://gerrit.ovirt.org/6217 for bug 842338 (how come this was not found during pre-integration?).
Please try this issue with the rhev-3.0 version of this fix.
I found the same issue with different scenario:
1. create bond bridged network (via setupnetworks)
# brctl show
bridge name bridge id STP enabled interfaces
rhevm 8000.001517a76a4c no eth0
sw2 8000.001d0968714e no bond0
2. edit bonding mode (via setupnetworks)
# brctl show
bridge name bridge id STP enabled interfaces
rhevm 8000.001517a76a4c no eth0
sw2 8000.000000000000 no
This will lead to the same result of nicless bridge.
attaching vdsm log.
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.
http://rhn.redhat.com/errata/RHSA-2012-1508.html
Created attachment 601222 [details] vdsm log rhevm-3.1.0-9.el6ev.noarch (on cluster 3.1) vdsm-4.9.6-24.0.el6_3.x86_64 Description of problem: running addNetwork directly on host or using old REST API to attach bond interface to host leads to nicless bridge running: # vdsClient 0 addNetwork bridge=sw2 bond=bond0 nics=eth2,eth3 result: # brctl show bridge name bridge id STP enabled interfaces rhevm 8000.001517a76a4c no eth0 sw2 8000.000000000000 no note: this problem directly affect the creation of bond0 on sw2 via REST old API POST url: /api/hosts/ae11957e-d98d-11e1-b2c5-001a4a169763/nics body: <host_nic> <name>bond0</name> <network> <name>sw2</name> </network> <bonding> <slaves> <host_nic> <name>eth2</name> </host_nic> <host_nic> <name>eth3</name> </host_nic> </slaves> </bonding> </host_nic>