Strange behavior in dpkg with the latest update.

[Aa2vK45ketPHf4Dq]

Greetings!

I noticed some strange behavior in dpkg with the latest update.

During deployment, I received the following warnings:
dpkg: warning: unable to delete old directory '/lib/systemd/system': Directory not empty
dpkg: warning: unable to delete old directory '/lib/systemd': Directory not empty

It's strange that dpkg is trying to delete these directories—they're system directories and are still occupied.
Here's what dpkg -S /lib/systemd/system/ returns: ksm-control-daemon: /lib/systemd/system
dpkg -S /lib/systemd/: ksm-control-daemon: /lib/systemd/system.

Is this normal behavior?

On nodes where I didn't have time to deploy the update,
dpkg -S /lib/systemd/ returns: ifupdown2, ksm-control-daemon: /lib/systemd/system
The ifupdown2 package is one of those that was updated.

 

[mfederanko]

Hey, whats the pve version before and after upgrading? pveversion gives you that information.
How are you upgrading?

 

[Aa2vK45ketPHf4Dq]

Hey, whats the pve version before and after upgrading? pveversion gives you that information.
How are you upgrading?

I updated via UI from version pve-manager/9.1.5/80cf92a64bef6889 (running kernel: 6.17.4-2-pve) to pve-manager/9.1.5/80cf92a64bef6889 (running kernel: 6.17.9-1-pve).

 

[leesteken]

Looks normal if some update removed ifupdown2 from /lib/systemd. The package manager will remove the parent directories if there is nothing left in them, which is not the case. I don't think this is anything specific to Proxmox and just how Debian package management works.