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

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.

@Danp said in error on copy VM cross pools:

@Gheppy said in error on copy VM cross pools:

fd7d52d38bf4d6ffc6288d0c86acdbbfdaca3fad - NOT OK

This is the same commit that we discussed in following open issue --

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

/cc @julien-f @badrAZ

BitSprocket created this issue in vatesfr/xen-orchestra

open XO From source restore backup fails with VDI_IO_ERROR #4640

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

@julien-f, correct me if I'm wrong but currently, we don't try to map the VM's VIFs with specific PIFs of the destination host. We use the default behaviour of a normal XAPI VM import.

Sure! Make sure you're connected to XO with xo-cli and then:

$ xo-cli log.delete namespace=restore id=1570142063787

Hi @axiom00, it's not possible to clear the logs from the UI. We purposely removed the feature because the logs are very useful to investigate on a problem and they were too often deleted by mistake. Let us know what you think about this

Hi @S-Pam, thanks for the suggestion! Are you talking about having such a Gantt chart when you're creating a new scheduled job or once the jobs have run to see what happened? I can see one limitation with the "preview" one: we'd need to know in advance how much time each run will take and that's not something we're able to guess.

It's an admin privilege.

Hi @discostur!
You can only set the allowed IPs via IP pools at the moment. And you can access IP pools either by being an XO Admin or with Self Service.
So:

• Create an IP pool (Settings > IPs) with the IP range you want to allow the user to use
• Create a Resource Set (Self Service > New) and select the user and the IP pool you just created

If it's not a UTC formatted string, then it will indeed behave as if the 2 dates were more than 30 seconds apart. Is it supposed to happen? We can easily fix that.

We compare the time reported by XAPI's method host.get_servertime and Node's Date.now() in XOA and check if they're more than 30 seconds apart. We work with timestamps so the timezones shouldn't matter.