Tested OK on
Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz

I powered on my spare test "server" and ran this update.
All went fine.
After the reboot I started the fully updated XOA (local installed) and ran it for a few minutes.
then I shut it down but it sat for a few minutes so I did a force shut down from xsconsole.
Rebooted the host again and started the XOA, shut it down and it worked fine
Tested one more time and it went OK.

Upgrade to RC2 worked fine so far with netinstall ISO in ventoy on a 8 gen i5 HP laptop. And a "full" ISO on its own USB on a Lenovo Thinkcentre Ryzen 5 2400GE

No stats :o(
but netdata seems to work

@olivierlambert
I have reported a similar issue with the cpu report:
Lots of performance alerts after upgrading XO to commit aa490
https://xcp-ng.org/forum/topic/9658/lots-of-performance-alerts-after-upgrading-xo-to-commit-aa490/14#

I increased the dom0 RAM from default 1.75 to 2 GiB
Hopefully this will do.

yes there is, in the docs
https://docs.xen-orchestra.com/backups#exclude-disks

@rtjdamen
Exactly

I have a similar backup strategy
One backup job with 2 schedules
Works fine for me

@bvitnik @redakula @irtaza9
This is how I filtered out with TAGS
Added a TAG Visa to the Template I wanted to show

Then I selected the tag in Edit my settings | Custom filters | Templates | Default filter

@gduperrey

I updated my test host and all seems to work fine.
But I have 1 question:
Do I need to disable the testing repo or is it removed at the reboot?

yum clean metadata --enablerepo=xcp-ng-testing
yum update --enablerepo=xcp-ng-testing
reboot

[10:33 x1 ~]# yum repolist 
Inlästa insticksmoduler: fastestmirror
Loading mirror speeds from cached hostfile
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-base: mirrors.xcp-ng.org
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-updates: mirrors.xcp-ng.org
förråds-id                                 förrådsnamn                                           status
xcp-ng-base                                XCP-ng Base Repository                                4 376
xcp-ng-updates                             XCP-ng Updates Repository                               125
repolist: 4 501

@Bastien-Nollet
More problems
I previous had 2 XO disabled from the alerts.

But when I decided to remove both of them from the exclude or if I toggle the green exclude VMs "switch", I got this error:

plugin.configure
{
  "id": "perf-alert",
  "configuration": {
    "baseUrl": "Removed",
    "hostMonitors": [
      {
        "smartMode": true,
        "alarmTriggerLevel": 60,
        "alarmTriggerPeriod": 60
      },
      {
        "smartMode": true,
        "variableName": "memoryUsage",
        "alarmTriggerLevel": 90
      }
    ],
    "toEmails": [
      "Removed"
    ],
    "vmMonitors": [
      {
        "smartMode": true,
        "alarmTriggerLevel": 60,
        "alarmTriggerPeriod": 60,
        "excludeUuids": false,
        "uuids": [
          "2f819438-5ab1-7309-99b0-7116313a03fe",
          "ee56c3c7-fd7d-c9aa-b2e1-ee698267e241"
        ]
      }
    ],
    "srMonitors": [
      {
        "smartMode": false,
        "uuids": [],
        "excludeUuids": false
      }
    ]
  }
}
{
  "code": 10,
  "data": {
    "errors": [
      {
        "instancePath": "/vmMonitors/0/smartMode",
        "schemaPath": "#/properties/vmMonitors/items/oneOf/0/properties/smartMode/anyOf/0/not",
        "keyword": "not",
        "params": {},
        "message": "must NOT be valid"
      },
      {
        "instancePath": "/vmMonitors/0/smartMode",
        "schemaPath": "#/properties/vmMonitors/items/oneOf/0/properties/smartMode/anyOf/1/const",
        "keyword": "const",
        "params": {
          "allowedValue": false
        },
        "message": "must be equal to constant"
      },
      {
        "instancePath": "/vmMonitors/0/smartMode",
        "schemaPath": "#/properties/vmMonitors/items/oneOf/0/properties/smartMode/anyOf",
        "keyword": "anyOf",
        "params": {},
        "message": "must match a schema in anyOf"
      },
      {
        "instancePath": "/vmMonitors/0/uuids",
        "schemaPath": "#/properties/vmMonitors/items/oneOf/1/properties/uuids/not",
        "keyword": "not",
        "params": {},
        "message": "must NOT be valid"
      },
      {
        "instancePath": "/vmMonitors/0/excludeUuids",
        "schemaPath": "#/properties/vmMonitors/items/oneOf/2/properties/excludeUuids/const",
        "keyword": "const",
        "params": {
          "allowedValue": true
        },
        "message": "must be equal to constant"
      },
      {
        "instancePath": "/vmMonitors/0",
        "schemaPath": "#/properties/vmMonitors/items/oneOf",
        "keyword": "oneOf",
        "params": {
          "passingSchemas": null
        },
        "message": "must match exactly one schema in oneOf"
      }
    ]
  },
  "message": "invalid parameters",
  "name": "XoError",
  "stack": "XoError: invalid parameters
    at invalidParameters (/opt/xo/xo-builds/xen-orchestra-202503081124/packages/xo-common/api-errors.js:26:11)
    at default._configurePlugin (file:///opt/xo/xo-builds/xen-orchestra-202503081124/packages/xo-server/src/xo-mixins/plugins.mjs:175:13)
    at default.configurePlugin (file:///opt/xo/xo-builds/xen-orchestra-202503081124/packages/xo-server/src/xo-mixins/plugins.mjs:199:16)
    at Xo.configure (file:///opt/xo/xo-builds/xen-orchestra-202503081124/packages/xo-server/src/api/plugin.mjs:12:3)
    at Task.runInside (/opt/xo/xo-builds/xen-orchestra-202503081124/@vates/task/index.js:175:22)
    at Task.run (/opt/xo/xo-builds/xen-orchestra-202503081124/@vates/task/index.js:159:20)
    at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202503081124/packages/xo-server/src/xo-mixins/api.mjs:469:18)"
}

I then tried to remove 1 VM , OK
Removed the 2nd one, OK
But when I tried to toggle the green switch I got this error

plugin.configure
{
  "id": "perf-alert",
  "configuration": {
    "baseUrl": "Removed",
    "hostMonitors": [
      {
        "smartMode": true,
        "alarmTriggerLevel": 60,
        "alarmTriggerPeriod": 60
      },
      {
        "smartMode": true,
        "variableName": "memoryUsage",
        "alarmTriggerLevel": 90
      }
    ],
    "toEmails": [
      "Removed"
    ],
    "vmMonitors": [
      {
        "smartMode": true,
        "alarmTriggerLevel": 60,
        "alarmTriggerPeriod": 60,
        "excludeUuids": false,
        "uuids": []
      }
    ],
    "srMonitors": [
      {
        "smartMode": false,
        "uuids": [],
        "excludeUuids": false
      }
    ]
  }
}
{
  "code": 10,
  "data": {
    "errors": [
      {
        "instancePath": "/vmMonitors/0/smartMode",
        "schemaPath": "#/properties/vmMonitors/items/oneOf/0/properties/smartMode/anyOf/0/not",
        "keyword": "not",
        "params": {},
        "message": "must NOT be valid"
      },
      {
        "instancePath": "/vmMonitors/0/smartMode",
        "schemaPath": "#/properties/vmMonitors/items/oneOf/0/properties/smartMode/anyOf/1/const",
        "keyword": "const",
        "params": {
          "allowedValue": false
        },
        "message": "must be equal to constant"
      },
      {
        "instancePath": "/vmMonitors/0/smartMode",
        "schemaPath": "#/properties/vmMonitors/items/oneOf/0/properties/smartMode/anyOf",
        "keyword": "anyOf",
        "params": {},
        "message": "must match a schema in anyOf"
      },
      {
        "instancePath": "/vmMonitors/0/uuids",
        "schemaPath": "#/properties/vmMonitors/items/oneOf/1/properties/uuids/not",
        "keyword": "not",
        "params": {},
        "message": "must NOT be valid"
      },
      {
        "instancePath": "/vmMonitors/0/excludeUuids",
        "schemaPath": "#/properties/vmMonitors/items/oneOf/2/properties/excludeUuids/const",
        "keyword": "const",
        "params": {
          "allowedValue": true
        },
        "message": "must be equal to constant"
      },
      {
        "instancePath": "/vmMonitors/0",
        "schemaPath": "#/properties/vmMonitors/items/oneOf",
        "keyword": "oneOf",
        "params": {
          "passingSchemas": null
        },
        "message": "must match exactly one schema in oneOf"
      }
    ]
  },
  "message": "invalid parameters",
  "name": "XoError",
  "stack": "XoError: invalid parameters
    at invalidParameters (/opt/xo/xo-builds/xen-orchestra-202503081124/packages/xo-common/api-errors.js:26:11)
    at default._configurePlugin (file:///opt/xo/xo-builds/xen-orchestra-202503081124/packages/xo-server/src/xo-mixins/plugins.mjs:175:13)
    at default.configurePlugin (file:///opt/xo/xo-builds/xen-orchestra-202503081124/packages/xo-server/src/xo-mixins/plugins.mjs:199:16)
    at Xo.configure (file:///opt/xo/xo-builds/xen-orchestra-202503081124/packages/xo-server/src/api/plugin.mjs:12:3)
    at Task.runInside (/opt/xo/xo-builds/xen-orchestra-202503081124/@vates/task/index.js:175:22)
    at Task.run (/opt/xo/xo-builds/xen-orchestra-202503081124/@vates/task/index.js:159:20)
    at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202503081124/packages/xo-server/src/xo-mixins/api.mjs:469:18)"
}

@kagbasi-ngc
Until there is a solution to the log export, You could keep the old XOA with the network disabled

@ph7
3rd run

No alert.
Somehow, the CPU usage is lower.
I shall lower the alert limits to see what happens.

4th run with 55% limit
I got 1+1 alarms this time.

5th run
I got 1+1 alarms this time to.

6th run
Increased the concurrency to 2.
this did put some more stress on the system.

only 1+1 alerts again.
Seems like You nailed it.

Maybe You should check some more

And I am sorry for that, I was wrong

@ph7
And it did report the correct VM at the end of alert

@Bastien-Nollet
Hi
I updated my test server and a copy of a Ronivay XO

1st run

Host:

I only got 1+1 alert on e-mail, that seems OK.

2nd run

This time NO alert.
Maybe You should check some more
I will test again tomorrow, Good night...

@bvitnik @redakula @irtaza9
This is how I filtered out with TAGS
Added a TAG Visa to the Template I wanted to show

Then I selected the tag in Edit my settings | Custom filters | Templates | Default filter

@Andrew said in All drop-down options are empty:

release 5.103.1

How do You do this?
Is it possible to choose exactly this release when running the update, or do you check github every day?
Sorry for this question but I don't know the github finesses

I increased the dom0 RAM from default 1.75 to 2 GiB
Hopefully this will do.

In the replication job I keep Replication Retention=2
So at the time of reboot, 03:48 UTC, there was 2 saved CR-jobs that ran at 01:10 and 01:40

According to the time in red markings, The first alert ran at 05:00 CET (UTC + 1 hour)

And this is from dmesg:
[ 0.994105] rtc_cmos 00:02: setting system clock to 2025-02-24 03:48:56 UTC (1740368936)

I can not figure out

1. why did the host reboot?
2. why did one of the CR-jobs start ??
3. why was there ~15 hours without any graph?

I have UPS with NUT-shutdown on the host and on my trueNAS, with no indication of power failure.