@bogikornel are you talking about another issue? We are on an issue specifically on "pool metadata backups". It seems you are talking about VM backups. If yes, can you send the backup log please?
XO Team
Developers of Xen Orchestra
Posts
-
RE: Backup fails with "Body Timeout Error", "all targets have failed, step: writer.run()"
-
RE: Backup fails with "Body Timeout Error", "all targets have failed, step: writer.run()"
-
RE: Backup fails with "Body Timeout Error", "all targets have failed, step: writer.run()"
@MajorP93 Hi,
Thank you, thank you! I think you found it! It seems to be SMB, @acebmxer can you confirm that you also use smb please?
If this is the case, the bad news is I think we will need to update our docs to not advise SMB at all: it was already said for delta but maybe we will have to extend this to all kind of BR
-
RE: Backup fails with "Body Timeout Error", "all targets have failed, step: writer.run()"
@JB this really looks like a network issue
are the host/xoa remotes ?
-
RE: When the XCPNG host restart, it restarts running directly, instead of being in maintenance mode
Hi,
XOA version:
xo-server 5.193.1
xo-web-premium 5.191.0We've noticed on our production XOA server that when we put an XCPNG host in a pool into maintenance mode, we reboot it and then it reconnects to its pool but is no longer in maintenance mode.
Is it possible to configure the XCPNG hosts so that they automatically return to maintenance mode after a reboot?Regards,
Oliv77
Hi @oliv77, XO 6.7 - latest - adds this option in REST API and next month we should have the available action (Disable host and evacuate VM) in XO6 !
-
RE: 🛰️ XO 6: dedicated thread for all your feedback!
Ah sorry I read it too quickly. This panel is only there in some occasions, but I see the point of only displaying it when we click on a relevant element. Feedback for you @julienxovates
While on the topic of the tree-view panel.
Have you noticed that the indentation changes if there is a chevron indicating that there are VMs on a host? Making it so that the hosts no longer are alinged vertically

Hi @jr-m4, it took some time but we corrected the identation in 6.7 (latest)

-
RE: Backup fails with "Body Timeout Error", "all targets have failed, step: writer.run()"
@JB this looks like an issue while reading the export part. Did you configure a default backup network in the pool ?
is there any firewall/sdn controller that can filter out some reading ?note that we have removed several point that where hiding some errors this month.
-
RE: v6 UI VDI's not being shown all the time.
This issue should be fixed in the latest release (to be out today).
-
RE: Deploy VM via cloud-init config
@acebmxer Thank you for your quick feedback.
-
RE: Deploy VM via cloud-init config
Hi @acebmxer,
Can you test if the branch:
fix_cloudinit_importfix your issue?
Edit: It is available on the master branch.