Description of problem: When running ovirt-hosted-engine-setup on hosts (CentOS 6.5) with VLAN tagged interfaces it fails with the following error message: 2014-02-25 15:35:20 INFO otopi.plugins.ovirt_hosted_engine_setup.network.bridge bridge._misc:189 Configuring the management bridge 2014-02-25 15:35:20 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/network/bridge.py", line 194, in _misc ].s.getVdsCapabilities()['info']['nics'][nics] KeyError: 'eth0.200' Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-1.1.0-1.el6.noarch How reproducible: Trying to use vlan tagged interface as ovirtmgmt network in ovirt-hosted-engine-setup Steps to Reproduce: 1. Install CentOS 6.5 with vlan tagged interface (e.g. eth0.200) 2. Run ovirt-hosted-engine-setup and choose interface eth0.200 for ovirtmgmt interface Actual results: ovirt-hosted-engine-setup fails with error message posted above Expected results: Create ovirtmgmt-interface with VLAN tag Additional info: If I remove the VLAN tag setup is working fine, but if you need VLAN tags you have to do the following to make it work: - Set switch port to untagged for this VLAN - Configure eth0 instead of eth0.200 - Run hosted engine setup - Configure VLAN for ovirtmgmt in oVirt (which surprisingly worked for an active interface) - Configure VLAN tagging on hosts - Reconfigure switch ports - Sync networks in oVirt network setup tab Adding support for VLAN tagged interfaces into ovirt-hosted-engine-setup would make live much easier.
Rene, thanks for both the report and the provided workaround!
marking this bug as verified, since the particular issue described in this BZ is fixed in beta of ovirt 3.5. End to end testing of whole self hosted engine over VLAN interface will be performed in bug 1076944.
oVirt 3.5 has been released and should include the fix for this issue.