Upgrading issue from 5.4-15 tot 6.0

Theo Lodewijk

Member
Jul 21, 2020
4
0
6
39
Hello, I have some issues about upgrading proxmox.

Here is the full command line for updating.

https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0
systemctl stop pve-ha-lrm
systemctl stop pve-ha-crm
echo "deb http://download.proxmox.com/debian/corosync-3/ stretch main" > /etc/apt/sources.list.d/corosync3.list
apt update
apt dist-upgrade --download-only
error form here --> apt dist-upgrade


root@node2:~# pve5to6
Checking proxmox-ve package version..
PASS: proxmox-ve package has version >= 5.4-2

Checking running kernel version..
PASS: expected running kernel '4.15.18-30-pve'.

Checking for installed stock Debian Kernel..
PASS: Stock Debian kernel package not installed.

= CHECKING CLUSTER HEALTH/SETTINGS =

SKIP: standalone node.

= CHECKING HYPER-CONVERGED CEPH STATUS =

SKIP: no hyper-converged ceph setup detected!

= CHECKING CONFIGURED STORAGES =

PASS: storage 'n2s1' enabled and active.
PASS: storage 'local' enabled and active.
PASS: storage 'hdd' enabled and active.
SKIP: storage 'local-lvm' disabled.

= 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..
PASS: no running guest detected.
INFO: Checking if the local node's hostname 'node2' is resolvable..
INFO: Checking if resolved IP is configured on local node..
PASS: Resolved node IP '5.178.67.118' configured and active on single interface.
INFO: Check node certificate's RSA key size
PASS: Certificate 'pve-root-ca.pem' passed Debian Busters security level for TLS connections (4096 >= 2048)
PASS: Certificate 'pve-ssl.pem' passed Debian Busters security level for TLS connections (2048 >= 2048)
INFO: Checking KVM nesting support, which breaks live migration for VMs using it..
PASS: KVM nested parameter not set.
INFO: Checking VMs with OVMF enabled and bad efidisk sizes...
PASS: No VMs with OVMF and problematic efidisk found.

= SUMMARY =

TOTAL: 19
PASSED: 15
SKIPPED: 3
WARNINGS: 1
FAILURES: 0



489 upgraded, 110 newly installed, 14 to remove and 0 not upgraded.
Need to get 0 B/237 MB of archives.
After this operation, 253 MB of additional disk space will be used.
Do you want to continue? [Y/n]
W: (pve-apt-hook) !! WARNING !!
W: (pve-apt-hook) You are attempting to remove the meta-package 'proxmox-ve'!
W: (pve-apt-hook)
W: (pve-apt-hook) If you really want to permanently remove 'proxmox-ve' from your system, run the following command
W: (pve-apt-hook) touch '/please-remove-proxmox-ve'
W: (pve-apt-hook) run apt purge proxmox-ve to remove the meta-package
W: (pve-apt-hook) and repeat your apt invocation.
W: (pve-apt-hook)
W: (pve-apt-hook) If you are unsure why 'proxmox-ve' would be removed, please verify
W: (pve-apt-hook) - your APT repository settings
W: (pve-apt-hook) - that you are using 'apt full-upgrade' to upgrade your system
E: Sub-process /usr/share/proxmox-ve/pve-apt-hook returned an error code (1)
E: Failure running script /usr/share/proxmox-ve/pve-apt-hook
 
This sounds like some repositories are not configured correctly and thus package dependencies go a bit crazy.

Can you show the output of apt update?
 
  • Like
Reactions: Theo Lodewijk
Where is the regular Proxmox VE repository? I don't see any call to the no-subscription or enterprise repo. Only the intermediate Corosync3 Repository.

You should have one of these repositories configured. Which depends on if you have a subscription:
Code:
deb https://enterprise.proxmox.com/debian/pve buster pve-enterprise
deb http://download.proxmox.com/debian/pve buster pve-no-subscription

See https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_package_repositories