GitHub user bhouse-nexthop closed the discussion with a comment: Bridge interface not recognized for newly added host if they don't have a physical interface attached
my preference would be deference to the sysadmin setting this up. If the bridge is configured and its in an up state, good enough. Sysadmins not really capable of that are probably using Proxmox instead ;) I'm surprised I haven't hit his earlier, I run a pure L3 environment where there's only a vxlan on the bridge and no other interfaces, so there must be some conditional logic allowing vx* or something too? No matter what relying on naming would never be a good strategy as there is no enforced naming convention. It was only when trying to set something up at the office with a switch that wasn't vxlan capable where we had to expose a couple of vlans that we hit this. I'd need to browse through the code. But it was frustrating as we couldn't find any mention of the actual error in the logs (granted we were running at stock log levels which are already pretty verbose) GitHub link: https://github.com/apache/cloudstack/discussions/10804#discussioncomment-14109837 ---- This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
