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

    Issues when upgrading with HA enabled

    Scheduled Pinned Locked Moved Solved Development
    26 Posts 4 Posters 9.2k Views 1 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.
    • ? Offline
      A Former User @olivierlambert
      last edited by A Former User

      @olivierlambert

      Hmm I've a feeling there is misunderstanding here 😄 Disabling HA doesnt effect the VMs running on the slave at all? And then when I've rebooted the master and enable HA again on the "slave (old master) I can transfer the VMS over back to it and then repeat the steps for all hosts? If thats the case then its ok 😃 It's just that I understood it as, if I disable the HA I can't get the connections back between the hosts without have to shut everything down and upgrade all hosts and then start everything up again.

      EDIT: "Disabling HA is straightforward, and just time to reboot your pool master (first)." - Yes I have learned my lesson the first time 🙂
      If I just wanna upgrade files with "yum update" -command through the CLI I dont need to disable it everytime?
      Is there a way to manually move the "master role"?

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

        Disabling HA won't do anything. Just migrate your VMs from the master (to any slave host), reboot it. That's pretty much it. Do the same for all your hosts (migrating VMs, rebooting, re-migrate VMs on it).

        When it's done, just re-enable HA.

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

          Don't mix things. yum update can be used to upgrade (from 7.4 to 7.5) but most of the time it's use to do simple updates (some doesn't require even to reboot the host).

          HA won't interfere until you decide to reboot a host.

          ? 1 Reply Last reply Reply Quote 0
          • ? Offline
            A Former User @olivierlambert
            last edited by A Former User

            @olivierlambert
            I was answering txsastre in the same post thus the misunderstanding I think. 🙂 And when I was going to disable HA on my host I got a message that indicated that it would break everything.
            But the way you describe it, it sounds ok. So basically, everytime one need to upgrade something, major/minor thats the way to do it, regardless if reboot is necessary or not?

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

              If you don't need to reboot, don't touch HA 🙂 HA is tricky when it comes to have hosts to reboot. I would avoid it in general BTW… more dangerous than helping in most of the cases.

              ? 1 Reply Last reply Reply Quote 0
              • ? Offline
                A Former User @olivierlambert
                last edited by

                @olivierlambert
                Okej, its that part that's tricky 😃 Yea maybe so, but it's cool. And makes the uptime better even if it's just a lab. I've been using vmware for a while at my last work. But the licensing is not nice for a homelab. So this is my first time with xcp-ng (xenserver). I'll try updating tomorrow. Thanks.

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