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.

The UI only supports IPv4 at the moment. If IPv6 is supported everywhere in the back-end (xo-server and XS/CH/XCP-ng), we should add support for it in the UI.

Hi, I tried to reproduce but I don't seem to have any issue deploying a XOA on a pool that doesn't have a default SR (as long as I select a SR that has enough space when prompted).

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

pdonias created this issue in vatesfr/xen-orchestra

open Hide legacy backup menu entry #4467

@julien-f I don't think there will be that many complaints since:

• as @olivierlambert said, there shouldn't be that many legacy backups any more
• if you're looking for your backups, you'll most likely click on the only menu entry that says "backup"
• legacy backup users have already been used to going to the Backup NG view to see their legacy backups for a while now because when you go to the Backup view, there's already a message telling you the legacy backups aren't shown there any more

Am I being too optimistic?

I don't think it would be an issue to always (ie until XO 6, maybe?) show the legacy backups in the Backup NG view. We can even show them at the top of the page to make sure users don't miss them.
@julien-f Complaints about what? Not finding their backups?

@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.

@olivierlambert Is the new XOA deployed on xoa.io?

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