you can do a "brctl show" on the node where the lxc ct does not start ? Do you have same problem with a vm ? (This look like the vnet bridge is not created on the host, but you should have an error when applying sdn configuration).Hi all,
i've just started with playing around with the SDN software and reading this thread not sure if this is a bug, or operator error,
however I ran into the following
I have two nodes in a cluster
I tried setting up a vxlan using the same controller and this all worked and I saw VNET1 appear on all nodes
I subsequently tried setting up bgp evpn which I could push no issues and i see VNET02 appear on all nodes, however when I then tries to bind the new vnet to a container I get an error:
run_buffer: 314 Script exited with status 2
lxc_create_network_priv: 3068 No such device - Failed to create network device
lxc_spawn: 1786 Failed to create the network
__lxc_start: 1999 Failed to spawn container "147"
TASK ERROR: startup for container '147' failed
So i figured maybe as this is a beta this might be a bug and i reverted the configuration back to VXLAN only, using VNET1 and the above error remains. I can now only use default bridges on both my nodes.
I have removed both ovswitch and the perl script however the error remains. Is this a known issue? or is this just me being daft somehow?
Happy to help push this functionality further as it is indeed pretty brilliant,
do you use proxmox 6.4 with last update ?