daviftorres commented on issue #10884:
URL: https://github.com/apache/cloudstack/issues/10884#issuecomment-3020312833
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.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
