ova import failing silently. logs show timeout against xcp-ng node

ITJamie

@olivierlambert
heres the exact one im importing
https://cloud-images.ubuntu.com/focal/20220215/focal-server-cloudimg-amd64.ova

olivierlambert

Perfect, this will help us to test it on our side We'll keep you posted!

olivierlambert

@nraynaud any chance you can take a look?

nraynaud

yes, I'll have a look

olivierlambert

Thanks!

nraynaud

I am extremely sorry, but it seems to works on my machine

Capture d’écran 2022-02-17 à 10.00.28.png

BUT, the error I see in your logs also exists at another customer site, and they also trigger it with a publicly available OVA.
If you can and want, would you mind trying to import 'watchguard-dimension_2_2.ova' https://software.watchguard.com/SoftwareDownloads?current=true&familyId=a2RF00000009On4MAE
and check if you get the same error ? you don't have to start the VM, we are just looking for vhd-tool output: vhd-tool: Non-zero size required in xensource.log

We will confer internally. in the mean time.

Nicolas.

ITJamie

@nraynaud said in ova import failing silently. logs show timeout against xcp-ng node:

Non-zero size required

confirmed i do get the same error. I have not managed to successfully upload any ova or vmdk through the gui

for additional context, i am running this on Version 98.0.4758.80 (Official Build) (arm64) chrome on an m1x mac.
ive also tried it through latest chrome on a windows machine

I saw very little network throughput from the point i pressed "upload" to the point the error appeared in logs. I have a feeling the vmdk is just not being converted in the browser. Can we enable additional logging in the vmdk to vhd code?

olivierlambert

Could you also check with Firefox, just to be sure?

Also, what kind of storage (SR) is the target on your XCP-ng? (local ext, LVM, iSCSI?)

ITJamie

@olivierlambert local ext and nfs. ive tried both. ive also tried it against different xcp-ng hosts,all installed from the same 8.2.0 iso

tried with firefox. same deal. i noticed in osx's activity monitor it only sent 10MB total

ITJamie

@ITJamie Screenshot 2022-02-17 at 11.57.00.png

after messing around re-attempting uploads. i managed to get this to appear in debugger console logs...

ITJamie

@olivierlambert
firefox (latest after i upgraded it) on windows just worked!
managed to upload the ubuntu image and the watchguard image!

so nether firefox nor chrome worked on mac.
firefox (97.0) did work on windows.
firefox uploads worked to both local storage and nfs

chrome didnt work on windows when i tried yesterday. however today when i rdp'd in i noticed it was awaiting an upgrade. post upgrade it did manage to upload (im not sure how out of date it was, i dont use windows much)

so currently it means we can work with xoa uploader on windows. but not mac (at least, not m1x arm64 macs, ill try pull out one of my older macs later and see if it works on x86-64 bit mac)

if theres any additional tests you need me to perform to try help that other user @nraynaud mentioned id be happy to.

nraynaud

@ITJamie thanks! it's the first clue ever we get on this problem.

and it is front side, which makes it a bit easier to find.

It's not a slam dunk, because it works here, on a mac with chrome, mut we have a lead.

ITJamie

@nraynaud
if there is a way to quickly enable a lot of console logging for this im happy to swap out the xoa build and re-test and give you logs

nraynaud

@ITJamie oh I see you're building from sources, even better, would you mind being my eyes in Chrome debugger?

when you click on the 'import' button (maybe for a failing VMDK disk, it's the simplest code path that fails) there should be a POST request to a weird URL , if you could tell me the content-length of the request (not the response), and if you see anything untowards in the payload.

here is a capture of a normal thing on my computer:
https://gfycat.com/aggressivedisgustinggopher (there is an HD button at the bottom right)
the payload size should be a few KB and at the bottom there should be the file name. No private information transits here, it's the addresses of the the blocks in the file, not their content.

Thank you for your help.

nraynaud

@ITJamie No, we don't have any hierarchical log system on the front side AFAIK.

ITJamie

@nraynaud So this is interesting.
there is no payload at all, and it takes quite awhile for any of the tabs (including headers) to show any data.
the response and request section are completely empty.

heres the "copied as curl"

curl 'http://<ip>/api/xwE65b7EvmOp46LgogDxER7co_8Jl1P2NktYW_oszOs' -X POST -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:96.0) Gecko/20100101 Firefox/96.0' -H 'Accept: */*' -H 'Accept-Language: en-US,en;q=0.5' -H 'Accept-Encoding: gzip, deflate' -H 'Referer: http://<ip>/' -H 'Content-Type: multipart/form-data; boundary=---------------------------274750692132175193903430548728' -H 'Origin: http://<ip>' -H 'Content-Length: 960097718' -H 'Connection: keep-alive' -H 'Cookie: <removed>'

ITJamie

@nraynaud
I left the above running until now in firefox. it still had not showed any data in response or request.

Once i refreshed the page I got this console error
importVms watchguard-dimension_2_2.ova TypeError: NetworkError when attempting to fetch resource. index.js:172:159005

This would seem to me that the page had been waiting for something all that time

ITJamie

@nraynaud sadly ive started to see import errors again...

Ive tried changing builds on the xoa side but it doesnt seem to fix it...
previous ovf files that were working have not stopped importing.

example of the error on xcp-ng side

Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] Importing raw VDI R:d744d9fee162 failed with exception Server_error(VDI_IO_ERROR, [ Device I/O errors ])
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] Raised Server_error(VDI_IO_ERROR, [ Device I/O errors ])
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] 1/12 xapi Raised at file ocaml/xapi/vhd_tool_wrapper.ml, line 75
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] 2/12 xapi Called from file lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] 3/12 xapi Called from file lib/xapi-stdext-pervasives/pervasiveext.ml, line 35
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] 4/12 xapi Called from file lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] 5/12 xapi Called from file lib/xapi-stdext-pervasives/pervasiveext.ml, line 35
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] 6/12 xapi Called from file ocaml/xapi/import_raw_vdi.ml, line 156
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] 7/12 xapi Called from file ocaml/xapi/import_raw_vdi.ml, line 194
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] 8/12 xapi Called from file ocaml/xapi/server_helpers.ml, line 100
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] 9/12 xapi Called from file ocaml/xapi/server_helpers.ml, line 121
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] 10/12 xapi Called from file lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] 11/12 xapi Called from file lib/xapi-stdext-pervasives/pervasiveext.ml, line 35
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] 12/12 xapi Called from file lib/backtrace.ml, line 177
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace]
Feb 24 15:08:32 xcp-ng-03958 xapi: [debug||1252 /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.logout D:aecf708cfad5 created by task D:6567b55f1ad9
Feb 24 15:08:32 xcp-ng-03958 xapi: [ info||1252 /var/lib/xcp/xapi|session.logout D:df9fcc048c68|xapi_session] Session.destroy trackid=ec26a660c6eeea965008c581e6547c0d
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||import] Caught exception in import handler: VDI_IO_ERROR: [ Device I/O errors ]
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] VDI.import D:6567b55f1ad9 failed with exception Unix.Unix_error(Unix.EPIPE, "single_write", "")
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] Raised Unix.Unix_error(Unix.EPIPE, "single_write", "")
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] 1/9 xapi Raised at file unix.ml, line 328
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] 2/9 xapi Called from file lib/xapi-stdext-unix/unixext.ml, line 469
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] 3/9 xapi Called from file lib/xapi-stdext-unix/unixext.ml, line 471
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] 4/9 xapi Called from file ocaml/xapi/import_raw_vdi.ml, line 232
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] 5/9 xapi Called from file ocaml/xapi/server_helpers.ml, line 100
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] 6/9 xapi Called from file ocaml/xapi/server_helpers.ml, line 121
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] 7/9 xapi Called from file lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] 8/9 xapi Called from file map.ml, line 135
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] 9/9 xapi Called from file sexp_conv.ml, line 147
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace]
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] VDI.import D:957854cadc4e failed with exception Unix.Unix_error(Unix.EPIPE, "single_write", "")
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] Raised Unix.Unix_error(Unix.EPIPE, "single_write", "")
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace] 1/1 xapi Raised at file (Thread 1158 has no backtrace table. Was with_backtraces called?, line 0
Feb 24 15:08:32 xcp-ng-03958 xapi: [error||1158 :::80||backtrace]
Feb 24 15:08:32 xcp-ng-03958 xapi: [debug||149 ||xenops] Event on VM 12558119-28e5-4a64-9053-1c0074c5b641; resident_here = true
Feb 24 15:08:32 xcp-ng-03958 xapi: [debug||149 ||dummytaskhelper] task timeboxed_rpc D:168d1d548a5c created by task D:a90e0cbb13bb

i also installed the official appliance on another ip. that worked correctly for loading the same ova files...

I did notice that the official ova image mentions node 14 during its upgrade process. I built from sources with node 17 since the xoa docs say to use latest. Think this issue could be down to using a much newer node version?

nraynaud

@ITJamie I'm sorry I can't answer about the node version until we get the bug.

I suspect there is some kind of compounding, where an error happens somewhere, but is lost by improper error handling, and no all we see is a corrupted state long after the error happened.

Arraylist

@ITJamie I am having the same issue!
Same error, also trying to import Watchguard Dimension 2.2.
I am on XOA 5.67 (node: 16.13.2) and XCP-ng 8.2.1.
I am using Windows and tried with Firefox 97 and Chrome 98, fails with both.
The VM also kind of gets created (with the [Importing] before the name, which never goes away).
Both disks also get created (Data disk looks complete, but System disk is always attached to control domain on host)