I upgraded a bookworm/pve8 system to trixie/pve9 using dist-upgrade, and cleaned old packages using autoremove.
In addition, I purged all packages with state "rc", to get rid of all old stuff, my standard upgrade practice.
After reboot, there was no network. ifup ens8303 didn't work either: "Another instance of this program is already running". Well, no...
It turns out that ifupdown2 tries to lock "/run/network/.lock", but fails because there's no directory /run/network.
Unfortunately, mkdir /run/network won't survive a reboot, so I changed argv.py to use /run/network.lock as lockfile.
Which still didn't work after the next boot, although a manual "ifup -a" did the job just fine.
This was the moment when installed ifupdown (removing proxmox-ve...), and re-installed ifupdown2 and proxmox-ve. Now, I had the ifupdown package in rc-state, and a reboot works as expected.
It appears to me a little non-standard to have one package depending on left-overs of another uninstalled predecessor package...
In addition, I purged all packages with state "rc", to get rid of all old stuff, my standard upgrade practice.
After reboot, there was no network. ifup ens8303 didn't work either: "Another instance of this program is already running". Well, no...
It turns out that ifupdown2 tries to lock "/run/network/.lock", but fails because there's no directory /run/network.
Unfortunately, mkdir /run/network won't survive a reboot, so I changed argv.py to use /run/network.lock as lockfile.
Which still didn't work after the next boot, although a manual "ifup -a" did the job just fine.
This was the moment when installed ifupdown (removing proxmox-ve...), and re-installed ifupdown2 and proxmox-ve. Now, I had the ifupdown package in rc-state, and a reboot works as expected.
It appears to me a little non-standard to have one package depending on left-overs of another uninstalled predecessor package...