Attempting to add new host fail on xoa and on server, worked on xcp-ng center
-
I got the following when trying to add a new host to an existing pool
pool.mergeInto { "sources": [ "0af9d764-44e6-1393-4eea-6cb59b934f2a" ], "target": "38aea760-cf23-927c-ccf5-90969681e04b", "force": true } { "message": "app.getLicenses is not a function", "name": "TypeError", "stack": "TypeError: app.getLicenses is not a function at enforceHostsHaveLicense (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/pool.mjs:15:30) at Pools.apply (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/pool.mjs:80:13) at Pools.mergeInto (/opt/xen-orchestra/node_modules/golike-defer/src/index.js:85:19) at Xo.mergeInto (file:///opt/xen-orchestra/packages/xo-server/src/api/pool.mjs:311:15) at Task.runInside (/opt/xen-orchestra/@vates/task/index.js:175:22) at Task.run (/opt/xen-orchestra/@vates/task/index.js:159:20) at Api.#callApiMethod (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.mjs:469:18)" }
Had no idea what was up with this error, so updated the xoa vm and installed updates. But I still got the same error
I then tried adding it from the server itself, that also failed
/home/jonathon/Pictures/Screenshots/Screenshot from 2025-05-20 15-26-59.png
Just to see if it would work, I then tried with the latest xcp-ng center, and that worked.
So I do not need anything now, but thought it was interesting and worth posting.
-
Your XO VM is about 2 months out-of-date. Please make sure you are fully updated before posting making this type of post.
Let us know if you are able to reproduce using an up-to-date version of XO. You could also use a free trial of XOA to test this.
-
Indeed, there's a big yellow warning "You are not up to date with master". Maybe we should mark it bigger?
-
I ran the upgrade yesterday. And this is the state that it gave me
installing : node-v22.15.1 mkdir : /usr/local/n/versions/node/22.15.1 fetch : https://nodejs.org/dist/v22.15.1/node-v22.15.1-linux-x64.tar.xz installed : v22.15.1 (with npm 10.9.2) Stopping xo-server... Checking for Yarn package... Checking for Yarn update... Reading package lists... ... yarn install v1.22.22 [1/5] Validating package.json... [2/5] Resolving packages... [3/5] Fetching packages... [4/5] Linking dependencies... [5/5] Building fresh packages... $ husky install husky - Git hooks installed Done in 46.08s. yarn run v1.22.22 $ TURBO_TELEMETRY_DISABLED=1 turbo run build --filter xo-server --filter xo-server-'*' --filter xo-web • Packages in scope: xo-server, xo-server-audit, xo-server-auth-github, xo-server-auth-google, xo-server-auth-ldap, xo-server-auth-oidc, xo-server-auth-saml, xo-server-backup-reports, xo-server-load-balancer, xo-server-netbox, xo-server-perf-alert, xo-server-sdn-controller, xo-server-test, xo-server-test-plugin, xo-server-transport-email, xo-server-transport-icinga2, xo-server-transport-nagios, xo-server-transport-slack, xo-server-transport-xmpp, xo-server-usage-report, xo-server-web-hooks, xo-web • Running build in 22 packages • Remote caching disabled Tasks: 29 successful, 29 total Cached: 0 cached, 29 total Time: 1m18.85s Done in 79.13s. Updated version 5.177.0 / 5.173.2 Updated commit a49b27bff7d325f704957b8aac3055ad0407bd40 2025-05-20 16:42:02 +0200 Checking plugins... Ignoring xo-server-test plugin Cleanup plugins... Restarting xo-server...
-
It does not matter now, the host has been added. I had just found the error to be interesting that thought someone would want to know about it.
-
@Jonathon We are interested if you can reproduce using an up-to-date instance of XO.
-
@Danp Sorry, due to the host being added and me continuing on with my other tasks, it is not. I could have made that more clear.