Description of problem:
hosted-dengine --deploy does not detect issues with ovirtmgmt network configuration.

Version-Release number of selected component (if applicable):
ovirt-hosted-engine-setup-1.3.3.4-1.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. create bond which is suppose to be in the ovirtmgmt bridge with incorrect configuration. (BONDING_OPTS='mode=802.3ad mmimon=100 xmit_hash_policy=layer2+3') there should be miimon instead of mmimon

Actual results:
2016-03-15 17:29:53 DEBUG otopi.plugins.ovirt_hosted_engine_setup.engine.add_host add_host._wait_host_ready:96 VDSM host in installing state
2016-03-15 17:29:54 DEBUG otopi.plugins.ovirt_hosted_engine_setup.engine.add_host add_host._wait_host_ready:96 VDSM host in non_operational state
2016-03-15 17:29:55 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:219 DIALOG:SEND                 The host hosted_engine_2 is in non-operational state.
2016-03-15 17:29:55 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:219 DIALOG:SEND                 Please try to activate it via the engine webadmin UI.
2016-03-15 17:29:55 DEBUG otopi.plugins.otopi.dialog.human human.queryString:156 query OVEHOSTED_NON_OPERATIONAL
2016-03-15 17:29:55 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:219 DIALOG:SEND                 Retry checking host status or ignore this and continue (Retry, Ignore)[Retry]? 


Expected results:
The tool wil notify the user of the incorrect network configuration.

Additional info:
vdsm fails with the following error message:

jsonrpc.Executor/3::DEBUG::2016-03-15 17:29:51,975::__init__::503::jsonrpc.JsonRpcServer::(_serveRequest) Calling 'Host.setupNetworks' in bridge with {u'bondings': {}, u'networks': {u'ovirtmgmt': {u'vlan': u'xx', u'ipaddr': u'x.x.x.x', u'bonding': u'bond0', u'mtu': u'1500', u'netmask': u'x.x.x.x', u'STP': u'no', u'bridged': u'true', u'gateway': u'x.x.x.x', u'defaultRoute': True}}, u'options': {u'connectivityCheck': u'true', u'connectivityTimeout': 120}}
jsonrpc.Executor/4::DEBUG::2016-03-15 17:29:51,976::__init__::503::jsonrpc.JsonRpcServer::(_serveRequest) Calling 'Host.ping' in bridge with {}
jsonrpc.Executor/4::DEBUG::2016-03-15 17:29:51,976::__init__::533::jsonrpc.JsonRpcServer::(_serveRequest) Return 'Host.ping' in bridge with True
jsonrpc.Executor/3::ERROR::2016-03-15 17:29:52,011::API::1643::vds::(_rollback) 'mmimon' is not a valid bonding option
Traceback (most recent call last):
  File "/usr/share/vdsm/API.py", line 1641, in _rollback
    yield rollbackCtx
  File "/usr/share/vdsm/API.py", line 1493, in setupNetworks
    supervdsm.getProxy().setupNetworks(networks, bondings, options)
  File "/usr/share/vdsm/supervdsm.py", line 50, in __call__
    return callMethod()
  File "/usr/share/vdsm/supervdsm.py", line 48, in <lambda>
    **kwargs)
  File "<string>", line 2, in setupNetworks
  File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod
    raise convert_to_error(kind, result)
ConfigNetworkError: (25, "'mmimon' is not a valid bonding option")