XOA deploy error

nathanael-h

Hello @kbsp @stefanflegg and @fatek, a new XOA image has just been uploaded. Can you test it and keep us posted?

kbsp

@nathanael-h Deployment via vates.tech was successful!

fatek

Thank you, I am now able to deploy XOA!

olivierlambert

Great news Thanks for reporting the issue, it was rather subtle.

fatek

@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?

newbie2xcp

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

olivierlambert

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)

newbie2xcp

@olivierlambert I did this, log is attached original message above
.

olivierlambert

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

newbie2xcp

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 failure

use 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.sh

We 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.

olivierlambert

So now regular deploy should work

stefanflegg

Just tested the newly released 8.3 iso and I can confirm that XOA deployed as expected.

olivierlambert

Thank you for your feedback @stefanflegg !

HamiltonWDS

I know this has been some time for this thread, but raising it due to having the same issue and finding via a web search.
I encountered the same problems when attempting to deploy from the Website and XO-Lite. I also had a failure when trying to download the deploy.sh. The cause of the problems appears to be due to outdated OpenSSL version (OpenSSL/1.0.2k-fips) when using curl.

I am using the latest XCP-ng version of 8.3
I did perform an update after the installation.

Running the command:

curl https://xoa.io/deploy > deploy.sh

Results in:

  % 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 failure

Running:

curl --version

Results in:

curl 8.6.0 (x86_64-koji-linux-gnu) libcurl/8.6.0 OpenSSL/1.0.2k-fips zlib/1.2.7 OpenLDAP/2.4.44
Release-Date: 2024-01-31
Protocols: dict file ftp ftps gopher gophers http https imap imaps ipfs ipns ldap ldaps pop3 pop3s rtsp smtp smtps telnet tftp
Features: AsynchDNS GSS-API HSTS HTTPS-proxy IPv6 Kerberos Largefile libz NTLM SPNEGO SSL threadsafe UnixSockets

I was not successful in updating OpenSSL or Certificates (I did not add any respositories).

However, downloading the deploy.sh script by wget was successful and I was able to then deploy XOA.

olivierlambert

Add @nathanael-h to take a look

nathanael-h

@HamiltonWDS Thanks for the report. As it works with wget let use it! I'll switch from curl to wget in doc. In the meantime some colleagues will investigate more.