Bug 951018 - Don't fail when a non-existing bond is requested via setupNetworks.
Summary: Don't fail when a non-existing bond is requested via setupNetworks.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.1.3
Hardware: x86_64
OS: Windows
medium
medium
Target Milestone: ---
: 3.1.4
Assignee: Antoni Segura Puimedon
QA Contact: Meni Yakove
URL:
Whiteboard: network
Depends On: 649239 918666
Blocks: 647155 649241
TreeView+ depends on / blocked
 
Reported: 2013-04-11 11:01 UTC by Antoni Segura Puimedon
Modified: 2016-02-10 19:52 UTC (History)
16 users (show)

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.
Clone Of: 918666
Environment:
Last Closed: 2013-05-01 18:25:37 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0774 0 normal SHIPPED_LIVE rhev 3.1.4 - vdsm bug fix update 2013-05-01 22:23:56 UTC
oVirt gerrit 12534 0 None None None Never
oVirt gerrit 12701 0 None None None Never

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
Note You need to log in before you can comment on or make changes to this bug.