Closed cairoapcampos closed 3 months ago
Hi,
Please read this first before reporting a bug: https://xen-orchestra.com/docs/community.html#report-a-bug
Rebuild with the latest commit and try again, if you still have the issue, we'll re-open here. Thanks!
@olivierlambert I updated commit 32448. However, the error persists.
I generated a new routine and the error repeated:
We need a bit more context because it sounds very likely an issue with your setup. Can you reproduce the issue with XOA?
@olivierlambert I updated the post and added a short video that shows the details. I noticed this problem occurs when Zstd compression is used.
Can you reproduce the issue with XOA? Have you checked that you can reach all hosts directly?
I only use XO from the sources. I don't have the XOA. Using XO I can do DR without using Zstd.
For the sake of identifying the issue, please deploy an XOA and test on both stable and latest channel to see if you have the issue. If yes, then the problem is maybe in XCP-ng. That's why it would have been better to start investigating on the forum before opening an issue here, where the goal here is more to post confirmed problems to avoid overwhelming XO developers.
OK. I will focus all my future questions on the forum. You can keep this thread closed then. I will carry out new tests.
Thank you very much! As soon as we identify something that can be reproduced by others, we'll re-open here and try to find the culprit!
Are you using XOA or XO from the sources?
XO from the sources
Which release channel?
stable
Provide your commit number
58cc1
Describe the bug
When executing the Disaster Recovery routine, the error "408 Request timeout" is displayed.
Error message
To reproduce
The Disaster Recovery routine is created for a Linux VM by setting compression to Zstd.
The routine is executed manually, and then an error status is displayed. When examining the reason for the error, the message "408 Request timeout" is displayed.
Watch the detailed video:
https://github.com/vatesfr/xen-orchestra/assets/21186839/f2384286-b669-4050-858c-2f1b4a147cc4
Expected behavior
No response
Screenshots
No response
Node
I don't know how to specify.
Hypervisor
8.2
Additional context
No response