[SOLVED] Glitch / possible bug in webUI (updates)

[n0x0n]

Hi all,
there's a glitch I found that's possibly a bug.
I replaced postfix with nullmailer, both provide mail-transport-agent.
postfix is in state 'removed' (rc in dpkg terms). No other packages changed / installed / removed.

Looking at updates I found this:



apt list --upgradable does not show that postfix will be installed / updated. Performing the upgrade did not install postfix (as expected).
No reverse deps either:

n0x0n@pve:~# apt-cache rdepends --no-{suggests,conflicts,breaks,replaces,enhances} --installed --recurse postfix
postfix
Reverse Depends:
 |pve-manager
 |pve-manager
 |pve-manager
 |pve-manager
 |pve-manager
 |pve-manager
 |pve-manager
 |pve-manager
 |pve-manager
 |pve-manager
 |pve-manager
 |pve-manager
 |pve-manager
 |pve-manager
 |pve-manager
 |pve-manager
 |pve-manager
 |pve-manager
 |pve-manager
pve-manager
Reverse Depends:
  proxmox-ve
  proxmox-ve
proxmox-ve
Reverse Depends:
n0x0n@pve:~#

May this be a bug and if so, how can I help track it down?

 

[fiona]

Hi,
please share the contents of /var/lib/pve-manager/pkgupdates and pveversion -v. Can it be that there was an update for postfix available before it got removed?

 

[n0x0n]

Can it be that there was an update for postfix available before it got removed?

I don't think so, because the latest version in buster is 3.4.14-0+deb10u1 and that's what I had when removing. I had installed pve 6 first quarter of last year and replaced postfix directly after installation. dpkg still shows the old buster version (pve 6 = buster has postfix (3.4.14-0+deb10u1)):
rc postfix 3.4.14-0+deb10u1 amd64 High-performance mail transport agent

Shortly after it became available, I upgraded to pve 7 = bullseye which has postfix (3.5.6-1).

# cat /var/lib/pve-manager/pkgupdates
[]

pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-8
pve-kernel-5.13: 7.1-6
pve-kernel-5.11: 7.0-10
pve-kernel-5.4: 6.4-5
pve-kernel-5.13.19-3-pve: 5.13.19-6
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-4-pve: 5.11.22-9
pve-kernel-5.4.128-1-pve: 5.4.128-2
pve-kernel-5.4.106-1-pve: 5.4.106-1
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-2
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.0-15
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-1
proxmox-backup-client: 2.1.3-1
proxmox-backup-file-restore: 2.1.3-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-5
pve-cluster: 7.1-3
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-4
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-pve2
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1

 

[n0x0n]

@Fabian_E : Anything else I can do to help track this down?

 

[fiona]

Sorry, I put this on my TODO-list, but hadn't come back around to it yet. Here is a patch that should fix the issue. Thanks for reporting!

 

[n0x0n]

Hi @Fabian_E, no worries, reporting bugs is my way to contribute
Thank you for the patch and have a good week!