Thanks,
I can mount it manually, but when trying to read the file, I'm getting the error: /usr/lib/python3.6/site-packages/vdsm/storage/clusterlock.py: No such file or directory
The directory's user & group are on my user (I'm unable to change ownership for some reason), but I have set earlier the directory's (which I tried to add as a storage domain) permissions to 777

On Thu, Jan 2, 2020 at 5:24 PM Nir Soffer <nsoffer@redhat.com> wrote:
On Thu, Jan 2, 2020 at 4:44 PM Dana Elfassy <delfassy@redhat.com> wrote:
>
> Hi,
> When trying to add a storage domain to a 4.4 host I'm getting this error message:
> Error while executing action New NFS Storage Domain: Unexpected exception
>
> The errors from vdsm.log:
> 2020-01-02 09:38:33,578-0500 ERROR (jsonrpc/0) [storage.initSANLock] Cannot initialize SANLock for domain 6ca1e203-5595-47e5-94b8-82a7e69d99a9 (clusterlock:259)
> Traceback (most recent call last):
>   File "/usr/lib/python3.6/site-packages/vdsm/storage/clusterlock.py", line 250, in initSANLock
>     lockspace_name, idsPath, align=alignment, sector=block_size)
> sanlock.SanlockException: (-202, 'Sanlock lockspace write failure', 'IO timeout')

This means sanlock operation failed with a timeout - the storage was too slow
or there some issue on the storage side.

Can you mount this manually and access file as user vdsm?

> 2020-01-02 09:38:33,579-0500 INFO  (jsonrpc/0) [vdsm.api] FINISH createStorageDomain error=Could not initialize cluster lock: () from=::ffff:192.168.100.1,36452, flow_id=17dc614
> e, task_id=05c2107a-4d59-48d0-a2f7-0938f051c9ab (api:52)
> 2020-01-02 09:38:33,582-0500 ERROR (jsonrpc/0) [storage.TaskManager.Task] (Task='05c2107a-4d59-48d0-a2f7-0938f051c9ab') Unexpected error (task:874)
> Traceback (most recent call last):
>   File "/usr/lib/python3.6/site-packages/vdsm/storage/clusterlock.py", line 250, in initSANLock
>     lockspace_name, idsPath, align=alignment, sector=block_size)
> sanlock.SanlockException: (-202, 'Sanlock lockspace write failure', 'IO timeout')

Looks like same error raised again, a common issue in legacy code.

> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>   File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 881, in _run
>     return fn(*args, **kargs)
>   File "<decorator-gen-121>", line 2, in createStorageDomain
>   File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 50, in method
>     ret = func(*args, **kwargs)
>   File "/usr/lib/python3.6/site-packages/vdsm/storage/hsm.py", line 2622, in createStorageDomain
>     max_hosts=max_hosts)
>   File "/usr/lib/python3.6/site-packages/vdsm/storage/nfsSD.py", line 120, in create
>     fsd.initSPMlease()
>   File "/usr/lib/python3.6/site-packages/vdsm/storage/sd.py", line 974, in initSPMlease
>     return self._manifest.initDomainLock()
>   File "/usr/lib/python3.6/site-packages/vdsm/storage/sd.py", line 620, in initDomainLock
>     self._domainLock.initLock(self.getDomainLease())
>   File "/usr/lib/python3.6/site-packages/vdsm/storage/clusterlock.py", line 308, in initLock
>     block_size=self._block_size)
>   File "/usr/lib/python3.6/site-packages/vdsm/storage/clusterlock.py", line 260, in initSANLock
>     raise se.ClusterLockInitError()
> vdsm.storage.exception.ClusterLockInitError: Could not initialize cluster lock: ()

There is no information about this error, looks like the public
useless error we raise for the
underlying error seen before.