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):
3.5
How reproducible:
100%
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
Actual results:
physical host is non-operational in self hosted engine GUI
Expected results:
physical host is UP (ovirt-hosted-engine-setup --deploy takes care of configuring management network as VLAN tagged)
Additional info:
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
Comment 3Antoni Segura Puimedon
2014-08-08 13:51:44 UTC
@Sandro,
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).