Host dbsync failed and XAPI restart everytime after patches installation

dtresp

After patches installation, we can't enable host cause XAPI restart everytime and the dbsync failed.

The host has XAPI interfaces but not PIF interfaces.

This host can't mount lvmoiscsi storage but can mount other storages.
If we try to mount the ISCSI storage we have the following error :

"code": "SR_BACKEND_FAILURE_97",
  "params": [
    "",
    "Unable to retrieve the host configuration ISCSI IQN parameter",
...

But from the master host, we can see the iscsi_iqn parameter with the command xe host-param-list uuid=HOST_UUID

It's the first time we have a problem after patches installation.

I think if we solve the ISCSI problem it will work, but I don't know how to troubleshoot this one.

Could you help us please ?

olivierlambert

Hi,

First off, if it's production (which I assume is the case here), I would strongly suggest to get support for your hosts. It's a lot better to get a decent support with a guarantee of response time. We have new offers "all inclusive" with both XCP-ng+XO. Feel free to contact us on https://vates.tech/contact/ for more info (especially if you are already an XO customer, that might be interesting to you). Hopefully, you'll see the value of getting support, which is not just when you have a problem but also helping you all along, answering your questions/architecture/design whatever related to the whole stack. Getting a subscription is also being sure it won't disappear due to a lack of money, especially for a tool that is running your critical IT services.
I suspect you maybe have a slave more up to date than the master.

dtresp

Hi,

Thanks, I will suggest to get support for our hosts.
Exactly. So, you recommand to install patches on master host before slave hosts ?
What happen if the master host is more up to date than the slaves ?

olivierlambert

Really, you should because it would have prevent you this situation in the first place, but also some other future questions or problem you might have
That's one of the few capital rules in XCP-ng world. Your master must ALWAYS be more recent than the slaves (or at the same level obviously), otherwise slaves won't be able to connect. I think you really need some assistance on best practices and such, please contact us so we can assist more generally. If this basic requirement is not understand, you might have other/deeper issues.