@olivierlambert Yes, we saw this before, we are investigating.

@wilsonqanda qcow2 packages are in a separate repository. You should have setup the repo, a grep -r "qcow2" /etc/yum.repos.d/ should tell you if it was setup on your host.

@wilsonqanda, can you share the /var/log/SMlog? Do you installed qcow2 release and use some qcow2 VDIs?

@acp Here is the procedure to re-insert your host in the SR.

Make sure you have the required packages by running these commands on it:

yum install -y xcp-ng-release-linstor
yum install -y xcp-ng-linstor

It should be the case because the node was running the services before, but better to check.

And then restart the toolstack to detect the LINSTOR driver:

xe-toolstack-restart

Ensure you have the same configuration on each PBD of your XOSTOR SR using this command.

xe pbd-list sr-uuid=<UUID>

All device-config must be the same.

Then, use this command with the correct <GROUP_NAME> and <HOST_UUID> to add the node to the SR:

xe host-call-plugin host-uuid=<HOST_UUID> plugin=linstor-manager fn=addHost args:groupName=<GROUP_NAME>

For a short description, this command (re)create a PBD, open DRBD/LINSTOR ports, start specific services and add the node in the LINSTOR database.

A storage layer is not directly added to this node. You can verify the storage state like this:

linstor sp list

You shouldn't see the storage pool of your node yet.

Run the correct command where the controller is running to add the volume group in the LINSTOR database:

# For thin:
linstor storage-pool create lvmthin <NODE_NAME> <SP_NAME> <VG_NAME>

# For thick:
linstor storage-pool create lvm <NODE_NAME> <SP_NAME> <VG_NAME>

A new linstor sp list should show you the node now.