No networking on 1/3 nodes after PVE 8.4 upgrade

eroji

Renowned Member
Mar 26, 2017
8
0
66
41
I have a 3 node cluster running Minisforum MS-01 hosts, using Thunderbolt as the intra-cluster networking for Ceph. Everything was configured and working smoothly prior to recently upgrading to PVE 8.4, and kernel 6.8. I'm not exactly sure which one caused the issue, but I noticed some strange behavior on 1 of the 3 nodes. Specifically, after a reboot, the networking does not start up properly, leaving the host off the network. After logging into the host directly, I can see that networking.service did not start successfully. I checked to see if the `networking` service is enabled, which it is. Restarting networking.service does resolve the issue and brings the host back online, but this has to be done manually each reboot. I compared the configuration between the hosts but I don't see anything that differs for this particular one. Looking for some guidance on what I'm missing here.

ifupdown2.debug.log
Code:
2025-05-17 18:18:26,215: MainThread: ifupdown2: log.py:196:__init_debug_logging(): debug: persistent debugging is initialized
2025-05-17 18:18:26,232: MainThread: ifupdown2: main.py:74:main(): error: Another instance of this program is already running.
2025-05-17 18:18:26,232: MainThread: ifupdown2: log.py:373:write(): info: exit status 89
2025-05-17 18:18:26,232: MainThread: ifupdown2: log.py:381:report_error_to_systemd(): error: >>> Full logs available in: /var/log/ifupdown2/network_config_ifupdown2_126_May-17-2025_18:18:26.215835 <<<

interfaces
Code:
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

auto enp87s0
iface enp87s0 inet manual

auto enp90s0
iface enp90s0 inet manual

auto enp2s0f0np0
iface enp2s0f0np0 inet manual

auto enp2s0f1np1
iface enp2s0f1np1 inet manual

auto en05
iface en05 inet manual
        mtu 65520

iface en05 inet6 manual

iface wlp91s0 inet manual

auto en06
iface en06 inet manual
        mtu 65520

iface en06 inet6 manual

auto bond0
iface bond0 inet manual
        bond-slaves enp2s0f0np0 enp2s0f1np1
        bond-miimon 100
        bond-mode 802.3ad
#vm

auto bond1
iface bond1 inet manual
        bond-slaves enp87s0 enp90s0
        bond-miimon 100
        bond-mode balance-alb
#mgmt

auto vmbr0
iface vmbr0 inet manual
        bridge-ports bond0
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

auto vmbr1
iface vmbr1 inet static
        address 10.64.10.252/24
        gateway 10.64.10.1
        bridge-ports bond1
        bridge-stp off
        bridge-fd 0

source /etc/network/interfaces.d/*

interfaces.d/thunderbolt
Code:
auto lo:0
iface lo:0 inet static
        address 10.0.0.82/32
    
auto lo:6
iface lo:6 inet static
        address fc00::82/128

#this must always be the last line in this file
post-up /usr/bin/systemctl restart frr.service
 
Last edited: