XOA import script failing silently

xc3pee0

On a fresh install of xcp-ng 7.6.0, I am trying to setup XOA as the first guest-

bash -c "$(curl -s http://xoa.io/deploy)"

At first this failed silently after 10s or so no command line response at all. This turned out to be my DNS resolver not being enabled for the VLAN I created for this new xcp-ng host.

With that fixed, the script now runs. It also confirms "Your XOA will be started using DHCP", also Importing XOA VM... but then, returns to the prompt silently after a few minutes.

If I do xe-disk-vmlist, or look in the console for a shiny new XOA guest VM, there's nothing there...

I am guessing this is caused by connectivity, but can't imagine where.

During installation, I configured the xcp-ng host to connect to the correct VLAN ID where the USB installer dialogue prompted me. Verfied this as the host was assigned the correct static IP, hostname, DNS and NTP settings by the router. Local DNS is verified working (now), and I also setup (and checked) the firewall rules to allow outbound http and https traffic for all hosts.

Does xcp-ng or the the XOA deploy script require special connectivity to work?

olivierlambert

No "special" connectivity. Do you have a proxy or something like that? Basically, it calls a VM import on a specific URL.

Also, we'll have very soon an even easier deploy method, so I'll get back to you for a test on this new import method

borzel

@xc3pee0 did you set a default SR?

xc3pee0

@olivierlambert Thank you! If I can't run XOA by then, I fear I will be your keenest tester candidate!

Good idea re the proxy. I disabled my IDS but it made no difference. I don't see any log entries showing web requests being blocked/sent to nowhere.

This is the exact output, failure must be at the last line

# bash -c "$(curl -s http://xoa.io/deploy)"

Welcome to the XOA auto-deploy script!

Network settings:
IP address? [dhcp] 

Your XOA will be started using DHCP

Importing XOA VM...
# xe vm-disk-list *
Error: No matching VMs found
#

xc3pee0

@borzel Thanks for suggesting that. I've been trying to figure out how to verify what is presently set, and what it should be before changing things around.

The install doesn't seem to complain. I think sr-list outputs a list of the local Storage Repositories. All look in order to me, though none are shown as the 'default SR'.

#xe sr-list
uuid ( RO)                : 4c688668-4dc6-b3h6-809b-0b7bd24d9e87
          name-label ( RW): XCP-ng Tools
    name-description ( RW): XCP-ng Tools ISOs
                host ( RO): bmhost
                type ( RO): iso
        content-type ( RO): iso


uuid ( RO)                : f0fb7153-b98a-dd87-76f3-8b1924d0312d
          name-label ( RW): Removable storage
    name-description ( RW): 
                host ( RO): bmhost
                type ( RO): udev
        content-type ( RO): disk


uuid ( RO)                : 29724485-bfba-4263-43e9-6141e76bze35
          name-label ( RW): DVD drives
    name-description ( RW): Physical DVD drives
                host ( RO): bmhost
                type ( RO): udev
        content-type ( RO): iso


uuid ( RO)                : 5145f480-47da-a2ab-a4f2-9a0a4h625ef8
          name-label ( RW): Local storage
    name-description ( RW): 
                host ( RO): bmhost
                type ( RO): ext
        content-type ( RO): user

I guess the last one is the default SR, as I opted to allow thin provisioning in the installer (it says this forces the SR to be created as an ext partition), and as you can see above, it is the only one formatted as ext.

Maybe I'm not doing this right (?)

olivierlambert

Hi!

The new standard way to import is here: https://xen-orchestra.com/#!/xoa

Let me know if you have any issue. It's still in beta yet, and we got one small issue to fix (it won't fetch the XO username/password, so it's still admin@admin.net / admin)