New VM Creator drop-down is not working

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.