@julien-f I can confirm what @Andrew posted... I also updated to Master Commit 583c7 and the CR backups are working properly once again!
Thank you so much!!
@julien-f I can confirm what @Andrew posted... I also updated to Master Commit 583c7 and the CR backups are working properly once again!
Thank you so much!!
I just wanted to chime in that I was having the same issue after updating to the latest commit earlier today, 1b5157e9a7a7ba9a49ebc9484737c34ef3da95ed.
I rolled back to my previous commit (granted, it's a bit of an older one as I hadn't updated since last week) and the CR backups started working again perfectly.
In my case, both XCP-ng hosts are on the same subnet.
So, something seems to have broken CR backups between last week and today. Fortunately, rolling-back got everything working again.
If there's anything I can do on my end that might help, just let me know!
@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.
@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.
@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!
@Danp OK... I'll try updating and see if that makes a difference!
@Danp Yes... it happens on every VM in the pool, no matter on which host they happen to reside.
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!
@olivierlambert A-ha! Thanks! So it was just a coincidence... and I was a little ahead of the game.
Sorry for the confusion. Thanks for putting my head on straight!
@olivierlambert Maybe it's two different things?
After applying all the latest updates as of about 90 minutes ago, I now have this new "Edit VM Notes" button on my screen:
I had never seen that before... and I last updated on Wednesday of last week.
I thought that might be what @Melissa-FR was talking about, but maybe this is another new, unrelated feature?
@olivierlambert Ugh... I'm sorry if this is not the place to put this since you already closed it, or if I should open a new ticket. I apologize if I am wrong for doing this.
So, I see the new feature popping up in Orchestra... but are there any links to instructions on how to use it? I've been searching here on the site but haven't found any. I might simply be missing the obvious.
I click on the "Edit VM Notes" button that is now available on each VM's "General" tab, but no matter what I type in the box that pops up, I get an "invalid syntax" error.
Again... if I should generate a new question for this, please let me know and I'll write one up.
Thanks again!
@Melissa-FR Thank you, @Melissa-FR! I really appreciate the update.
@Andrew Thank you Andrew... sorry it took me a while to get back to you. It seems every time I have to go and update Node they change the method you need to do so and it takes me forever to figure out what I'm supposed to do.
I still haven't figured that out, but that's on me. However, restarting the toolstack did not fix the issue, but restarting the XO Ubuntu host server did.
I've not seen anything like that before, where I've had to reboot the entire host server after applying commits... but if it works, I shall not argue!
Thank you again for all of your help. I hope you have a wonderful weekend and a fantastic holiday season.
@Andrew Thank you for the quick reply!
I have two redundant copies of Orchestra so I can test and have the same error message on both.
On copy number one, I am still on an older commit, #4a5bc. This one is running on Node v18.18.2.
On copy number two, I am on the latest commit, #bb3b8. This one is also running on Node v18.18.2.
Nothing was changed on either version of Orchestra or the underlying Ubuntu OS, only the commit was updated. Was there some kind of update to Node that needs to be applied manually?
Thanks once again!
Good afternoon and happy holidays!
I am currently running XO from sources. Commit #bb3b8 (just ran the update before submitting this ticket at 12:05 PM Eastern Time on 12/08/2023).
Everything had been working normally, and is still working for the most part, until I updated the latest commits back on Monday afternoon. Since then, I get the following on the Disks tab for every VM on every host:
Updating to the latest available commit at the time of typing, #bb3b8, has not fixed the issue. This is the only tab in all of Orchestra that is not working properly. I also have found that if I go to the Local Storage for each host and go to the Disks tab from that location, I can see each of the disks, no problem.
So, something seems to be preventing the data from being displayed on that single tab for all VMs on all hosts. This has not affected the operation of any VM or had any other side effects; just the display of disk information on that one tab in the VM itself is broken.
I welcome any suggestions! Thank you all!
@olivierlambert I believe it was 16.7... yeah, I know... I should have updated that long ago but always seem to forget about the non-Orchestra stuff!
Hey... what do you know... I actually figured this out on my own! I try to stay on top of all of the Orchestra specific updates like commits and such but forget about some of the underlying prerequisites that Orchestra uses. In this case, I had been negligent in updating my node version to 18.18.
I updated node and, boom, the tab is back up and working now as expected!
Sorry to raise an issue when it wasn't needed. I guess if anyone else has the issue, this will remind them to keep their systems fully up to date, too!
Thanks again for responding so quickly! I always appreciate your work!! Feel free to resolve the issue!!
@olivierlambert Wow... thank you so much for the insanely rapid reply!
All of the other screens in Orchestra seem to be working just fine, including the console window:
Everything in there is working and fully responsive, exactly as you would expect it to be. No issues with the VM's or anything else... just that one tab!
The current setup details:
XCP-ng Version = 8.2
XO Version = from Sources
XO-Server = 5.124.0
XO-Web = 5.126.0
Orchestra Commit = 7c009
Some time between Friday, when I updated to Orchestra Commit 00a17 and today, when I updated to Orchestra Commit 7c009, something was changed that seems to have broken the "Advanced" tab for all of the virtual machines. If I click on that tab now, all I see is the following:
It was working when last I checked on Friday, and no other changes were made other than updating to the latest commit earlier today. From what I can tell, this is the only tab that appears to be broken, and it's only for the "Advanced" tab for virtual machines. The "Advanced" tab in other areas, for hosts, for example, work just fine.
I can start doing the walk-back routine to see if I can find the specific commit that started the issue if that will help.