Hi @bnerickson, indeed, the configurations are correctly imported but plugins aren't automatically "configured" when you import a config. We'll improve that, thanks for the report

Hi @theaeon, this should already be fixed, could you check the full log for that error in Settings > Logs? It should give you more details.

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.

Hi @RaHu! No, at the moment, we don't synchronize hosts' information. I'm not even sure where that information could go as there isn't such a thing as a host object in Netbox, AFAIK.

@olivierlambert No, because {name} will be replaced by the main name input (at the top of the form), not the individual names in case of bulk creation. So you should get "test1", "test2", as expected.

Hi @bnerickson, indeed, the configurations are correctly imported but plugins aren't automatically "configured" when you import a config. We'll improve that, thanks for the report

@theaeon No, that's a normal case and it's handled properly. The issue would be if one of the IPs has 2 IPs in the same field separated by a white space like: "x.x.x.x y.y.y.y", or if the field is just empty or anything else that doesn't look like a proper IP address.

If you want to check the addresses more thoroughly, you can install xo-cli with npm i -g xo-cli, log into your XO with xo-cli --register <XO-Server URL> <username> <password> and then run xo-cli --list-objects --addresses type=VM \$pool=<pool ID>.

Hi @kajetan321, please add this to your xo-server config file:

[logs]
level = 'debug'

then test the plugin again and check xo-server's output when the error occurs to help identify what's causing the issue.

Thanks @theaeon. Could you check if some of your VMs on that pool have invalid IP addresses? You can do that from the home page by filtering only the VMs on that pool (Pools selector at the top of the page) and expanding the details for all the VMs to show the IP addresses (hamburger button at the top right hand corner). Each IP address must be in its own blue rectangle and with the correct format for either IPv4 or IPv6. Let me know if this is too hard to check, we'll find another way.

Hi @theaeon, this should already be fixed, could you check the full log for that error in Settings > Logs? It should give you more details.

Hi @luca-steinke, this is indeed something that we should and will document. Here are the minimum required permissions:

View permissions on:

• extras > custom-fields
• ipam > prefixes

All permissions on:

• ipam > ip-addresses
• virtualization > cluster-types
• virtualization > clusters
• virtualization > interfaces
• virtualization > virtual-machines

Hi @NielsH, thanks for the feedback, we'll discuss it but this may indeed have to wait for XO 6.

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