Unable to add host to pool (db mismatch)
-
We've been building on a running pool and want to add our last host to it. Host had a fresh install, renamed interfaces, but adding it provides:
POOL_JOINING_HOST_MUST_HAVE_SAME_DB_SCHEMA(5.602, 5.603)
We've opened a ticket and was advised to do the following:
https://help.vates.tech/kb/en-us/14/103Completed this step and the new host now has identical packages to the rest of the pool. Tried to add again, same error:
POOL_JOINING_HOST_MUST_HAVE_SAME_DB_SCHEMA(5.602, 5.603)Also rebooted the new host (incase this was the issue) but same result.
How do we update the db schema?
-
DB schema is updated automatically when you make your updates. So there's an update mismatch between your hosts.
-
The purpose of the exercise is to get the new host updated with identical packages/updates to match the pool master
Am I correct in saying that when "Install all patches" is selected on the new host, it will resolve the db_schema mismatch and still be able to successfully join the pool?
Unless the new host has more updates afterwards than the pool master and won't be able to join the pool?
-
@olivierlambert - what can we provide to assist log wise? I can confirm the only 2 packages that are different from the yum changes are iftop and the intel fibre card. The rest are identical.
Is there another command we can run to retrigger the database migration on the new host?
-
Have you rebooted after installing patches? Or at least restarted the toolstack?
-
@olivierlambert yes we have. What's funny is that we were able to add the other member to the pool a couple of months ago (this is the final one we need to add before we can actually schedule downtime to do proper pool maintenance). Our current pool only has 2 hosts in it, so we cannot really do master / pool restarts as the risk of reboot scenario with a single host will more than likely overload the single host.
We have installed exactly the same patches of the pool. The new host has also been rebooted. Is there a manual mechanism to upgrade the schema on the new host? As the new host is currently empty, we're happy to perform whatever is needed to get it to join the pool.
-
Again, there's absolutely no reason to upgrade a schema manually, if you have installed the package, a simple toolstack restart would have done it automatically on XAPI start. That's why it doesn't make sense to me.
-
Ping @andriy.sultanov
-
Could you please provide the output of (for the master and the candidate host):
xe host-list params=software-versionIt does seem odd....
