Description of problem: Bridge name and bridge device seems to be mixed up during engine-setup. Version-Release number of selected component (if applicable): - ovirt-node-ng-installer-master-2017112909 - appliance 4.2-20171130.1.el7.centos How reproducible: During hosted-engine-setup the user gets asked which interface is supposed to be used for the management bridge. The selected value will be set as OVEHOSTED_NETWORK/bridgeName in the answer file. Unfortunately this value will be used as name of the bridge and results in: --== HOST NETWORK CONFIGURATION ==-- [ INFO ] Bridge bond_ge.145 already created [WARNING] Unable to detect the interface where Bridge bond_ge.78 has been created on When setting the value to "ovirtmgmt" in the answer file results in a question during setup: Please indicate a nic to set ovirtmgmt bridge on: (bond_ge.78, em1, bond_ge, em2) [bond_ge.78]: Setting the interface during setup seems to set the values as expected. --== CONFIGURATION PREVIEW ==-- Bridge interface : bond_ge.78 Bridge name : ovirtmgmt Unfortunately, this still fails: Failed to execute stage 'Misc configuration': Failed to setup networks {'ovirtmgmt': {'vlan': 78, 'ipaddr': u'192.168.78.40', 'netmask': u'255.255.255.0', 'bonding': u'bond_ge', 'gateway': u'192.168.78.254', 'defaultRoute': True}}. Error: "Command Host.setupNetworks with args {'bondings': {}, 'options': {'connectivityCheck': False}, 'networks': {'ovirtmgmt': {'vlan': 78, 'ipaddr': u'192.168.78.40', 'netmask': u'255.255.255.0', 'bonding': u'bond_ge', 'gateway': u'192.168.78.254', 'defaultRoute': True}}} failed: (code=25, message=bad bond name(s): bond_ge)" Actual results: errors Expected results: bond_ge.78 will be setup as interface for the management bridge Additional info:
I reconfigured my setup to use bond0 instead of bond_ge. In this case the setup does not complain about "bad bond name(s)"
(In reply to Bernhard Seidl from comment #0) Copy paste error: - [ INFO ] Bridge bond_ge.145 already created + [ INFO ] Bridge bond_ge.78 already created
(In reply to Bernhard Seidl from comment #1) > I reconfigured my setup to use bond0 instead of bond_ge. In this case the > setup does not complain about "bad bond name(s)" Please see: https://bugzilla.redhat.com/show_bug.cgi?id=1452243#c7
I believe this should be reopened. We just encountered this as well, where our bond is called mgmt: [ INFO ] Configuring the management bridge [ ERROR ] Failed to execute stage 'Misc configuration': Failed to setup networks {'ovirtmgmt': {'bonding': 'mgmt', 'ipaddr': u'10.51.14.112', 'netmask': u'255.255.255.0', 'defaultRoute': True, 'gateway': u'10.51.14.1'}}. Error: "Command Host.setupNetworks with args {'bondings': {}, 'options': {'connectivityCheck': False}, 'networks': {'ovirtmgmt': {'bonding': 'mgmt', 'ipaddr': u'10.51.14.112', 'netmask': u'255.255.255.0', 'defaultRoute': True, 'gateway': u'10.51.14.1'}}} failed: (code=25, message=bad bond name(s): mgmt)" [ INFO ] Yum Performing yum transaction rollback I can't see why mgmt is in any way an invalid bond name, all our bonded interfaces are named after their native network.
# rpm -qa | grep -i ovirt ovirt-host-dependencies-4.2.0-1.el7.centos.x86_64 ovirt-host-deploy-1.7.0-1.el7.centos.noarch ovirt-provider-ovn-driver-1.2.2-1.el7.centos.noarch ovirt-hosted-engine-setup-2.2.3-1.el7.centos.noarch ovirt-imageio-common-1.2.0-1.el7.centos.noarch ovirt-host-4.2.0-1.el7.centos.x86_64 ovirt-engine-sdk-python-3.6.9.1-1.el7.noarch ovirt-engine-appliance-4.2-20171219.1.el7.centos.noarch ovirt-hosted-engine-ha-2.2.2-1.el7.centos.noarch cockpit-ovirt-dashboard-0.11.3-0.1.el7.centos.noarch ovirt-vmconsole-1.0.4-1.el7.noarch ovirt-release42-4.2.0-1.el7.centos.noarch ovirt-vmconsole-host-1.0.4-1.el7.noarch ovirt-setup-lib-1.1.4-1.el7.centos.noarch python-ovirt-engine-sdk4-4.2.2-2.el7.centos.x86_64 ovirt-imageio-daemon-1.2.0-1.el7.centos.noarch
I can confirm that if the bond is renamed to 'bond0' the install works, so I would say it's a problem with passing bonded interface names that don't start with 'bond'.
Based on the discussion in https://lists.ovirt.org/pipermail/users/2018-January/086090.html: Keeping the "bond" prefix compulsory the setup routines should check this before starting to install. This would apply to a package based and node install.