--- Begin Message ---
Hi Marco,
October 2, 2025 at 12:54 PM, "Marco Gaiarin" <[email protected]
mailto:[email protected]?to=%22Marco%20Gaiarin%22%20%3Cgaio%40lilliput.linux.it%3E
> wrote:
>
> Some servers, all upgraded from PVE6 to PVE7 and then PVE8.
>
> Still i have some server Dell PowerEdge T440 that, sometime, not ever, fail
> to rename interfaces, some log:
>
> Oct 2 11:44:03 pppve2 (udev-worker)[891]: lo: Invalid network interface
> name, ignoring:
> Oct 2 11:44:03 pppve2 (udev-worker)[869]: eth1: Could not set
> AlternativeName= or apply AlternativeNamesPolicy=, ignoring: File exists
> Oct 2 11:44:03 pppve2 (udev-worker)[869]: ens1f1: Failed to rename network
> interface 3 from 'eth1' to 'ens1f1': File exists
> Oct 2 11:44:03 pppve2 (udev-worker)[869]: ens1f1: Failed to process device,
> ignoring: File exists
> Oct 2 11:44:03 pppve2 (udev-worker)[899]: eno1: Could not set
> AlternativeName= or apply AlternativeNamesPolicy=, ignoring: File exists
>
> clearly, ifup2 does not found ens1f1 and don't bind the interface to the
> bond.
>
> I need to check manually the bond:
>
> root@pppve2:~# mailto:root@pppve2:~# ip link | grep bond0
> 2: ens1f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master
> bond0 state UP mode DEFAULT group default qlen 1000
> 5: eno1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master
> bond0 state UP mode DEFAULT group default qlen 1000
> 10: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue
> master vmbr0 state UP mode DEFAULT group default qlen 1000
> root@pppve2:~# mailto:root@pppve2:~# ip link | grep bond1
> 6: eno2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master
> bond1 state UP mode DEFAULT group default qlen 1000
> 12: bond1: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue
> master vmbr1 state UP mode DEFAULT group default qlen 1000
> root@pppve2:~# mailto:root@pppve2:~# ip link | grep bond2
> 4: ens5f0np0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq
> master bond2 state UP mode DEFAULT group default qlen 1000
> 7: ens5f1np1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq
> master bond2 state UP mode DEFAULT group default qlen 1000
> 9: bond2: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 9000 qdisc noqueue
> state UP mode DEFAULT group default qlen 1000
>
> find missing interface:
>
> root@pppve2:~# mailto:root@pppve2:~# ip link | grep eth[0-9]
> 3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master
> bond1 state UP mode DEFAULT group default qlen 1000
>
> and manually bind them:
>
> root@pppve2:~# mailto:root@pppve2:~# ip link set eth1 master bond1
> root@pppve2:~# mailto:root@pppve2:~# ip link | grep bond1
> 3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master
> bond1 state UP mode DEFAULT group default qlen 1000
> 6: eno2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master
> bond1 state UP mode DEFAULT group default qlen 1000
> 12: bond1: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue
> master vmbr1 state UP mode DEFAULT group default qlen 1000
>
> Why? It is better to fire up a bug?
>
No, that is the usual thing to do when upgrading. ;) Till PVE9 at least, the
pinning tool should help you there.
https://pve.proxmox.com/pve-docs/pve-admin-guide.html#network_pin_naming_scheme_version
Cheers,
Alwin
--- End Message ---
