all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Marco Gaiarin <gaio@lilliput.linux.it>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] Again (not) renaming interfaces...
Date: Thu, 2 Oct 2025 12:54:11 +0200	[thread overview]
Message-ID: <h722rl-bj51.ln1@leia.lilliput.linux.it> (raw)


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:~# 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:~# 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:~# 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:~# 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:~# ip link set eth1 master bond1
 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?


Thanks.

-- 



_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user


             reply	other threads:[~2025-10-02 21:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02 10:54 Marco Gaiarin [this message]
2025-10-06 12:10 ` Alwin Antreich via pve-user

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=h722rl-bj51.ln1@leia.lilliput.linux.it \
    --to=gaio@lilliput.linux.it \
    --cc=pve-user@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal