Proxmox Virtual Environment 9.1 available!

Wanted to provide an update with my 9.1.2 move. I too found the ISO upload bug. Download via url is the only way to get ISOs loaded at this time. Error shown:

starting file import from: /var/tmp/pveupload-93b7660434769d3896ec263ed8f3647c
TASK ERROR: failed to stat '/var/tmp/pveupload-93b7660434769d3896ec263ed8f3647c'
Click to expand...
 
Hi,
Pouch6867 said:
Wanted to provide an update with my 9.1.2 move. I too found the ISO upload bug. Download via url is the only way to get ISOs loaded at this time. Error shown:
Click to expand...
please open a separate thread and provide more details. Is the upload done on the same node you are logged in or another one? Is there any information in the system logs/journal? Note that 9.1.2 is not the latest available version (anymore).
 
fiona said:
Hi,

please open a separate thread and provide more details. Is the upload done on the same node you are logged in or another one? Is there any information in the system logs/journal? Note that 9.1.2 is not the latest available version (anymore).
Click to expand...
doesn't look like it's needed. 9.1.4 fixed whatever bug it was.
 
SteveITS said:
https://pve.proxmox.com/wiki/Upgrade_from_8_to_9 does not mention QDevice that I see...is there a need and/or recommended process to upgrade that? Just upgrade it to Trixie also?
Click to expand...
Imho this should be enough since the qdevice daemon by design lightweight and configuration-less, so I would expect a flawless upgrade:
QDevice Technical Overview
The Corosync Quorum Device (QDevice) is a daemon which runs on each cluster node. It provides a configured number of votes to the cluster’s quorum subsystem, based on an externally running third-party arbitrator’s decision. Its primary use is to allow a cluster to sustain more node failures than standard quorum rules allow. This can be done safely as the external device can see all nodes and thus choose only one set of nodes to give its vote. This will only be done if said set of nodes can have quorum (again) after receiving the third-party vote.

Currently, only QDevice Net is supported as a third-party arbitrator. This is a daemon which provides a vote to a cluster partition, if it can reach the partition members over the network. It will only give votes to one partition of a cluster at any time. It’s designed to support multiple clusters and is almost configuration and state free. New clusters are handled dynamically and no configuration file is needed on the host running a QDevice.

The only requirements for the external host are that it needs network access to the cluster and to have a corosync-qnetd package available. We provide a package for Debian based hosts, and other Linux distributions should also have a package available through their respective package manager.

Note Unlike corosync itself, a QDevice connects to the cluster over TCP/IP. The daemon can also run outside the LAN of the cluster and isn’t limited to the low latencies requirements of corosync.

https://pve.proxmox.com/wiki/Cluster_Manager#_corosync_external_vote_support
Click to expand...

Maybe there are some edgecases not mentioned in the docs or I'm not aware of but I can't remember any discussion of problems with the corosync-qnetd daemon (which is used to provide the service on the qdevice-node) regarding the update from PVE8 to 9 and from Debian Bookworm to Trixie.

Propably you could even get away with waiting longer before updating the qdevice to trixie (although to be honest I don't see much of a point in it, ymmv)

In my two-node cluster in my homelab I didn't had any problems either, but of course one example in a homelab doesn't say much.
 
You must log in or register to reply here.
Top Bottom
Back