New VM Creator drop-down is not working

JamfoFL

Good morning and happy Leap Day to my fellow Xen Orchestra folks!

I'm having an issue where the new "VM Creator" drop down on the Advanced tab for my virtual machines does not appear to work. I can click the arrow to bring up the list of all the associated users, but once I select any of the users I receive an error log.

First, the Orchestra details. It is 9:15 AM EST on February 29th, and I just installed all of the latest commits. Both the Master and Xen Orchestra commits report #2560b.

As soon as I click on any of the names in the drop down, I receive an "Invalid parameter" error message. Here's the full log:

vm.set
{
  "creation": {
    "user": "06168cdb-3e03-464d-b623-015d8f5aeb79"
  },
  "id": "d886a884-82c6-d68b-419f-f26279eff06d"
}
{
  "code": 10,
  "data": {
    "errors": [
      {
        "instancePath": "",
        "schemaPath": "#/additionalProperties",
        "keyword": "additionalProperties",
        "params": {
          "additionalProperty": "creation"
        },
        "message": "must NOT have additional properties"
      }
    ]
  },
  "message": "invalid parameters",
  "name": "XoError",
  "stack": "XoError: invalid parameters
    at Module.invalidParameters (/root/xen-orchestra/packages/xo-common/api-errors.js:26:11)
    at Xo.call (file:///root/xen-orchestra/packages/xo-server/src/xo-mixins/api.mjs:92:22)
    at Api.#callApiMethod (file:///root/xen-orchestra/packages/xo-server/src/xo-mixins/api.mjs:441:19)"
}

Hopefully that makes sense to the bigger brains out there.

Not a big deal, really... just an error that popped up!

Danp

Tested on my side, but wasn't able to replicate. Does this happen with every VM?

JamfoFL

Danp Yes... it happens on every VM in the pool, no matter on which host they happen to reside.

Danp

JamfoFL IDK... it works fine for me. What does node -v return?

JamfoFL

Danp It reports, "v18.18.2".

Danp

I'm on v18.19.1

JamfoFL

Danp OK... I'll try updating and see if that makes a difference!

JamfoFL

Danp Yup... that fixed it. Seems like such a minor revision update of Nodejs, but I guess it was the secret sauce.

Thanks for your mental prowess! I really appreciate your help.

Please feel free to close this out!

olivierlambert

That's weird A minor release shouldn't trigger that, any idea julien-f ?

julien-f

It has likely nothing to do with Node's version.

JamfoFL Make sure your xo-server is up-to-date on master, both rebuilt and restarted.

JamfoFL

julien-f Thanks for following up. I don't know if you saw the whole thread, but both master and Xen Orchestra were updated with the latest commits before I started and that did not seem to help. Once I updated Nodejs from 18.18.2 to 18.19.1 everything worked as expected.

I can't do any further testing as things were because everything is working now.

It could be that there was something slightly messed up in my Nodejs install and updating to 18.19.1 fixed that issue and, by extension, the problem I was having in Orchestra. My original error log message is posted above, if that helps.

julien-f

JamfoFL I have absolutely no idea how this error could be related to the version of Node, it really looks like an old version of xo-server which did not support the creation param.

If you cannot reproduce, let's close this for now.

JamfoFL

julien-f Agreed... I will add (just for future reference) that I did confirm that I was on the very latest versions of xo-server at the time... in fact, I made sure to apply all updates and reboot the Xen server before submitting the ticket.

Nothing seemed to work... even multiple reboots, etc. Once Danp made mention of the Nodejs version and I updated from v18.18.2 to v18.19.1 everything immediately started working. I made no other changes after applying the Nodejs update.

So while that may not have been the cause, it somehow fixed whatever was ailing me. I have no explanation either, other than the fact that making that change is what took me from the feature not working to the feature working.