Description of problem: It looks like since today (I'm using latest ISO ovirt-node-ng-installer-ovirt-4.2-pre-2017120512) I cannot create a vm which will be the node (on 192.168.0.102) and the HE on 192.168.0.101 Version-Release number of selected component (if applicable): 2.2.0 How reproducible: Always Steps to Reproduce: 1. build a VM and install the ISO, set the IP on 192.168.0.101 (for example) 2. Either through web gui or cli (by running ovirt-hosted-engine-setup) give a hostname (that is written in DNS) like ovirt.home with IP 192.168.0.102 3. You'll see error message Actual results: [ ERROR ] The Engine VM (192.168.0.101/32) and this host (192.168.0.102/32) will not be in the same IP subnet. Static routing configuration are not supported on automatic VM configuration. Expected results: It should work. tons of places cannot create different subnets or vlans. If this is a correct behavior, then it should be an option, not mandatory. I'm just trying to install the Node, the HE, and record a youtube video on the upcoming version. Now I can't do that..
I tried to reformat the machine and reinstall the latest snapshot ISO. Surprise, it worked...
And I think I found the bug.. Using the web UI, when configuring everything, the VM engine IP that I'm entering - doesn't get any subnet (while the host itself has the correct /24 subnet), so the HE engine install failed. running the ovirt-hosted-engine-setup through terminal, the script adds the /24 to the HE VM and it seems to work.
*** This bug has been marked as a duplicate of bug 1522712 ***