Julien Fontanet

I'm not sure those advanced actions should be exposed in the UI, IMHO, users should use `xe` for such dangerous things. Does XCP-ng Center expose it?

Hi, The idea is interesting but it's not a priority for us, if a PR for this appear, we'll take a look though :smiley:

Likely related to the issue nodejs/node#48145 You can work around this by increasing the default `autoSelectFamilyAttemptTimeout` of 250 (miliseconds) in `/etc/xoa-updater/config.autoSelectFamilyAttemptTimeout.json`: ```json { "autoSelectFamilyAttemptTimeout": 1000 } ```

Also, you need to upgrade before being able to do that. If you need help, please open a proper support ticket and a support tunnel.

@olivierlambert What should we do with this issue?

@rtjdamen Are you sure both your XOA and your XO Proxies are up-to-date on latest channel? If they are, we need to take a look at them.

@rtjdamen After looking at your infra, it seems that there is still a major improvement, there are very few `VDI_IN_USE` errors now :slightly_smiling_face: The only problem we saw comes from...

@MathieuRA You are probably not wrong, but this is a separate feature and a separate implementation, no need to do them at the same time.

There is no easy answer on this, to help mitigating this issue you can disable the merge worker so that the merge step happens during the backup run itself. This...

@b-Nollet I'm not very familiar with Icinga 2, but using the compact mode would make sense to me.