GitHub user weizhouapache added a comment to the discussion: Net Creation Fails on Second KVM Host Due to Invalid Bridge Name Format
> We encountered the same issue described in the linked thread, with an > identical environment, host OS, and network setup. The suggested workaround > worked for us, so we're sharing our configuration below as a reference for > others: > > ``` > network: > version: 2 > ethernets: > eth0: > match: > name: enp3s0f0 > set-name: eth0 > eth1: > match: > name: enp3s0f1 > set-name: eth1 > eth2: > match: > name: enp4s0f0 > set-name: eth2 > eth3: > match: > name: enp4s0f1 > set-name: eth3 > bridges: > cloudbr0: > <redacted> > interfaces: > - eth0 > cloudbr1: > <redacted> > interfaces: > - eth3 > cloudbr2: > <redacted> > interfaces: > - eth2 > ``` > > Important note: Applying this configuration on a running system will likely > cause failures—System VMs and Virtual Routers will need to be restarted. > > Recommendation: Make these changes during a scheduled maintenance window, > ideally before applying patches or upgrading CloudStack components. This way, > you can take advantage of the required restarts of the Agent and/or > Management services. > > Additionally: This approach allows you to standardize interface names (e.g., > eth0, eth1) across all nodes and clusters. It helps avoid unnecessary stress > during NIC replacements in production, where a new interface might otherwise > be assigned a different name. thanks @daviftorres for the sharing in our testing environments, we use `net.ifnames=0 biosdevname=0` in the grub config, all the servers (ubuntu, debian, rhel variants) use ethX. it makes configuration easier GitHub link: https://github.com/apache/cloudstack/discussions/11148#discussioncomment-13680173 ---- This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
