From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 2EF0E1FF17E for ; Thu, 2 Oct 2025 23:10:42 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 264F417C2D; Thu, 2 Oct 2025 23:10:45 +0200 (CEST) From: Marco Gaiarin Date: Thu, 2 Oct 2025 12:54:11 +0200 Organization: Il gaio usa sempre TIN per le liste, fallo anche tu!!! Message-ID: X-Trace: eraldo.lilliput.linux.it 1759437403 2014936 192.168.1.45 (2 Oct 2025 20:36:43 GMT) X-Mailer: tin/2.6.4-20240224 ("Banff") (Linux/6.14.0-33-generic (x86_64)) X-Gateway-System: SmartGate 1.4.5 To: pve-user@lists.proxmox.com X-SPAM-LEVEL: Spam detection results: 0 AWL -0.431 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DATE_IN_PAST_06_12 1.543 Date: is 6 to 12 hours before Received: date DMARC_PASS -0.1 DMARC pass policy JMQ_SPF_NEUTRAL 0.5 SPF set to ?all KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_PASS -0.001 SPF: HELO matches SPF record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [PVE-User] Again (not) renaming interfaces... X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE user list MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-user-bounces@lists.proxmox.com Sender: "pve-user" 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: mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 5: eno1: mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 10: bond0: mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000 root@pppve2:~# ip link | grep bond1 6: eno2: mtu 1500 qdisc mq master bond1 state UP mode DEFAULT group default qlen 1000 12: bond1: mtu 1500 qdisc noqueue master vmbr1 state UP mode DEFAULT group default qlen 1000 root@pppve2:~# ip link | grep bond2 4: ens5f0np0: mtu 9000 qdisc mq master bond2 state UP mode DEFAULT group default qlen 1000 7: ens5f1np1: mtu 9000 qdisc mq master bond2 state UP mode DEFAULT group default qlen 1000 9: bond2: 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: 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: mtu 1500 qdisc mq master bond1 state UP mode DEFAULT group default qlen 1000 6: eno2: mtu 1500 qdisc mq master bond1 state UP mode DEFAULT group default qlen 1000 12: bond1: 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