[SOLVED] pve6to7 error APT.pm

[dunk1452]

Hello, I'm plagued by an error that I have had but have ignored until now since I want to upgrade to Pve7.

The output from pve6to7:

Checking for package updates..
WARN: Not an ARRAY reference at /usr/share/perl5/PVE/API2/APT.pm line 169.

FAIL: unable to retrieve list of package updates!

I've also attached the APT.pm file below.

This error is also present when trying to upgrade packages in the web UI and via pveupgrade command, I've worked around this issue by simply using apt dist-upgrade up until now.

This is the output from pveupgrade command:

root@pve:~# pveupgrade
Starting system upgrade: apt-get dist-upgrade
Not an ARRAY reference at /usr/share/perl5/PVE/API2/APT.pm line 169, <DATA> line 755.

Is this something I need to address before upgrading to Pve7?

Thanks.

 

[Dominic]

Hi,

I've worked around this issue by simply using apt dist-upgrade up until now.

So both apt update and apt dist-upgrade run flawlessly? Have you run pveupdate sometime?

 

[dunk1452]

Hi, yes apt update & apt dist-upgrade work fine.

Same problem occurs from pveupdate command:

root@pve:~# pveupdate
Not an ARRAY reference at /usr/share/perl5/PVE/API2/APT.pm line 169.

 

[fiona]

Hi,
can you share the output of pveversion -v and cat /var/lib/pve-manager/pkgupdates?

 

[dunk1452]

root@pve:~# pveversion -v
proxmox-ve: 6.4-1 (running kernel: 5.11.21-1-pve)
pve-manager: 6.4-13 (running version: 6.4-13/9f411e79)
pve-kernel-5.11: 7.0-2~bpo10
pve-kernel-5.4: 6.4-4
pve-kernel-helper: 6.4-4
pve-kernel-5.11.21-1-pve: 5.11.21-1~bpo10
pve-kernel-5.11.17-1-pve: 5.11.17-1~bpo10
pve-kernel-5.4.124-1-pve: 5.4.124-1
pve-kernel-5.4.78-2-pve: 5.4.78-2
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.2-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve4~bpo10
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.1.0-1
libpve-access-control: 6.4-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-3
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-3
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.12-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.6-1
pve-cluster: 6.4-1
pve-container: 3.3-6
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-4
pve-firmware: 3.2-4
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1

Hmm looks like an issue with this one?

root@pve:~# cat /var/lib/pve-manager/pkgupdates
{}root@pve:~#

 

[fiona]

You should be fine after simply removing this file, it'll be re-created as needed. It's just for caching available updates, but seems like the empty JSON object {} instead of the empty JSON array [] got written to it for some reason, causing the problem. I'll try to find out where.

 

[dunk1452]

Ah yes! xD that seems to have fixed things.

root@pve:/var/lib/pve-manager# pveupdate
root@pve:/var/lib/pve-manager# pveupgrade
Starting system upgrade: apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Your System is up-to-date

root@pve:/var/lib/pve-manager# pve6to7 --full
= CHECKING VERSION INFORMATION FOR PVE PACKAGES =

Checking for package updates..
PASS: all packages uptodate

Checking proxmox-ve package version..
PASS: proxmox-ve package has version >= 6.4-1

Checking running kernel version..
PASS: expected running kernel '5.11.21-1-pve'.

= CHECKING CLUSTER HEALTH/SETTINGS =

SKIP: standalone node.

= CHECKING HYPER-CONVERGED CEPH STATUS =

SKIP: no hyper-converged ceph setup detected!

= CHECKING CONFIGURED STORAGES =

PASS: storage 'btrfs' enabled and active.
PASS: storage 'btrfs-pve-bs' enabled and active.
PASS: storage 'local' enabled and active.
PASS: storage 'local-lvm' enabled and active.

= MISCELLANEOUS CHECKS =

INFO: Checking common daemon services..
PASS: systemd unit 'pveproxy.service' is in state 'active'
PASS: systemd unit 'pvedaemon.service' is in state 'active'
PASS: systemd unit 'pvestatd.service' is in state 'active'
INFO: Checking for running guests..
WARN: 3 running guest(s) detected - consider migrating or stopping them.
INFO: Checking if the local node's hostname 'pve' is resolvable..
INFO: Checking if resolved IP is configured on local node..
PASS: Resolved node IP '192.168.1.7' configured and active on single interface.
INFO: Checking backup retention settings..
PASS: no problems found.
INFO: checking CIFS credential location..
PASS: no CIFS credentials at outdated location found.
INFO: Checking custom roles for pool permissions..
INFO: Checking node and guest description/note legnth..
PASS: All node config descriptions fit in the new limit of 64 KiB
PASS: All guest config descriptions fit in the new limit of 8 KiB
INFO: Checking container configs for deprecated lxc.cgroup entries
PASS: No legacy 'lxc.cgroup' keys found.
INFO: Checking storage content type configuration..
PASS: no problems found
INFO: Checking if the suite for the Debian security repository is correct..
INFO: Make sure to change the suite of the Debian security repository from 'buster/updates' to 'bullseye-security' - in /etc/apt/sources.list:10
INFO: Make sure to change the suite of the Debian security repository from 'buster/updates' to 'bullseye-security' - in /etc/apt/sources.list:12

= SUMMARY =

TOTAL:    20
PASSED:   17
SKIPPED:  2
WARNINGS: 1
FAILURES: 0

ATTENTION: Please check the output for detailed information!

Thanks for the help!