XOA Quick Deploy

Danp

@julien-f The command was run directly on my xcp-ng 8.2 host.

# curl --version
curl 7.29.0 (x86_64-redhat-linux-gnu) libcurl/7.29.0 NSS/3.34 zlib/1.2.7 libidn/1.28 libssh2/1.4.3
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp scp sftp smtp smtps telnet tftp
Features: AsynchDNS GSS-Negotiate IDN IPv6 Largefile NTLM NTLM_WB SSL libz unix-sockets

julien-f

@danp Thanks for your help, it appears the version of curl available on XCP-ng 8.2 (or CH 8.2) is very old and does not support any ciphers available on https://xoa.io

You can use wget to work around this (we'll update the docs):

> bash -c "$(wget -qO- https://xoa.io/deploy)"

Danp

@julien-f said in XOA Quick Deploy:

bash -c "$(wget -qO- https://xoa.io/deploy)"

Thanks, that appears to be working. But it doesn't explain why both web based methods are failing.

olivierlambert

That's unrelated. Or at least, we did tests and it works here (on multiple hosts).

Danp

@olivierlambert I just tried the Quick Deploy on your website and it appears to be working now. When I tried it this morning, I couldn't get past the initial "connect" screen (tried with both FF and Chrome).

Still having issues with the local deploy via XCP-ng. Looking at the browser console, it appears to be having issues loading jQuery --

olivierlambert

I can't reproduce with a local deploy on a stock XCP-ng 8.2

It's weird you got a forbidden. Anyone else having the issue?

Danp

@olivierlambert said in XOA Quick Deploy:

stock XCP-ng 8.2

FWIW, I do have the latest test packages installed on my server.

stormi

@danp What's the output of rpm -q xapi-core? You may have a test version of XAPI that regressed on serving files from the webpage.

Danp

@stormi

# rpm -q xapi-core
xapi-core-1.249.10-1.1.xcpng8.2.x86_64

stormi

@danp OK, so the 403 errors will be solved if you downgrade to the latest released update:

yum downgrade xapi-core xapi-tests xapi-xe

Danp

@stormi Thanks for the solution. Was this a known issue with the test packages?

stormi

@danp Yes, see https://xcp-ng.org/forum/post/42132

jcapagcuan-svi

Hi,

I'm having the same issues and I tried bash -c "$(curl -sS http://xoa.io/deploy)" (notice http only to skip the ssl error). I am stuck in Importing XOA VM. Whenever I check xe vm-list it says XOA is halted. Tried starting it manually but still no luck.

Here's my xapi-core version xapi-core-1.249.9-1.1.xcpng8.2.x86_64 . I tried upgrading and downgrading but still no luck. Not sure how to troubleshoot this issue.

olivierlambert

Hi,

On what XCP-ng or XenServer version are you trying to deploy it?

jcapagcuan-svi

@olivierlambert XCP-NG 8.2

jcapagcuan-svi

@jcapagcuan-svi It's a supermicro servers with 32 cores cpu and 128GB memory

Pielander

I've just had exactly the same problems - XOA wouldn't deploy either through the web interface or the CLI. After much squinting and pondering and trial and error, I eventually traced it to a DNS issue. I changed the DNS nameserver to 1.1.1.1 and it now works perfectly.

I then excitedly looked for this thread again to post the solution, and accidentally came across this very similar thread where the solution is in the first reply. https://xcp-ng.org/forum/topic/4500/xoa-deployment-issue

Oh well, those are 2 hours of my life I'll never get back! I hope this helps someone else!

olivierlambert

Hi! Thanks for the feedback. The issue was "on your side"? (ie DNS you filled incorrectly initially?) or on ours? I mean, is there anything we can do to improve this from our perspective?

Thanks!

Pielander

@olivierlambert The issue was very much on my side (the network configuration was DHCP, so I blame my router). It was definitely not caused by XCP-NG itself.

I suppose the only thing that could potentially be refined on your side is the signposting, as the error message is a little cryptic. Having said that, the error says "source not found", which is absolutely accurate, and I guess there's no way for the installer to know why it can't find the source repository!

The main reason I posted was so the information would be available in this thread whenever the next person searches the same error, but thank you for following it up anyway. This forum is a great resource, and I'm sure I'm not the only one who really appreciates you taking the time to engage with the community and look for opportunities for improvement.

Moxified

I know this is quite old but wanted to update with additional findings.

I had the same error and it turns out you are using a non-standard port. In this case, tcp/8888 which I have blocked on my perimeter firewall.