Hi @acebmxer,
Can you test if the branch: fix_cloudinit_import fix your issue?
Edit: It is available on the master branch.
Hi @acebmxer,
Can you test if the branch: fix_cloudinit_import fix your issue?
Edit: It is available on the master branch.
@Andrew @probain
XO was hiding some error message and fell back silently ( or fail later) , this onth updates gives us more information
are you using NBD ( it is mandatory for qcow2 disks) ?
is NBD enable on at least one network per pool ?
can XO access this network ?
is there a default backup network on the pool ? with NBD ? accessible by XO ?
any more logs on journalctl ( I am expecting some nbdinfos )
@pedro_udifar Hi,
You can try again with minPartSize=100000000 indeed. But I would advise you to contact B2 directly. They should have a clearer error to show instead of a 500.
Thanks for your patience and your help
@pedro_udifar This is indeed a particular case. Can you switch xo-server log to debug please? Then we would need the journalctl from your xo-server. You can give it to me through MP if you prefer.
Hello @tmk,
The fix is on its way: https://github.com/vatesfr/xen-orchestra/pull/10129
It should be included in XO 6.7, which will be released at the end of month.
I was able to reproduce the problem, so it seems the modifications we brought a couple of weeks ago didn't fix it.
I'm working on a fix at the moment.
Hello @tmk,
Can you tell me which version of XO you are using?
We made a modification on the task error handling a couple of weeks ago.
They run once a day @ 03:04 before the normal backup that starts @ 03:10 and they have all run OK since July 8, the failed one reported 8 days ago ( post ~85 )
Hi, just to be sure, are you saying it is working ok apart one task 8 days ago?
@itservices Great news.
Don't hesitate to post here again if you encounter a similar issue in the future.