You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just had the problem that durining initial installation the NIC was detected as ETH4 but after the first reboot the NIC was ETH0. So the load order of modules / race conditons etc. influence the NIC naming.
To persist this properly we have been creating udev rules based on PCI bus ID / SysFS or other ways (tried to avoid MAC addresses, because they change when NICs are replaced in existing devices).
-> could we get some sort of "create udev persistence" for the NICs NMC is configuring to avoid problems in case NICS are added / removed / replaced?
The text was updated successfully, but these errors were encountered:
Just had the problem that durining initial installation the NIC was detected as ETH4 but after the first reboot the NIC was ETH0. So the load order of modules / race conditons etc. influence the NIC naming.
To persist this properly we have been creating udev rules based on PCI bus ID / SysFS or other ways (tried to avoid MAC addresses, because they change when NICs are replaced in existing devices).
-> could we get some sort of "create udev persistence" for the NICs NMC is configuring to avoid problems in case NICS are added / removed / replaced?
The text was updated successfully, but these errors were encountered: