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.
Bug 844347 - 3.1 beta1 - VDSM: addNetwork Failed to attach bridge to bond interface
Summary: 3.1 beta1 - VDSM: addNetwork Failed to attach bridge to bond interface
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.3
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: beta
: ---
Assignee: Igor Lvovsky
QA Contact: Meni Yakove
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-30 11:45 UTC by Avi Tal
Modified: 2022-07-09 05:37 UTC (History)
9 users (show)

Fixed In Version: vdsm-4.9.6-26.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-04 19:04:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
vdsm log (416.74 KB, application/x-compressed-tar)
2012-07-30 11:45 UTC, Avi Tal 		no flags Details
engine log (29.78 KB, application/x-compressed-tar)
2012-07-30 11:45 UTC, Avi Tal 		no flags Details
vdsm log using setupnetworks (678.10 KB, application/x-compressed-tar)
2012-07-31 09:15 UTC, Avi Tal 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1508 0 normal SHIPPED_LIVE Important: rhev-3.1.0 vdsm security, bug fix, and enhancement update 2012-12-04 23:48:05 UTC

Description Avi Tal 2012-07-30 11:45:13 UTC 
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>
Comment 1 Avi Tal 2012-07-30 11:45:45 UTC 
Created attachment 601223 [details]
engine log
Comment 3 Dan Kenigsberg 2012-07-30 15:23:53 UTC 
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.
Comment 4 Avi Tal 2012-07-31 09:14:29 UTC 
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.
Comment 5 Avi Tal 2012-07-31 09:15:15 UTC 
Created attachment 601482 [details]
vdsm log using setupnetworks
Comment 8 Igor Lvovsky 2012-08-01 16:42:24 UTC 
http://gerrit.ovirt.org/#/c/6826/
Comment 9 Meni Yakove 2012-08-05 07:36:57 UTC 
verified on vdsm-4.9.6-26.0.
Tested on SetupNetwork, RestAPI and vdsClient.
Comment 12 errata-xmlrpc 2012-12-04 19:04:07 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.