12:42 a.m.
Okay, I don't see the person's reply to this thread (maybe it was a direct reply
to me?), but now I can authenticate. Except... now it's complaining it can't get
sanlock...
2023-11-17 17:34:43,315-0600 INFO (jsonrpc/4) [storage.sanlock] Initializing sanlock for
domain a476e565-d06a-473f-bd35-d052cbca7653
path=/rhev/data-center/mnt/192.168.1.11:_mnt_POOL0/a476e565-d06a-473f-bd35-d052cbca7653/dom_md/ids
alignment=1048576 block_size=512 io_timeout=10 (clusterlock:325)
2023-11-17 17:34:43,317-0600 ERROR (jsonrpc/4) [storage.sanlock] Cannot initialize lock
for domain a476e565-d06a-473f-bd35-d052cbca7653 (clusterlock:347)
Traceback (most recent call last):
File "/usr/lib/python3.9/site-packages/vdsm/storage/clusterlock.py", line 333,
in initLock
sanlock.write_lockspace(
sanlock.SanlockException: (19, 'Sanlock lockspace write failure', 'No such
device')
2023-11-17 17:34:43,317-0600 INFO (jsonrpc/4) [vdsm.api] FINISH createStorageDomain
error=Could not initialize cluster lock: () from=::ffff:192.168.1.16,50468,
flow_id=228696e3, task_id=f106211c-2e11-48de-8abc-42925ba70a0c (api:35)
2023-11-17 17:34:43,318-0600 ERROR (jsonrpc/4) [storage.taskmanager.task]
(Task='f106211c-2e11-48de-8abc-42925ba70a0c') Unexpected error (task:860)
Traceback (most recent call last):
File "/usr/lib/python3.9/site-packages/vdsm/storage/clusterlock.py", line 333,
in initLock
sanlock.write_lockspace(
sanlock.SanlockException: (19, 'Sanlock lockspace write failure', 'No such
device')
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.9/site-packages/vdsm/storage/task.py", line 867, in
_run
return fn(*args, **kargs)
File "<decorator-gen-123>", line 2, in createStorageDomain
File "/usr/lib/python3.9/site-packages/vdsm/common/api.py", line 33, in
method
ret = func(*args, **kwargs)
File "/usr/lib/python3.9/site-packages/vdsm/storage/hsm.py", line 2315, in
createStorageDomain
newSD = create(
File "/usr/lib/python3.9/site-packages/vdsm/storage/nfsSD.py", line 103, in
create
fsd.initSPMlease()
File "/usr/lib/python3.9/site-packages/vdsm/storage/sd.py", line 1215, in
initSPMlease
return self._manifest.initDomainLock()
File "/usr/lib/python3.9/site-packages/vdsm/storage/sd.py", line 628, in
initDomainLock
self._domainLock.initLock(self.getDomainLease())
File "/usr/lib/python3.9/site-packages/vdsm/storage/clusterlock.py", line 349,
in initLock
raise se.ClusterLockInitError()
vdsm.storage.exception.ClusterLockInitError: Could not initialize cluster lock: ()
2023-11-17 17:34:43,318-0600 INFO (jsonrpc/4) [storage.taskmanager.task]
(Task='f106211c-2e11-48de-8abc-42925ba70a0c') aborting: Task is aborted:
'value=Could not initialize cluster lock: () abortedcode=701' (task:1165)
2023-11-17 17:34:43,318-0600 ERROR (jsonrpc/4) [storage.dispatcher] FINISH
createStorageDomain error=Could not initialize cluster lock: () (dispatcher:66)
2023-11-17 17:34:43,318-0600 INFO (jsonrpc/4) [jsonrpc.JsonRpcServer] RPC call
StorageDomain.create failed (error 701) in 2.46 seconds (__init__:300)
"No such device"?
and in sanlock.log:
2023-11-17 17:20:30 150756 [1038]: open error -13 EACCES: no permission to open
/rhev/data-center/mnt/192.168.1.11:_mnt_POOL0/dcd1274e-f8df-4f61-98bd-66ad335f7c94/dom_md/ids
2023-11-17 17:20:30 150756 [1038]: check that daemon user sanlock 179 group sanlock 179
has access to disk or file.
2023-11-17 17:34:43 151609 [1038]: open error -13 EACCES: no permission to open
/rhev/data-center/mnt/192.168.1.11:_mnt_POOL0/a476e565-d06a-473f-bd35-d052cbca7653/dom_md/ids
2023-11-17 17:34:43 151609 [1038]: check that daemon user sanlock 179 group sanlock 179
has access to disk or file.
Why is so much of this needing my personal touch to setup? Shouldn't access through
36:36 be sufficient? Sorry, just not happy that something that I thought would be a
straightforward process is becoming more involved than I thought.