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 835784 - 3.1 - Allow to create a network on top of existing bond in additional to create a new bond and network
Summary: 3.1 - Allow to create a network on top of existing bond in additional to crea...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Igor Lvovsky
QA Contact: GenadiC
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-27 06:20 UTC by Igor Lvovsky
Modified: 2022-07-09 05:36 UTC (History)
9 users (show)

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


Attachments (Terms of Use)


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 Igor Lvovsky 2012-06-27 06:20:26 UTC
Description of problem:

Assume you already have a bond0 for (eth1, eth2) and now you want to create network "bridge_woVlan" on top of it and in additional you want to create a new bond1 for (eth3, eth4) and create network "bridge_woVlan_2" on top of bond 1.
If you want to do it in same setupNetwork command, we will fail, as you can see bellow:

Thread-38::DEBUG::2012-06-26 18:37:13,507::BindingXMLRPC::872::vds::(wrapper) client [10.35.18.152]::call setupNetworks with ({'bridge_woVlan': {'bondin
g': 'bond4', 'bridged': 'true'}, 'bridge_woVlan_2': {'bonding': 'bond3', 'bridged': 'true'}}, {'bond3': {'nics': ['eth4', 'eth5'], 'options': 'mode=4'}}
, {'connectivityCheck': 'true', 'connectivityTimeout': 60000}) {} flowID [61555da6]

....

MainProcess|Thread-38::ERROR::2012-06-26 18:37:13,535::configNetwork::1152::setupNetworks::(setupNetworks) 'bond4'
Traceback (most recent call last):
  File "/usr/share/vdsm/configNetwork.py", line 1107, in setupNetworks
    d['nics'] = bondings[d['bonding']]['nics']
KeyError: 'bond4'
MainProcess|Thread-38::ERROR::2012-06-26 18:37:13,536::supervdsmServer::76::SuperVdsm.ServerCallback::(wrapper) Error in setupNetworks
Traceback (most recent call last):
  File "/usr/share/vdsm/supervdsmServer.py", line 74, in wrapper
    return func(*args, **kwargs)
  File "/usr/share/vdsm/supervdsmServer.py", line 150, in setupNetworks
    return configNetwork.setupNetworks(networks, bondings, **options)
  File "/usr/share/vdsm/configNetwork.py", line 1107, in setupNetworks
    d['nics'] = bondings[d['bonding']]['nics']
KeyError: 'bond4'


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create bond0 with (eth1, eth2)  and apply the action
2. Do followinf in single setupNetwork command:  
   - attach network 'bridge_woVlan' to the bond1
   - create bond2 with (eth3, eth4)
   - attach network "bridge_woVlan_2" to the bond2
   - appply

3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Igor Lvovsky 2012-06-27 07:55:36 UTC
http://gerrit.ovirt.org/#/c/5737/1

Comment 3 GenadiC 2012-07-23 07:02:25 UTC
Verified in 3.1 SI11

Comment 6 errata-xmlrpc 2012-12-04 19:00:56 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.