multinode template does not work with OVN when control and network are not the same nodes

[Mattia Belluco]

The deployment of kolla-ansible fails when the multinode inventory file lists separate nodes as [control] and [network]: ovn-northd,ovn-sb-db, ovn-nb-db containers did not get deployed.

We could make it work by changing
[ovn-database:children]
control

to

[ovn-database:children]
network

**Environment**:
* OS (e.g. from /etc/os-release): Ubuntu Focal
* Kernel (e.g. `uname -a`): 5.4.0
* Docker version if applicable (e.g. `docker version`): 20.10.07
* Kolla-Ansible version 11.0.0
* Docker image Install type (source/binary): source
* Docker image distribution: Ubuntu
* Are you using official images from Docker Hub or self built? Docker Hub
* Share your inventory file, globals.yml and other configuration files if relevant

[Mattia Belluco (blmt)]

in attachment the only "fatal" occurrences. The nodes are then skipped and no OVN containers gets deployed on the [control] group.

[Michal Nasiadka (mnasiadka)]

Can you please run latest stable/Victoria code instead of latest release from pip?

It should be already fixed there by: https://review.opendev.org/c/openstack/kolla-ansible/+/776436

[Ivan Kolemanov (ivankolemanov)]

Mattia, the fix is ok, we run the described setup with Kolla-Ansible 11.0.0 and cherry picked https://review.opendev.org/q/ec04972b728b0b78717c9d18988eda06b61ebe77

[Mattia Belluco (blmt)]

Indeed the linked commit works like a charm and we could deploy the control plane as intended, without changing the parent-children relationship in the multinode template.

Thanks for the quick reply and pointers to the solution!