-
Notifications
You must be signed in to change notification settings - Fork 285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xapi not coming back on new master after pool.designate_new_master
, old master loses TLS verification
#6056
Comments
Checked on a brand new 8.2.1 pool, similar but not identical behavior: from the master I can launch a quick sequence of
And running a new sequence from the same machine (now a slave) to switch it back to master, I get the same result:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In this XCP-ng forum subthread, a user reports a pool breakage, which I was able to replicate as follows (not 100% repro, I got it on 2nd attempt after joining a 3rd host):
xe pool-designate-new-master
against the samehost-uuid
several times rapidly enough to run afterDESIGNATE_NEW_MASTER_IN_PROGRESS
stops to be returned but apparently before xapi realizes that host is already the masterThe
Lost connection to the server.
is likely key, as I saw it first when I got the issue.Forum post has user's full logs, the following are selected from my reproduction.
daemon.log
on the expected-new-master shows a failure to restartxapi
successfully, looping a few times on:with xensource.log showing:
Meanwhile, the old-master while restarting
xapi
reveals a strange situation, where it has lost its tls-enablement status:Digging the log reveals that this first occurred last friday, when I was (without success) trying to reproduce the issue with only 2 hosts in the pool.
The text was updated successfully, but these errors were encountered: