On Fri, 2017-12-15 at 16:09 +0100, Luca 'remix_tj' Lorenzetto wrote:
On Thu, Dec 14, 2017 at 10:10 AM, Ondra Machacek <omachace@redhat.com
wrote:.
This is unfortunately a bug, David(CCed) yesterday reported same issue to me. He will (or did) open an issue on github. I will fix it for 2.5, release and hopefully also for 2.4.3.
What do you suggest to do?
I think would be nice to make the first setup of a node directly with ansible, but if is not possible i can write down some python code for some tasks.
Luca
Hi Luca, In my case (bond-vlans-bridges), the problem turned out to be missing interface parameter: - name: setup host networks: ovirt_host_networks: interface: bond0 # I missed this one bond: name: bond0 interfaces - slave1 - slave2 networks: - name: rhevm # untagged, vm_network: no boot_protocol: dhcp - name: vms # vlan_tag: TAG, vm_network: yes boot_protocol: none If the ansible + ovirt network setup doesn't work for for you (it did for me), I'd suggest to move the interfaces configuration to a separate playbook that you have to keep anyway for repositories, NTP or engine ssh key. David (working on Spice, close but not oVirt proper :))