Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 951018

Summary: Don't fail when a non-existing bond is requested via setupNetworks.
Product: Red Hat Enterprise Virtualization Manager Reporter: Antoni Segura Puimedon <asegurap>
Component: vdsmAssignee: Antoni Segura Puimedon <asegurap>
Status: CLOSED ERRATA QA Contact: Meni Yakove <myakove>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.1.3CC: abaron, alkaplan, atal, bazulay, danken, hateya, iheim, jocarter, lpeer, lvernia, mkenneth, Rhev-m-bugs, sgrinber, yeylon, ykaul, zdover
Target Milestone: ---Keywords: CodeChange, ZStream
Target Release: 3.1.4   
Hardware: x86_64   
OS: Windows   
Whiteboard: network
Fixed In Version: vdsm-4.10.2-1.11.el6ev Doc Type: Bug Fix
Doc Text:
Previously, when setupNetworks referred to a non-existing bond, setupNetworks failed to validate bond options, returning "error parsing bonding options mode=4". This was because previously existing bond device options were confirmed to exist by a check determining whether sysfs exposed them. In this case, if the request bond did not exist during the check, the error message displayed and the bond options failed to validate. A patch to VDSM now ensures that when setupNetworks requests a bond that doesn't exist, bond option validation does not fail.
 Story Points: ---
Clone Of: 918666 Environment:
Last Closed: 2013-05-01 18:25:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 649239, 918666    
Bug Blocks: 647155, 649241    

Comment 4 Meni Yakove 2013-04-28 07:15:46 UTC 
Verified on:
vdsClient addNetwork bridge=bla bond=bond777 nics=eth4
rhevm-3.2.0-10.20.master.el6ev.noarch
Comment 6 errata-xmlrpc 2013-05-01 18:25:37 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/RHBA-2013-0774.html