This issue is reproducible using 2+2 and Duplex configurations Bare Metal
We also observed the following behavior:
* Besides Horizon reports the proper creation of the VMs, and it shows an assigned IP, the VM console can't be opened via Horizon.
*Once that we be able to open the console, using 2 different methods (virsh console and port forwarding / tunneling), we figured out, that the VMs doesn't have an IP assigned for the eth0 interface. I believe this is issue is already described here: https://bugs.launchpad.net/starlingx/+bug/1820378
* We assigned manually the IP to each one of the VMs, and tried the ping without success.
This issue is reproducible using 2+2 and Duplex configurations Bare Metal
We also observed the following behavior:
* Besides Horizon reports the proper creation of the VMs, and it shows an assigned IP, the VM console can't be opened via Horizon.
*Once that we be able to open the console, using 2 different methods (virsh console and port forwarding / tunneling), we figured out, that the VMs doesn't have an IP assigned for the eth0 interface. I believe this is issue is already described here: https:/ /bugs.launchpad .net/starlingx/ +bug/1820378
* We assigned manually the IP to each one of the VMs, and tried the ping without success.