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

    Host failure after patches

    Scheduled Pinned Locked Moved Management
    21 Posts 2 Posters 323 Views 3 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.
    • M Offline
      McHenry @McHenry
      last edited by

      With a new pool master I am still unable to access the old pool slave as it reports the pool master is unavailable:
      b2daad97-a7e1-4701-9852-788599fae4ea-image.png

      I expect this is because the pool slave is still looking for the old pool master and has not identified that a new pool master exists.

      What needs to be done to the pool slave to have it appear as a member of the pool again?

      F 1 Reply Last reply Reply Quote 0
      • F Offline
        flakpyro @McHenry
        last edited by

        @McHenry did you run

        xe pool-recover-slave
        

        after selecting a new master?

        M 1 Reply Last reply Reply Quote 0
        • M Offline
          McHenry @flakpyro
          last edited by McHenry

          @flakpyro

          No I didn't. Does this need to be run on the slave itself or the new master?

          When you say "after selecting a new master" do you mean after I did this on the new master?

          xe pool-emergency-transition-to-master
          

          Edit:
          Found this which shows this is run on the new pool master:
          https://www.ervik.as/how-to-change-the-pool-master-in-a-xenserver-farm/

          F 1 Reply Last reply Reply Quote 0
          • F Offline
            flakpyro @McHenry
            last edited by

            @McHenry

            Yes you'd run that command on the pool master.

            I linked this earlier in the thread, it outlines the process you need to follow:
            https://docs.xenserver.com/en-us/xenserver/8/dr/machine-failures.html

            Let us know if this works!

            M 1 Reply Last reply Reply Quote 0
            • M Offline
              McHenry @flakpyro
              last edited by

              @flakpyro

              Apologies, I missed that. I have run the command and now see:
              cda41870-c92a-4ff4-a0c5-3359db209d05-image.png

              hst103 is the new pool master. hst100 is the old pool master that failed.

              In XO I can only see hst103 under hosts however all three hosts are listed under the pool:
              c7ec1829-fd07-486e-9280-723544d3a1b3-image.png

              F 1 Reply Last reply Reply Quote 0
              • F Offline
                flakpyro @McHenry
                last edited by

                @McHenry Have you tried restarting the toolstack on the hosts since running pool-recover-slave?

                I have only had to do this once before but remember it going fairly smoothly at the time. (As smooth as you can expect a host failure to be anyways)

                M 1 Reply Last reply Reply Quote 0
                • M Offline
                  McHenry @flakpyro
                  last edited by McHenry

                  @flakpyro

                  Have restarted the tool stack but no different.

                  When I view hst110 I see:
                  30f512bf-b0e0-4aea-ac57-6912519c401d-image.png

                  I was tempted to restart it however it has Patches pending installation after a restart and as the mater is not fully patched I thought best not to restart it. I understand the master needs to be patched first.

                  I just checked xsconsole on hst110 and it shill shows pool master unavailable
                  8bdfff57-f781-4bfe-b970-685c6e7da261-image.png

                  Do I need to change the pool master used by the slave?
                  d7798915-9ee9-480c-889f-b700f48a7f97-image.png

                  F 1 Reply Last reply Reply Quote 0
                  • F Offline
                    flakpyro @McHenry
                    last edited by

                    @McHenry I am wondering if you are in a situation where you need to reboot. You have patches installed but have not rebooted, but have restarted tool stacks on the salves, which means some components have restarted and are running on their new versions? If you have support it may be best to reach out to Vates for guidance.

                    M 1 Reply Last reply Reply Quote 0
                    • M Offline
                      McHenry @flakpyro
                      last edited by

                      @flakpyro

                      Can I restart the slave and install patches if the master has not been patched yet?

                      F 1 Reply Last reply Reply Quote 0
                      • F Offline
                        flakpyro @McHenry
                        last edited by

                        @McHenry No the pool master must always been patched and rebooted first. Do you have a pool metadata backup? Are your VMs on shared storage of some sort? In case you need to rebuild the pool.

                        M 2 Replies Last reply Reply Quote 0
                        • M Offline
                          McHenry @flakpyro
                          last edited by

                          @flakpyro

                          My setup is pretty basic.
                          I have two hosts in the pool, one for running VMs on local storage and one for DR backups on local storage.
                          I'd like to setup shared storage so i could run the VMs on multiple hosts and seamlessly move them between hosts without migrating storage too.

                          To setup shared storage would this be on an xcp-ng host or totally independent of xcp-ng?

                          1 Reply Last reply Reply Quote 0
                          • M Offline
                            McHenry @flakpyro
                            last edited by

                            @flakpyro

                            All this complexity makes me question the advantages of having all hosts in the same pool.

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