XOA deploy error
-
@fatek I'm getting the same error. It's "INVALID_VALUE" for anyone searching the forum.
Trying to deploy via https://vates.tech/deploy/ I get another error, just two curly brackets: "{}"
I'll try the shell script, but I hope the web deploy options get fixed soon. I really appreciated how simple it was to deploy XOA on XCP-ng 8.2
-
No worries, we'll investigate ASAP!
-
@julien-f can you handle this for me?
-
-
I cannot reproduce on my lab, will check if I can trigger the issue elsewhere.
-
I experienced the same issue just now. Fresh install of 8.3 RC2 followed by XOA install from XO-LITE and got the same INVALID_VALUE error.
Tried from the Vates deploy site and got the same {} error.
Tried via bash script and XOA deployed successfully.
-
Deployment via vates.tech:
Payload:
{ "jsonrpc": "2.0", "method": "VM.import", "params": [ "OpaqueRef:ffc7769e-7f87-1cd4-d663-e0708c8668f1", "http://xoa.io/xva", "OpaqueRef:c4654571-863f-6eb2-f015-9055e29ecb98", false, false ], "id": 1 }
Response:
{ "jsonrpc": "2.0", "error": { "code": 1, "message": "INVALID_VALUE", "data": [ "bridge", "xapi1" ] }, "id": 1 }
After this I see an exclamation point in a red circle and an error message that's just {}. Other jsonrpc payloads seem to work. I can see my networks and datastores just fine.
Deployment via XO Lite
Payload:
{ "jsonrpc": "2.0", "id": 20, "method": "VM.import", "params": [ "OpaqueRef:a364cc08-dda6-f218-bd51-4956b4f18477", "http://xoa.io:8888/", "OpaqueRef:c4654571-863f-6eb2-f015-9055e29ecb98", false, false ] }
Response:
{ "jsonrpc": "2.0", "error": { "code": 1, "message": "INVALID_VALUE", "data": [ "bridge", "xapi1" ] }, "id": 20 }
After this I see the error message that @fatek posted a screenshot of.
-
That's interesting, can you check the
/var/log/xensource.log
file? -
I think I have lead, it's not due to the deploy script, but the XVA itself. Stay tuned.
-
Hello @kbsp @stefanflegg and @fatek, a new XOA image has just been uploaded. Can you test it and keep us posted?
-
@nathanael-h Deployment via vates.tech was successful!
-
Thank you, I am now able to deploy XOA!
-
Great news Thanks for reporting the issue, it was rather subtle.
-
@olivierlambert said in XOA deploy error:
Great news Thanks for reporting the issue, it was rather subtle.
Do I get a prize for that? maybe some ice crea or candy?
-
I just installed 3 fresh nodes of 8.2.1 and could not deploy via vates or via script, I then installed 8.3 rc2 and neither are working. 3 days ago, I was able to use script to install XOA and today no luck. I have tried with and without DHCP. Attaching log from rc2.xoa log.txt
8.2.1
8.3
-
Please try to deploy with the bash script and report if you have a more details error (otherwise it should be displayed inside the /var/log/xensource.log)
-
@olivierlambert I did this, log is attached original message above
. -
Sorry missed it. So "IMPORT_ERROR_PREMATURE_EOF" means something stopped the download before it was finished.
You can try to download XOA first, then use the deploy script locally to see if it's better. Follow this: https://xen-orchestra.com/docs/airgap.html#deploy-your-air-gap-xoa
-
link above uses https and I get this error
[16:39 r530-n3 ~]# curl https://xoa.io/deploy > deploy.sh
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (35) OpenSSL/1.0.2k-fips: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failureuse http instead downloads script
[16:39 r530-n3 ~]# curl http://xoa.io/deploy > deploy.sh
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 4970 100 4970 0 0 20525 0 --:--:-- --:--:-- --:--:-- 20622
[16:40 r530-n3 ~]# cat deploy.shWe did figure out Fortinet was blocking something for port 8888 and the FW admin adding xao.io to allow list, normal bash script started working, I tried curl https://xoa.io/deploy > deploy.sh after install and get same openssl error (not that I need to worry about it now).
Thanks for the assistance.
-
So now regular deploy should work