Just wanted to provide an update, it seems the issue is resolved for me in the latest round of commits.

@olivierlambert I activated the trial and imported my configuration from xo, making sure the perf-alert plugin was enabled/configured. I have not received any hanging tasks in XOA.

@olivierlambert Will do. Plugins are disabled and I'm updating back to master right now. Will report back.

@stormi Follow up on the steps I took to possibly help others that may have similar scenarios.

1. Migrated all VM's off of my Master (Node1) and rebooted, upgraded to 8.3 from ISO still on BIOS mode.
2. Once Node1 was back online, I went ahead and upgraded Node2, and Node3 one at a time. I would just move my current VM's around to the host I wasn't upgrading. Finally had all 3 hosts on 8.3.
3. Started the UEFI transition. I started with Node1 which was the master, but I changed the master to be on Node3. I went ahead and migrated all the VM's off the Node1, shutdown, pull the HDD (So I would have a backup) and put a new HDD in. Changed my boot mode to UEFI and did a fresh install. I removed Node1 from the cluster in XO. Once back online, I went ahead and just added Node1 back into my cluster and let XO do its magic of bringing everything back online.

Only issue I ran into was a POOL_JOINING_HOST_TLS_VERIFICATION_MISMATCH when I attempted to add the Node1 to the cluster. I followed the steps listed here: https://xcp-ng.org/forum/post/63470

Running xe pool-enable-tls-verification and xe host-emergency-reenable-tls-verification on Node3 which was still the master and was then able to get the new server added to the pool.

4. Moved the master back to Node1 and started the process over again on Node2 and 3.

@MathieuRA Thanks for the quick response and for flagging it, really appreciate it! No rush at all. Thank you for all the hard work being put into the REST API, it's been fantastic.

Currently the REST API (/rest/v0) has no endpoint for updating VM properties such as name_description or name_label from what I can find. The only available VM actions are
lifecycle operations (start, shutdown, reboot, snapshot, etc.).

Use case: I'm running an n8n automation that collects a list of active Docker containers running in different VM's, and I want to write that summary back to the VM's description field in XO — giving a live "what's running here" view directly in the XO UI without needing a separate dashboard. Would love to see this added.

@stormi Follow up on the steps I took to possibly help others that may have similar scenarios.

1. Migrated all VM's off of my Master (Node1) and rebooted, upgraded to 8.3 from ISO still on BIOS mode.
2. Once Node1 was back online, I went ahead and upgraded Node2, and Node3 one at a time. I would just move my current VM's around to the host I wasn't upgrading. Finally had all 3 hosts on 8.3.
3. Started the UEFI transition. I started with Node1 which was the master, but I changed the master to be on Node3. I went ahead and migrated all the VM's off the Node1, shutdown, pull the HDD (So I would have a backup) and put a new HDD in. Changed my boot mode to UEFI and did a fresh install. I removed Node1 from the cluster in XO. Once back online, I went ahead and just added Node1 back into my cluster and let XO do its magic of bringing everything back online.

Only issue I ran into was a POOL_JOINING_HOST_TLS_VERIFICATION_MISMATCH when I attempted to add the Node1 to the cluster. I followed the steps listed here: https://xcp-ng.org/forum/post/63470

Running xe pool-enable-tls-verification and xe host-emergency-reenable-tls-verification on Node3 which was still the master and was then able to get the new server added to the pool.

4. Moved the master back to Node1 and started the process over again on Node2 and 3.

Needing some assistance on where to start with the upgrade. I want to upgrade my 3-node cluster. As of right now all 3 nodes are on 8.2.1 but are BIOS boot, and it appears you need UEFI for 8.3 RC1. What is the best way to go about upgrading to where I wont lose data/vm’s? Understand I will most likely need to do a fresh install on each host.. What’s recommended? Should I start with the node that holds the master first on doing the fresh install?

Spoke too soon. Still getting them... Just much slower and father apart.. about 5-10 a day

Just wanted to provide an update, it seems the issue is resolved for me in the latest round of commits.

@olivierlambert I disabled perf-alert and restarted toolstack and let it sit for a while, no hanging tasks.

@olivierlambert I realized I was on the stable release... After updating to latest release I definately have hanging tasks

@olivierlambert I activated the trial and imported my configuration from xo, making sure the perf-alert plugin was enabled/configured. I have not received any hanging tasks in XOA.

@rmarion Im registered but dont have a license. Dont really want to use up the free trial, and it still only shows the two plugins. So maybe someone else can test.