Static IP Issues

cr4sh0verride

New Member
Nov 20, 2024
6
1
3
Has anyone run into this issue before?
It was working fine and I just rebooted it after installing CEPH and now I get this

I did a pveceph purge and it's gone now but I feel something was removed that shouldn't have been

systemd[1]: Starting networking.service - Network initialization...
networking[4249]: networking: Configuring network interfaces
networking[4264]: warning: cannot load "address" module: cannot import name 'splat' from 'jaraco.functools' (/usr/lib/python3/dist-packages/jaraco/functools.py)
/usr/sbin/ifup[4264]: warning: cannot load "address" module: cannot import name 'splat' from 'jaraco.functools' (/usr/lib/python3/dist-packages/jaraco/functools.py)
systemd[1]: Finished networking.service - Network initialization.

I can't set a static IP on any interface but DHCP is working

I've done an apt update and all the packages are installed

I've looked on another one of my nodes and it doesn't have any of these python libraries installed


proxmox-ve: 8.2.0 (running kernel: 6.8.12-4-pve)
pve-manager: 8.2.10 (running version: 8.2.10/536023790079895f)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-4
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
proxmox-kernel-6.8.12-2-pve-signed: 6.8.12-2
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
ceph-fuse: 18.2.4-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.0
libpve-storage-perl: 8.2.9
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.2.9-1
proxmox-backup-file-restore: 3.2.9-1
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.1
pve-cluster: 8.0.10
pve-container: 5.2.2
pve-docs: 8.2.5
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-1
pve-ha-manager: 4.0.6
pve-i18n: 3.3.0
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.7
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1
 
Last edited:
Seems to be ifup is the issue just running this command this is the output

ifup -a
warning: cannot load "address" module: cannot import name 'splat' from 'jaraco.functools' (/usr/lib/python3/dist-packages/jaraco/functools.py)
 
Well now I fixed this by renaming the jaraco folder /usr/lib/python3/dist-packages/jaraco to jaraco-old

Now it works

Seems like that got installed with ceph and broke the ifup program, as if it exists then it will try to use it
If it doesn't then it goes on it's merry way
 
Last edited:
  • Like
Reactions: accik
Well now I fixed this by renaming the jaraco folder /usr/lib/python3/dist-packages/jaraco to jaraco-old

Now it works

Seems like that got installed with ceph and broke the ifup program, as if it exists then it will try to use it
If it doesn't then it goes on it's merry way

Thank you!!!
This method works.

I encountered a similar problem on two proxmox servers.
At the same time, I did not experiment with ceph on one server.
But on the other, yes, I experimented with ceph and then deleted it-disabled it, and probably did something wrong.
 
Holy Debian god, this was the fix for my issues as well, wow.
Had forced reboot and after that no network, renaming that folder and reboot after no issues. Lesson learned to never ignore clear errors like this, spend two evenings with this...
Thanks again.
 
Encontered that error on one of hosts in testing environment. 8.2 + ceph-quincy
Renamed folder will return on next upgrade, so is there a real fix?

Upgrading does nothing useful for this error

PS: and it break down ceph dashboard… such a pity, dashboard is usefull

UPD: I've found a good solution
Bash:
apt install -y --allow-downgrades ifupdown2=3.0.0-1.1
apt-mark hold ifupdown2
This set up unaffected version and make package to no upgrade, making further upgrades painless
Mgr, mds and dashboard on affected nodes came online after restart
 
Last edited: