Hi! We introduced a bug in commit 59e6868 causing "Page not found"s and fixed it in commit 6e52794.

This is simple enough so we'll implement it in XO 5. Thanks for the feedback!

@d1rtym0nk3y Thanks for the feedback! This is actually something that we had in mind. It will probably have to wait for the next major version of XO, though.

I already opened one: https://github.com/vatesfr/xen-orchestra/issues/4882.

pdonias created this issue in vatesfr/xen-orchestra

closed [VM] Network: show IP addresses in front of their VIFs #4882

We're showing all the IP addresses reported by the VM's guest_metrics, and they're not sorted in any specific way, indeed. We could change that and show each address in front of the corresponding VIF.

I'm not seeing any. And I don't think this would be fixed by @julien-f's recent change on xo-server-xoa since it should already use the configured proxy by going through the updater.

/cc @Mohamedox

https://github.com/vatesfr/xen-orchestra/issues/4467

pdonias created this issue in vatesfr/xen-orchestra

closed Hide legacy backup menu entry #4467

@julien-f We could also completely remove the menu entry and simply keep showing the legacy backups (if there are any) in Backup NG like we already do.

@jedimarcus We fixed it on master. If you pull the branch and rebuild, the test should pass now.

@jedimarcus It's not that old but they indeed changed the limit from 50 to 100 characters in version 2.10. We'll fix the plugin so that the test also passes on old versions, and since you were able to synchronize your pool, you can ignore the test failure. And thanks for the report

Hi @jedimarcus, what version of Netbox are you using?

Thanks @cookie-eater2000, we'll take a look.

Hi @frabatbecker, there was a small issue with job.runSequence, we fixed it in master. We also added a button to allow you to copy job IDs from the UI. Thanks for the report and let us know if you have other issues!

Might be related to this issue: https://github.com/vatesfr/xen-orchestra/issues/5033.

pdonias created this issue in vatesfr/xen-orchestra

open [Console] Broken keyboard after AltGr has been pressed on Windows #5033

@notscottsmith So apparently, the old protocol also adds x/ipv4/x fields with space-delimited IPs. That's what causing the issue, so we'll have to handle them too. Thanks!

@notscottsmith Ok, could you run this inside XO's directory with the VM's host and its password:

./packages/xen-api/dist/cli.js --au <HOST> root <HOST ROOT PASSWORD>

It should start a CLI. And then run this with the VM's UUID:

> find({ uuid: '<VM UUID>' }).$guest_metrics.networks

@olivierlambert Most likely, yes. But it shouldn't be an issue anymore after this change (XO 5.60) so I don't understand why the error is still happening.

@notscottsmith Do you see those space-delimited IPs in the UI too?

There's a 1 min cache on XO's side. So if the updates weren't showing up for more than 1 minute, then it might be something else.