Commands in Xen Orchestra Jobs no longer working

PC_123

I recently needed to rebuild my instance of Xen Orchestra as part of an upgrade.

For some reason when using the Job that triggers host.start it returns with an invalid parameter error.

Any idea on what I could try to resolve this issue?

Error Details:

host.start
{
  "id": [
    "efa4ef5e...."
  ]
}
{
  "code": 10,
  "data": {
    "errors": [
      {
        "code": null,
        "reason": "type",
        "message": "must be string, but is array",
        "property": "@.id"
      }
    ]
  },
  "message": "invalid parameters",
  "name": "XoError",
  "stack": "XoError: invalid parameters
    at Module.invalidParameters (/opt/xo/xo-builds/xen-orchestra-202111080620/packages/xo-common/src/api-errors.js:21:32)
    at Object.call (file:///opt/xo/xo-builds/xen-orchestra-202111080620/packages/xo-server/src/xo-mixins/api.mjs:73:18)
    at Api.callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202111080620/packages/xo-server/src/xo-mixins/api.mjs:300:19)"
}

techjeff

I have seen this as well, and I reported Basic Job failing with "Invalid parameters" Error on vm.start #5983.

As of this writing, that bug appears to be in Triaging status.

I would also like to note that I have a startup job that was configured some time ago (didn't document when) which works just fine. If I recreate the same job from scratch, I get this new error.

This suggests that the issue is related to the newly created job object and the previous job object is still sending a string value containing the one VM rather than an array with a single vm.

It seems that either the UI changed to allow selection of multiple VMs per job, or if that was already possible, then the UI is attempting to send an array rather building a comma-separated string for example.

Hopefull you have a backup/snapshot to which you can revert until the issue is resolved if you really need that functionality.

PC_123

@techjeff

Thanks TechJeff!

Yes I have 5 different instances of Xen Orchestra sleeping across my pool. I updated my Primary & Secondary to the latest Xen Orchestra and that's when they stopped working.

Jobs that Xen Orchestra was coordinating for me included booting, backups, and shutdown's.
They all started failing on the new version:

XO-Server 5.83.0 / XO-Web 5.89.0 / Ubuntu 20

The older version running on Ubuntu 18 is XO-Server 5.78.2 / XO-Web 5.80.0 is back to being Primary and works flawlessly so far.

So I'll follow your advice and live on the old version until the issue is resolved.

This is still great software, sometimes it takes these issues to fully appreciate how useful & reliable this application is.

Big Thanks to you super smart people who keep these things working for us!!!

olivierlambert

The best solution is to rely on XOA, you know

techjeff

@olivierlambert said in Commands in Xen Orchestra Jobs no longer working:

The best solution is to rely on XOA, you know

I agree with @olivierlambert! Personally, I'm using XO from sources in my home lab environment -- nothing is "production" and I'm mostly having fun trying to give back to the open source community.