XOA can't start after installation and contradictory messages

olivierlambert

As I said, it's an edge case we didn't think before. So, obviously, we'll improve this (but first we need to reproduce the issue). Can you print the output of xe network-list on this host? I'm trying to understand why you don't have a network 0.

MajorTom

@olivierlambert

Sure.

# xe network-list
uuid ( RO)                : 64aeff7a-42ed-e455-fcc0-1f6b259046cb
          name-label ( RW): VLAN4
    name-description ( RW): VLAN4
              bridge ( RO): xapi3


uuid ( RO)                : 19d85500-c600-7476-13d4-6cb45b068186
          name-label ( RW): Bond 0+1
    name-description ( RW):
              bridge ( RO): xapi2


uuid ( RO)                : f9718515-8820-96d3-0ab9-1195d1c27def
          name-label ( RW): VLAN21
    name-description ( RW): VLAN21
              bridge ( RO): xapi6


uuid ( RO)                : adfcd92c-c127-8058-6f0e-fd0258383738
          name-label ( RW): Host internal management network
    name-description ( RW): Network on which guests will be assigned a private link-local IP address which can be used to talk XenAPI
              bridge ( RO): xenapi


uuid ( RO)                : 7c168d4b-6e5e-b2fa-249a-167792c9c641
          name-label ( RW): VLAN7
    name-description ( RW): VLAN7
              bridge ( RO): xapi4


uuid ( RO)                : c2fe838d-b71c-7520-8fc4-5998656c2a83
          name-label ( RW): VLAN20
    name-description ( RW): VLAN20
              bridge ( RO): xapi1


uuid ( RO)                : 77097537-8e7b-f375-abd6-d638ac42abcc
          name-label ( RW): Pool-wide network associated with eth0
    name-description ( RW):
              bridge ( RO): xenbr0


uuid ( RO)                : 7ea15b78-ff08-1285-f6d4-922fa35a22ca
          name-label ( RW): VLAN8
    name-description ( RW): VLAN8
              bridge ( RO): xapi5


uuid ( RO)                : 6c8acc25-f1f8-8d8f-c5c3-ee4c519d9825
          name-label ( RW): Pool-wide network associated with eth1
    name-description ( RW):
              bridge ( RO): xenbr1


uuid ( RO)                : 591ab537-8a76-1526-82ca-97908b86c444
          name-label ( RW): VLAN3
    name-description ( RW): VLAN3
              bridge ( RO): xapi0

olivierlambert

Thanks, we'll try to see if we could detect this case for an update on deploy script

MajorTom

@olivierlambert You're welcome.

As a start, to prevent false positive message that the XOA VM is ready at some IP address, the script could check the power-state in the result of

# xe vm-list name-label=XOA
uuid ( RO)           : e58ce2ec-4fe4-5a9f-70b1-f6a5ca204946
     name-label ( RW): XOA
    power-state ( RO): running

(whether running or not).

Low351

I realize this is an old topic, but that make me realize it's unfortunate that this hasn't been fixed at this point.
I tried to use the command line to install XOA and it complains with the same error. In my case it's because I am using bonded interfaces just like the OP. Surprising that it doesn't come up more often but I guess if you set this up before you bond the interfaces it's not an issue.

olivierlambert

@Low351 that's because the deploy script isn't the main/advised way to deploy XOA So it's lower in our backlog (vs the deploy UI from our website or even from within XCP-ng web page)

edit: I'll check with our teams if someone could add network selection quickly in the deploy script (which will hopefully solve the issue)

edit 2: investigating IF this will solve the issue first

julien-f

The deploy script is a very basic tool used as a fallback when the UI deploy is not available.

@Low351 Are you able to use the web quick deploy? https://xen-orchestra.com/#!/xoa

low351 0

@julien-f Yes, I realize that after. I finally just downloaded the ova and installed it that way, it's working fine. Thank you!

Low351

@olivierlambert It would be nice to have but as you stated originally not a real priority. I installed using the .ova without issue. Thanks for responding.

olivierlambert

FYI, we modified the deploy script to be able to automatically modify XOA's VIF to run on the management network.

So even in case of using only bonded networks like @Low351, this will now work.