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

    HA Operation Would Break Failover Plan

    Scheduled Pinned Locked Moved Solved Advanced features
    13 Posts 4 Posters 779 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
      Midget
      last edited by

      I got my environment back up and running. Reloaded all 3 hosts, wiped the drives, rebuilt the XOSTOR, and enabled HA. I built a simple Debian 12 VM on one of the hosts using the XOSTOR. But when I try to enable HA in the advance options tab, I get the output I've posted below. What am I doing wrong now? 😐

      vm.set
      {
        "high_availability": "restart",
        "id": "62dde87b-5dbf-119f-07aa-94434ca348b3"
      }
      {
        "code": "HA_OPERATION_WOULD_BREAK_FAILOVER_PLAN",
        "params": [],
        "call": {
          "method": "VM.set_ha_restart_priority",
          "params": [
            "OpaqueRef:207f8ee7-3b24-405f-a021-0a7a35b3a7d5",
            "restart"
          ]
        },
        "message": "HA_OPERATION_WOULD_BREAK_FAILOVER_PLAN()",
        "name": "XapiError",
        "stack": "XapiError: HA_OPERATION_WOULD_BREAK_FAILOVER_PLAN()
          at Function.wrap (file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/_XapiError.mjs:16:12)
          at file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/transports/json-rpc.mjs:35:21
          at runNextTicks (node:internal/process/task_queues:60:5)
          at processImmediate (node:internal/timers:447:9)
          at process.callbackTrampoline (node:internal/async_hooks:130:17)"
      }
      
      1 Reply Last reply Reply Quote 0
      • olivierlambertO Offline
        olivierlambert Vates 🪐 Co-Founder CEO
        last edited by

        So you have HA enabled on the pool, right? How did you enabled in the first place? (the command used)

        M 1 Reply Last reply Reply Quote 0
        • M Offline
          Midget @olivierlambert
          last edited by

          @olivierlambert

          xe pool-ha-enable heartbeat-sr-uuids=<XOSTOR UUID>
          

          I ran this on the pool master.

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

            Can you do a xe pool-ha-compute-max-host-failures-to-tolerate please?

            M 1 Reply Last reply Reply Quote 0
            • M Offline
              Midget @olivierlambert
              last edited by

              @olivierlambert 3 good Sir.

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

                Hmm that's probably the issue 🤔

                Can you do xe pool-param-set ha-host-failures-to-tolerate=2 uuid=pool-uuid and then retry to enable HA on your VM?

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

                  It's been a long week. I have wasted your time. I never installed the guest tools.../facepalm

                  EDIT
                  I realized it right after I ran that command. HA is now enabled.

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

                    So the error message was not great. It worked a soon you got tools installed in the VM?

                    M 1 Reply Last reply Reply Quote 0
                    • M Offline
                      Midget @olivierlambert
                      last edited by

                      @olivierlambert Correct Sir. I apologize for wasting your time.

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

                        Don't worry. The error message was not great. Time to enjoy the week-end 🙂

                        1 Reply Last reply Reply Quote 0
                        • olivierlambertO olivierlambert marked this topic as a question on
                        • olivierlambertO olivierlambert has marked this topic as solved on
                        • A Offline
                          arc1
                          last edited by

                          Hi,
                          I'm getting same error - HA_OPERATION_WOULD_BREAK_FAILOVER_PLAN() - when I try to put host in maintenance mode.
                          I have 3 nodes in pool and I set xe pool-ha-compute-max-host-failures-to-tolerate to 1.
                          In error log I'm not able to find why causes this error.
                          Any ideas? Tools are installed on all VMs.

                          DanpD 1 Reply Last reply Reply Quote 0
                          • DanpD Online
                            Danp Pro Support Team @arc1
                            last edited by

                            @arc1 What does xe pool-ha-compute-max-host-failures-to-tolerate return?

                            A 1 Reply Last reply Reply Quote 0
                            • A Offline
                              arc1 @Danp
                              last edited by arc1

                              @Danp said in HA Operation Would Break Failover Plan:

                              xe pool-ha-compute-max-host-failures-to-tolerate

                              It returns 1.:
                              [13:34 log]# xe pool-ha-compute-max-host-failures-to-tolerate
                              1

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