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

    Upgrade to XO v5.105 seems broken

    Scheduled Pinned Locked Moved Xen Orchestra
    9 Posts 6 Posters 462 Views 7 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.
    • love2scootL Offline
      love2scoot
      last edited by

      This was reported a few hours ago over on the XenOrchestraInstallerUpdater github page: https://github.com/ronivay/XenOrchestraInstallerUpdater/issues/288

      Just to be sure, I attempted a fresh install on top of Ubuntu v24.04LTS and found the same issues as upgrade attempts on my existing XO VMs.

      bluerockny created this issue in ronivay/XenOrchestraInstallerUpdater

      closed Update failure #288

      D 1 Reply Last reply Reply Quote 2
      • D Offline
        Davidj 0 @love2scoot
        last edited by

        This post is deleted!
        1 Reply Last reply Reply Quote 0
        • olivierlambertO Offline
          olivierlambert Vates 🪐 Co-Founder CEO
          last edited by olivierlambert

          We are aware of the issue and investigating. FYI, there's no version on the sources, just the last commit matters šŸ™‚

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

            I have 0 problem to build it in here following our doc. Are you sure it's not related to XO 6 build?

            $ yarn && yarn build
            yarn install v1.22.19
            warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
            [1/5] Validating package.json...
            [2/5] Resolving packages...
            success Already up-to-date.
            $ husky install
            husky - Git hooks installed
            Done in 0.57s.
            yarn run v1.22.19
            $ TURBO_TELEMETRY_DISABLED=1 turbo run build --filter xo-server --filter xo-server-'*' --filter xo-web
            ╭──────────────────────────────────────────────────────────────────────────╮
            │                                                                          │
            │                     Update available v2.4.2 ≫ v2.4.4                     │
            │    Changelog: https://github.com/vercel/turborepo/releases/tag/v2.4.4    │
            │             Run "npx @turbo/codemod@latest update" to update             │
            │                                                                          │
            │          Follow @turborepo for updates: https://x.com/turborepo          │
            ╰──────────────────────────────────────────────────────────────────────────╯
            turbo 2.4.2
            
            • Packages in scope: xo-server, xo-server-audit, xo-server-auth-github, xo-server-auth-google, xo-server-auth-ldap, xo-server-auth-oidc, xo-server-auth-saml, xo-server-backup-reports, xo-server-load-balancer, xo-server-netbox, xo-server-perf-alert, xo-server-sdn-controller, xo-server-test, xo-server-test-plugin, xo-server-transport-email, xo-server-transport-icinga2, xo-server-transport-nagios, xo-server-transport-slack, xo-server-transport-xmpp, xo-server-usage-report, xo-server-web-hooks, xo-web
            • Running build in 22 packages
            • Remote caching disabled
            
             Tasks:    27 successful, 27 total
            Cached:    27 cached, 27 total
              Time:    251ms >>> FULL TURBO
            
            Done in 0.43s.
            
            I 1 Reply Last reply Reply Quote 0
            • I Offline
              irtaza9 @olivierlambert
              last edited by

              @olivierlambert you are not checking the typescript level traces that's why there's no errors happening at your end.

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

                I'm building following the official documentation šŸ™‚

                F 1 Reply Last reply Reply Quote 1
                • P Offline
                  ph7 @irtaza9
                  last edited by

                  @irtaza9
                  My updates (from docs) work, except the v6
                  https://xcp-ng.org/forum/topic/10685/xo-ce-82ed2-and-5c390-update.

                  I 1 Reply Last reply Reply Quote 1
                  • I Offline
                    irtaza9 @ph7
                    last edited by

                    @ph7 Thank you. It seems to work like that. I'll wait for this fix.

                    1 Reply Last reply Reply Quote 0
                    • F Offline
                      fdhabhar @olivierlambert
                      last edited by

                      This post is deleted!
                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post