XOA Error when installing

kilo

Please note that my LAN is 192.168.0.x

olivierlambert

Because it's down. Put it up and see (or just reboot)

ZacApplegate

@olivierlambert any thoughts on my issue from the post above?

kilo

@olivierlambert @nackstein rebooted...and finally there........it really helped, you guys are great!...thnx a bunch for the support....

nackstein

uhm... I contributed to increase entropy. sorry. the original post was about another issue.

ZacApplegate

@olivierlambert any thoughts on my issue from the post above?

olivierlambert

Please select the right network with the web UI deploy interface on http://xen-orchestra.com/#!/xoa

ZacApplegate

@olivierlambert I tried each network option and I get the same error on all of them?

I installed xcp-ng with eth2 thats what the interface says and thats the one I have been trying to use.

sabival89

@ZacApplegate It appears that I am having the same issue and xapi0 doesn't appear when I run the ifconfig -a command.

@olivierlambert I have tried selecting each network option as well but to no avail.

olivierlambert

Okay so there's a problem while using this template with some XCP-ng/CH installs. But it's not clear why. Let me investigate.

olivierlambert

Is your XCP-ng fully up to date?

arvid

I just wanted to chime in to say that I had the same problem trying to install orchestra using the web interface and the curl script, but I was able to install it by downloading and importing the .xva in XCP-ng center.

This was on a fresh xcp-ng install on an old workstation with an intel i7 2600k.

olivierlambert

Okay so I modified the XVA, can you try again now?

olivierlambert

Ping @sabival89 @ZacApplegate and @arvid

arvid

@olivierlambert Yep, the web deploy worked for me now. I now have two xoa vms.

olivierlambert

\o/ Thanks a lot for your feedback.

To let you know why: for an unknown reason, the XVA exported included an incorrect bridge name, xapi0 instead of xenbr0.

So I had to unpack it, fix the XML with the right name and repack it. I remember it happened once in the past. Root cause is unclear but now I'll add extra checks before deploying, that bridge name is correct (everyone should have a xenbr0).

I couldn't spot the issue myself because in our test lab, we got xapi0 network, so it was working.

kilo

@olivierlambert How do i chech whether the xoa i have is exported with xapi0 or xenbr0 ?

olivierlambert

You don't, I replaced the one on our server right now. Don't check, just redeploy and you'll have the right version.

kilo

I have redeployed. now how do i verify that the xoa i have deployed is with a xapi0 or xenbr0

kilo

also facing this error