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

    Pool is connected but Unknown pool

    Scheduled Pinned Locked Moved Xen Orchestra
    21 Posts 3 Posters 6.5k Views 4 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.
    • Tristis OrisT Offline
      Tristis Oris Top contributor @olivierlambert
      last edited by

      @olivierlambert so since it works at XOA, what to do now?
      Is it because some difference at codebase?

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

        Your freshly deploy XOA is outdated. You need to register it to be able to download latest updates. Otherwise, it's not relevant to compare both.

        Tristis OrisT 1 Reply Last reply Reply Quote 0
        • Tristis OrisT Offline
          Tristis Oris Top contributor @olivierlambert
          last edited by

          @olivierlambert
          Current version: 5.73.1 - XOA build: 20210823

          • node: 16.14.2
          • npm: 8.12.1
          • xen-orchestra-upload-ova: 0.1.4
          • xo-server: 5.100.1
          • xo-server-telemetry: 0.5.0
          • xo-server-xoa: 0.14.0
          • xo-web-free: 5.101.1
          • xoa-cli: 0.31.0
          • xoa-updater: 0.43.1

          pool available.

          olivierlambertO 1 Reply Last reply Reply Quote 0
          • Tristis OrisT Offline
            Tristis Oris Top contributor
            last edited by

            also i tried to reset configuration on test copy.

                redis-cli
                FLUSHALL
                systemctl restart xo-server.service
            

            then manually add this pool to empty system. Problem still exist.

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

              @Tristis-Oris Okay now try to switch to latest branch (update and retry)

              Tristis OrisT 1 Reply Last reply Reply Quote 0
              • Tristis OrisT Offline
                Tristis Oris Top contributor @olivierlambert
                last edited by Tristis Oris

                @olivierlambert
                commit 6cbce, again reset DB - pool still unknown.

                also i restore XO from backup 27 aug.
                Xen Orchestra, commit b89e7
                xo-server 5.100.1
                xo-web 5.101.1

                pool available.
                then updated to commit 6cbce > again unknown pool.

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

                  1. Try with XOA latest
                  2. Alternatively, try to find the exact commit that make your failing when you connect.
                  Tristis OrisT 2 Replies Last reply Reply Quote 0
                  • Tristis OrisT Offline
                    Tristis Oris Top contributor @olivierlambert
                    last edited by Tristis Oris

                    @olivierlambert

                    1. yes, im finally on latest😁 step by step.
                      Current version: 5.74.0 - XOA build: 20210823
                    • node: 16.14.2
                    • npm: 8.12.1
                    • xen-orchestra-upload-ova: 0.1.4
                    • xo-server: 5.101.0
                    • xo-server-telemetry: 0.5.0
                    • xo-server-xoa: 0.15.0
                    • xo-web-free: 5.102.0
                    • xoa-cli: 0.31.0
                    • xoa-updater: 0.43.1

                    pooll is unknown.

                    1. i restored latest working backup i have. commit c1846, Aug 25.
                      so it broken between 25-31 aug.
                      any advise how to update for certain commit?
                    1 Reply Last reply Reply Quote 0
                    • Tristis OrisT Tristis Oris referenced this topic on
                    • Tristis OrisT Offline
                      Tristis Oris Top contributor @olivierlambert
                      last edited by

                      @olivierlambert got it. we modifed update script from sources to update for certain commit.

                      problem happens on this one.
                      https://github.com/vatesfr/xen-orchestra/commit/4dc7575d5bed3851a800840897f1ae3e19f224b8

                      0 MathieuRA committed to vatesfr/xen-orchestra
                      feat(xo-web/storage): display SR used for the HA state files (#6384)
                      
                      Fixes #6339
                      1 Reply Last reply Reply Quote 0
                      • olivierlambertO Offline
                        olivierlambert Vates 🪐 Co-Founder CEO
                        last edited by

                        Thanks. Pinging @julien-f about this 🙂

                        julien-fJ 1 Reply Last reply Reply Quote 0
                        • julien-fJ Offline
                          julien-f Vates 🪐 Co-Founder XO Team @olivierlambert
                          last edited by

                          Thank you for your reports, we have pinpointed the issue and we'll fix it soon 🙂

                          https://github.com/vatesfr/xen-orchestra/pull/6404

                          MathieuRA opened this pull request in vatesfr/xen-orchestra

                          closed fix(xo-server): handle unfetched VDIs in pool.$ha_statefiles #6404

                          Tristis OrisT 1 Reply Last reply Reply Quote 2
                          • Tristis OrisT Offline
                            Tristis Oris Top contributor @julien-f
                            last edited by Tristis Oris

                            @julien-f @olivierlambert
                            2371109b6fea26c15df28caed132be2108a0d88e
                            Fixed now, thanks you.

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