Habe auf der selben Maschine PVE6 und PBS1.1 installiert und würde jetzt gerne upgraden. Der Server ist Mitglied in einem 3-Node-Cluster.
Reicht es aus einfach mit der empfohlenen PVE-Upgrademethode zu arbeiten oder ist hier vielleicht eine andere Reihenfolge einzuhalten?
Reicht es aus einfach mit der empfohlenen PVE-Upgrademethode zu arbeiten oder ist hier vielleicht eine andere Reihenfolge einzuhalten?
Code:
____ ____ _____ ____ __ _____ __
| _ \| _ \ / _ \ \/ / \/ |/ _ \ \/ /
| |_) | |_) | | | \ /| |\/| | | | \ /
| __/| _ <| |_| / \| | | | |_| / \
|_| |_| \_/\___/_/\_\_| |_|\___/_/\_\
https://192.168.xxx.xxx:8006
https://pvestor01.xxx.lan:8006
Last login: Sat Jul 10 22:48:05 2021 from 192.168.xxx.xxx
root@pvestor01:~# pve6to7
= CHECKING VERSION INFORMATION FOR PVE PACKAGES =
Checking for package updates..
WARN: updates for the following packages are available:
proxmox-backup-server, proxmox-backup-client, proxmox-backup-docs
Checking proxmox-ve package version..
PASS: proxmox-ve package has version >= 6.4-1
Checking running kernel version..
PASS: expected running kernel '5.4.124-1-pve'.
= CHECKING CLUSTER HEALTH/SETTINGS =
PASS: systemd unit 'pve-cluster.service' is in state 'active'
PASS: systemd unit 'corosync.service' is in state 'active'
PASS: Cluster Filesystem is quorate.
Analzying quorum settings and state..
INFO: configured votes - nodes: 3
INFO: configured votes - qdevice: 0
INFO: current expected votes: 3
INFO: current total votes: 3
Checking nodelist entries..
PASS: nodelist settings OK
Checking totem settings..
PASS: totem settings OK
INFO: run 'pvecm status' to get detailed cluster status..
= CHECKING HYPER-CONVERGED CEPH STATUS =
SKIP: no hyper-converged ceph setup detected!
= CHECKING CONFIGURED STORAGES =
SKIP: storage 'backup' disabled.
PASS: storage 'local' enabled and active.
SKIP: storage 'local-lvm' disabled.
PASS: storage 'pve01pi-zfs' enabled and active.
PASS: storage 'pvestor01nfs' enabled and active.
PASS: storage 'pvestor01pbs' 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..
PASS: no running guest detected.
INFO: Checking if the local node's hostname 'pvestor01' is resolvable..
INFO: Checking if resolved IP is configured on local node..
PASS: Resolved node IP '192.168.xxx.xxx' configured and active on single interface.
INFO: Checking backup retention settings..
INFO: storage 'local' - no backup retention settings defined - by default, PVE 7.x will no longer keep only the last backup, but all backups
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:20
SKIP: NOTE: Expensive checks, like CT cgroupv2 compat, not performed without '--full' parameter
= SUMMARY =
TOTAL: 27
PASSED: 22
SKIPPED: 4
WARNINGS: 1
FAILURES: 0
ATTENTION: Please check the output for detailed information!
Last edited:
