Description of problem:
When self hosted engine is being deployed over VLAN it leads to situation when physical host is being made non-operational in the engine because hosts network is out of sync from cluster settings.
It is caused by engine-setup deploying engine with management network which does not have VLAN tag by default.
Self hosted engine should take care of this in the final configuration stage (after user confirms that engine is installed)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. configure VLAN tagged interface on physical host
2. yum install ovirt-hosted-engine-setup
3. ovirt-hosted-engine-setup --deploy
4. choose the VLAN interface to be used for deployment
5. finish the deployment
physical host is non-operational in self hosted engine GUI
physical host is UP (ovirt-hosted-engine-setup --deploy takes care of configuring management network as VLAN tagged)
at the moment host can be made operational by manual adjustment of management network in self hosted engine, however it must be VERY inconvenient for new users
this would be worth documenting in Installation_Guide/Installing_the_Self-Hosted_Engine.html
*** Bug 1124206 has been marked as a duplicate of this bug. ***
Antoni, is this case covered by your patch at http://gerrit.ovirt.org/28595 ?
My patch improves the configuration of the vdsm side. IIUC Martin talks about the problem that the engine representation of the ovirtmgmt network is not configured as vlanned, thus leading to the out-of-sync issue.
This should either be solved by configuring the engine ovirtmgmt network to be vlanned when configuring the hosted engine over a vlan or, perhaps in the future, not caring for more than connectivity for the management network (in terms of syncing).
Verified on -3.5.0-0.14.beta.el6ev and ovirt-hosted-engine-setup-1.2.1-1.el6ev.noarch
oVirt 3.5 has been released and should include the fix for this issue.