Created attachment 479049 [details]
full vdsm log

Description of problem: 
vdsm dose not report an error when addNetwork is initiated to create a bond interface with invalid argument or non-existent option specified in the "BONDING_OPTS" filed.

relevant part of the vdsm log:
Thread-42827::DEBUG::2011-02-16 10:00:43,224::clientIF::42::vds::(wrapper) [10.35.116.10]::call addNetwork with ('vlan163', '163', 'bond1', ['eth2', 'eth3'], {'STP': 'no', 'BONDING_OPTS': 'mode=X bond=X'}) {}
Thread-42827::DEBUG::2011-02-16 10:00:43,225::clientIF::1249::vds::(addNetwork) addNetwork(vlan163,163,bond1,['eth2', 'eth3'],{'STP': 'no', 'BONDING_OPTS': 'mode=X bond=X'})
Thread-42827::DEBUG::2011-02-16 10:00:43,225::utils::570::Storage.Misc.excCmd::(execCmd) '/usr/bin/sudo -n /usr/share/vdsm/addNetwork vlan163 163 bond1 eth2,eth3 STP=no "BONDING_OPTS=mode=X bond=X"' (cwd None)
Thread-42827::DEBUG::2011-02-16 10:00:48,370::utils::570::Storage.Misc.excCmd::(execCmd) SUCCESS: <err> = '/etc/sysconfig/network-scripts/ifup-eth: line 131: echo: write error: Invalid argument\n/etc/sysconfig/network-scripts/ifup-eth: line 131: /sys/class/net/bond1/bonding/bond: No such file or directory\n'; <rc> = 0
Thread-42827::DEBUG::2011-02-16 10:00:48,371::clientIF::47::vds::(wrapper) return addNetwork with {'status': {'message': 'Device eth3 has different MAC address than expected, ignoring.\n/etc/sysconfig/network-scripts/ifup-eth: line 131: echo: write error: Invalid argument\n/etc/sysconfig/network-scripts/ifup-eth: line 131: /sys/class/net/bond1/bonding/bond: No such file or directory\n', 'code': 0}}

*vdsm should report an "invalid argument" and "option not found" in this situation.

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

full vdsm log attached.