Unable to enable High Availability - INTERNAL_ERROR(Not_found)

jmannik

@andriy.sultanov @psafont
https://drive.google.com/file/d/1aJyCYSAuRIBb0X-23gJ6ORtrHSciYH8a/view?usp=sharing
Here is the log file

psafont

@jmannik said in Unable to enable High Availability - INTERNAL_ERROR(Not_found):

@andriy.sultanov @psafont
https://drive.google.com/file/d/1aJyCYSAuRIBb0X-23gJ6ORtrHSciYH8a/view?usp=sharing
Here is the log file

It's not crystal clear the condition that causes the exception, but I can see some unprotected exception being raised in that path host.ha_join_liveset when trying to recover the host uuid and it's not found. I'll investigate

psafont

@jmannik I have a test build that you can test, it will hopefully provide better error messages by raising an internal error with a reason.

The code is based on the newest builds, so I recommend updating to the latest version of XCP beforehand:

yum update
reboot

Once that is done, the test packages can be installed by creating the file /etc/yum.repos.d/xcp-test.repo:

[xcp-ng-psafont1]
name=xcp-ng-psafont1
baseurl=https://koji.xcp-ng.org/repos/user/8/8.3/psafont1/x86_64/
enabled=0
gpgcheck=1
repo_gpgcheck=1
metadata_expire=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-xcpng

then updating the host using the test developer repo

yum update --enablerepo=xcp-ng-psafont1

and finally restarting all the daemons

xe-toolstack-restart

Note: the repository will only be available for a limited amount of time, after which I will repurpose it and delete the instructions so it's not used anymore by accident.

tjkreidl

Note also that if HA is turned on or off, the host must be restarted for that change to take effect, if I recall correctly.

jmannik

@tjkreidl This hasn't been my experience so far, enabling HA has just enabled HA, no reboot needed.

@psafont I am patching all my hosts now, will do the above test packages on Sunday Night (it is Friday afternoon at the time of this post)

nikade

@jmannik said in Unable to enable High Availability - INTERNAL_ERROR(Not_found):

@tjkreidl This hasn't been my experience so far, enabling HA has just enabled HA, no reboot needed.

@psafont I am patching all my hosts now, will do the above test packages on Sunday Night (it is Friday afternoon at the time of this post)

Correct, no reboot needed to enable/disable HA.

tjkreidl

@nikade Interesting, as that at some point used to be the case, at least with XenServer!
I stand corrected and learned something new.

jmannik

@psafont
That is done now, tried to enable HA again and it was unsuccessful, what would you like me to do now?

olivierlambert

You should check the /var/log/xensource.log, it should provide a more explicit error message

tjkreidl

@olivierlambert Good idea. Also, they should make sure all hosts are at the same update/patch levels, the network is set up properly among the three or more hosts, there is a compatible HA shared storage properly set up, etc.
You folks have a good guide at: https://docs.xcp-ng.org/management/ha/