Restart the toolstack on each server.

Yes, it's technically possible, as long as the underlying hardware is compatible. For example, you can't put a server using AMD processors into a pool with Intel processors.

The server being moved into the existing pool will lose its local storage and all VMs stored there, so you will need to migrate those VMs to the main pool before the server is merged. Afterwards, you can move them back if desired.

@julien-f Technically, it is possible with post processing as I mentioned above. Here's an example using jq and awk --

 xo-cli --list-objects type=VM-snapshot | jq '.[]."$snapshot_of"' | sort | uniq -c | awk -F " " '{print "{\"uuid\":" $2 ",\"count\":" $1"}"}'| jq ' select( .count > 1)'

Output looks like this --

{
  "uuid": "07604606-e937-5147-2dac-c1b4280df234",
  "count": 2
}
{
  "uuid": "0f11c701-c5e5-b09b-4c5f-00cf38153783",
  "count": 2
}
{
  "uuid": "83139da5-48d5-33f6-79f9-79ea91a7163c",
  "count": 2
}
{
  "uuid": "fb4703e4-bfd6-47b8-3fd1-f1f52f9ed234",
  "count": 2
}
{
  "uuid": "ff8b29e3-4445-5b22-e475-450270f2a7f3",
  "count": 2
}

Note: I am not proficient with these linux utilities so there may be better ways to accomplish this.

There was a recent change that resulted in the launched module being renamed. You need to redo your service so that it loads ./dist/cli.mjs instead of ./bin/xo-server

You're running out of memory. Allocate more memory to the VM. I believe the current build requirement is 3GB.

You need a space between the URL and the user name.

@stormi Updated and rebooted. I'll report back if I encounter any issues.

Updated Dell R620 / XCP-ng 8.1. Rebooting all VMs now, but they appear to be coming up just fine.

@hvilches said in XCP-ng Center 20.03.00 released:

is-a-template ( RW): true

Looks like this is the culprit...

@flipsidecreations There's a new Netdata plugin, which appears to only be available in XOA Premium edition. It doesn't appear that you will be able to enable the new Advanced Live Telemetry using the versions you are currently running.

In the thread you found, @BenjiReis indicated that this is an xcp-ng issue, not XO. Did you try installing the patches with from the CLI?

Have you checked SMlog?

FWIW, I'm seeing the same issue for a non-S3 backup. Here is what the system log shows --

May 26 00:05:06 ubuntu-xo xo-server[11563]:   error: Error: task has already ended
May 26 00:05:06 ubuntu-xo xo-server[11563]:       at Task.logAfterEnd (/opt/xen-orchestra/@xen-orchestra/backups/Task.js:7:9)
May 26 00:05:06 ubuntu-xo xo-server[11563]:       at Task.#log (/opt/xen-orchestra/@xen-orchestra/backups/Task.js:144:16)
May 26 00:05:06 ubuntu-xo xo-server[11563]:       at Task.#end (/opt/xen-orchestra/@xen-orchestra/backups/Task.js:139:14)
May 26 00:05:06 ubuntu-xo xo-server[11563]:       at Task.success (/opt/xen-orchestra/@xen-orchestra/backups/Task.js:124:14)
May 26 00:05:06 ubuntu-xo xo-server[11563]:       at /opt/xen-orchestra/@xen-orchestra/backups/Task.js:111:52

Edit: Testing with fix_health_check and appears to work correctly.

@Bane It did... just not in a user friendly manner.

Have you checked your log files to see why the VDIs aren't coalescing? In XO, you can check under Dashboard > Health to observe the VDIs pending coalesce .

@Tristis-Oris What type of backup job and how often does it run?

@peterbrunton said in Xen Orchestra Quick Deploy Fails:

md127

Pretty sure you should use md127p3 instead.

Have you reviewed this thread?

Hi Andrew,

Anything unusual in the logs?

Dan

If you have a valid XOA license, then you always have the option of opening a support ticket.

Anything unusual / different about this VM? How many disks attached?

P.S. I assume that you're aware that Windows 2008 isn't officially supported any longer.