pve-firewall version not in pveversion

Thanks @dietmar. Including it in PVE 3.4x would be useful for reference while troubleshooting.

I see that it is included in line 543 in PVE 4.1's APT.pm file.

For those who want it in PVE 3.4, replace line 536 in it's /usr/share/perl5/API2/APT.pm:
Code:
    push @list, qw(lvm2 clvm corosync-pve openais-pve libqb0 redhat-cluster-pve resource-agents-pve fence-agents-pve pve-cluster qemu-server pve-firmware libpve-common-perl libpve-access-control libpve-storage-perl pve-libspice-server1 vncterm vzctl vzprocps vzquota pve-qemu-kvm ksm-control-daemon glusterfs-client);
with
Code:
    push @list, qw(lvm2 clvm corosync-pve openais-pve libqb0 redhat-cluster-pve resource-agents-pve fence-agents-pve pve-cluster qemu-server pve-firmware libpve-common-perl libpve-access-control libpve-storage-perl pve-libspice-server1 vncterm vzctl vzprocps vzquota pve-qemu-kvm ksm-control-daemon glusterfs-client pve-firewall);

The /usr/bin/pveversion file is part of the pve-manager package:
Code:
# which pveversion
/usr/bin/pveversion

# dpkg -S /usr/bin/pveversion
pve-manager: /usr/bin/pveversion

It gets the package list from a line in it:
Code:
my $pkgarray = PVE::API2::APT->versions({ node => 'localhost'});

As on date (see last line) for PVE 3.4x it should show:
Code:
# pveversion -v
proxmox-ve-2.6.32: 3.4-171 (running kernel: 2.6.32-44-pve)
pve-manager: 3.4-11 (running version: 3.4-11/6502936f)
pve-kernel-2.6.32-44-pve: 2.6.32-171
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-3
pve-cluster: 3.0-19
qemu-server: 3.4-6
pve-firmware: 1.1-5
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-34
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-22
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
pve-firewall: 1.0-22
 
Last edited: