No dedicated uplink interfaces detected, skipping distributed networking

[dnebing]

I have 4 shiny new Ubuntu Server 22.04 mini pcs with dual NICs.

One NIC is connected to the internet to serve general traffic. The other NIC is connected to a private switch that only the 4 nodes are connected to, and each is configured to use the private NIC for traffic between the nodes.

When I did the microcloud init step, though, I got a message, No dedicated uplink interfaces detected, skipping distributed networking.

Is there some sort of preparatory step that I missed so the init step would treat the 2nd NIC as the uplink interface?

[dnebing]

I just found https://github.com/canonical/microcloud/issues/89 so it is apparently a known issue?

The thread mentions requirements for the OVN nic identification, my internal network config doesn’t apply because I have assigned IP addresses to the card.

It also hints about maybe an appropriate netplan configuration as a solution, if there is a netplan config that I can use for the card, I’d love to give it a shot…

[tomp]

Hi @dnebing
I replied to your other thread about MicroCloud networking here:

Struggling with networking

Hi @dnebing I wanted to take some time to explain how MicroCloud networking operates and hopefully correlate that to your setup. The microcloud init has two different network related phases. The first stage asks you to “Select an address for MicroCloud’s internal traffic”. This will list all network interfaces that are up and configured with an IP address. This is used for intra-cluster traffic, including MicroCloud’s own mutlicast discovery process, as well as OVN and Ceph traffic between …

Hopefully that will help to explain what is happening here.
For the OVN uplink interface they should either be a bridge or be an unused (no IPs) physical interface.