XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    XOA Quick Deploy

    Scheduled Pinned Locked Moved Xen Orchestra
    29 Posts 11 Posters 9.6k Views 6 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • stormiS Offline
      stormi Vates 🪐 XCP-ng Team @Danp
      last edited by

      @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
      
      DanpD 1 Reply Last reply Reply Quote 2
      • DanpD Online
        Danp Pro Support Team @stormi
        last edited by

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

        stormiS 1 Reply Last reply Reply Quote 0
        • stormiS Offline
          stormi Vates 🪐 XCP-ng Team @Danp
          last edited by

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

          1 Reply Last reply Reply Quote 0
          • J Offline
            jcapagcuan-svi
            last edited by

            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.

            1 Reply Last reply Reply Quote 0
            • olivierlambertO Online
              olivierlambert Vates 🪐 Co-Founder CEO
              last edited by

              Hi,

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

              J 1 Reply Last reply Reply Quote 0
              • J Offline
                jcapagcuan-svi @olivierlambert
                last edited by

                @olivierlambert XCP-NG 8.2

                J 1 Reply Last reply Reply Quote 0
                • J Offline
                  jcapagcuan-svi @jcapagcuan-svi
                  last edited by

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

                  1 Reply Last reply Reply Quote 0
                  • PielanderP Offline
                    Pielander
                    last edited by

                    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!

                    1 Reply Last reply Reply Quote 0
                    • olivierlambertO Online
                      olivierlambert Vates 🪐 Co-Founder CEO
                      last edited by

                      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!

                      PielanderP 1 Reply Last reply Reply Quote 0
                      • PielanderP Offline
                        Pielander @olivierlambert
                        last edited by

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

                        1 Reply Last reply Reply Quote 0
                        • M Offline
                          Moxified
                          last edited by

                          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.

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post