XOA suddenly "empty" during rolling update
-
During rolling updates, XOA suddenly becomes "empty". The rolling update task is visible under "Tasks", but everything else is gone. Seems like it happens when XOA is migrated off one of the hosts, and everything comes back again when the hosts in question have been patched.
It happens every time we do the rolling update. Is this a known issue? All users logging in while this is happening are seeing the same thing.
-
@halvor This happens when the Master host is unreachable (first to be rebooted). XOA should connect again after the Master host reboots and is available (which could take a while depending on the host reboot time).
-
@Andrew
Aha! So by design? -
@halvor Yes, kind of... The pool master must be updated and rebooted first. If you move the master to a different host then you are no longer rebooting the pool master first. XOA is just a very smart client and needs the pool master to provide all of the pool information. Secondary machines will just redirect to the master, so if you try to connect XOA to one as a backup it won't work.
You just need to wait for the master to reboot and return to a functioning state and wait for XOA to automatically reconnect. The everything will start happening again.
If your master host is destroyed (ie. software corruption, hardware failure) then an existing host can be forced to take over the pool as master, but this is not a good thing to do unless the actual pool master is unrecoverable.
-
@Andrew said in XOA suddenly "empty" during rolling update:
@halvor Yes, kind of... The pool master must be updated and rebooted first. If you move the master to a different host then you are no longer rebooting the pool master first. XOA is just a very smart client and needs the pool master to provide all of the pool information. Secondary machines will just redirect to the master, so if you try to connect XOA to one as a backup it won't work.
You just need to wait for the master to reboot and return to a functioning state and wait for XOA to automatically reconnect. The everything will start happening again.
If your master host is destroyed (ie. software corruption, hardware failure) then an existing host can be forced to take over the pool as master, but this is not a good thing to do unless the actual pool master is unrecoverable.
Ok, great, thank you for clearing this up!