[ovirt-users] Re: Setting Up oVirt + NFS Storage Issues

[Arden Shackelford]

Just for reference in case anyone else comes across this, I opted to take the 
path of using GlusterFS in place of the NFS storage server that I've got to 
avoid having to make changes to the NFS server.

The glusterfs was setup on the same node, which is actually my preferred way to 
go for this.

Anyway, with the switch to gluster I'm up and running! Very excited to start 
playing with oVirt!

Thanks for the responses here to help me get a better understanding of how this 
stuff works!
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZQGJ6S4CEYT3L7QTSOQQHNMTDHAHWAQM/

[ovirt-users] Re: Setting Up oVirt + NFS Storage Issues

[Arden Shackelford]

Dang! Missed the part of ZFS not being supported :(

Yeah, NFS server is running Ubuntu, so not there by default. I'll see what I 
can do :)
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/IZTU744GVKY5OJT4QOULLZVKGYADXDOO/

[ovirt-users] Re: Setting Up oVirt + NFS Storage Issues

[Arden Shackelford]

Hey Amit,

Thanks for the response. Here's what I've got:

>Are your NFS exports permissions set correctly (probably yes if you can see
something created on your share)?

Here's the perms on the folder (/mnt/ovirt on NFS server):

File: ovirt
Size: 2   Blocks: 1  IO Block: 512directory
Device: 33h/51d Inode: 34  Links: 2
Access: (0755/drwxr-xr-x)  Uid: (   36/vdsm)   Gid: (   36/kvmovirt)
Access: 2020-08-04 17:54:06.971018988 +
Modify: 2020-08-04 17:54:09.410982092 +
Change: 2020-08-04 17:54:09.410982092 +
Birth: -

>Can you list your share contents with ls -lhZ?

Root of share:

drwxrwxr-x 4 vdsm kvmovirt ? 4 Aug  4 18:52 c6244268-aaeb-4b67-b12b-8a0e81d7c205

Inside of that:

drwxrwxr-x 2 vdsm kvmovirt ? 8 Aug  4 18:52 dom_md
drwxrwxr-x 2 vdsm kvmovirt ? 2 Aug  4 18:52 images

> Can you share the full error trace from vdsm.log?

Here's what I see:

2020-08-04 13:52:58,695-0500 INFO  (jsonrpc/1) [storage.xlease] Formatting 
index for lockspace 'c6244268-aaeb-4b67-b12b-8a0e81d7c205' (version=1) 
(xlease:701)
2020-08-04 13:52:58,767-0500 INFO  (jsonrpc/1) [storage.StorageDomain] Creating 
domain images directory 
'/rhev/data-center/mnt/storage01:_mnt_ovirt/c6244268-aaeb-4b67-b12b-8a0e81d7c205/images'
 (nfsSD:110)
2020-08-04 13:52:58,817-0500 INFO  (jsonrpc/1) [storage.StorageDomain] Removing 
remnants of deleted images [] (fileSD:735)
2020-08-04 13:52:58,819-0500 ERROR (jsonrpc/1) [storage.initSANLock] Cannot 
initialize SANLock for domain c6244268-aaeb-4b67-b12b-8a0e81d7c205 
(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: (19, 'Sanlock lockspace write failure', 'No such 
device')
2020-08-04 13:52:58,819-0500 INFO  (jsonrpc/1) [vdsm.api] FINISH 
createStorageDomain error=Could not initialize cluster lock: () 
from=:::192.168.222.200,37322, flow_id=228288c7, 
task_id=6bb381fd-9620-46bd-8c9a-0c6206e2cea4 (api:52)
2020-08-04 13:52:58,819-0500 ERROR (jsonrpc/1) [storage.TaskManager.Task] 
(Task='6bb381fd-9620-46bd-8c9a-0c6206e2cea4') Unexpected error (task:880)
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: (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.6/site-packages/vdsm/storage/task.py", line 887, in _run
return fn(*args, **kargs)
File "", 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 2644, 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 999, in 
initSPMlease
return self._manifest.initDomainLock()
File "/usr/lib/python3.6/site-packages/vdsm/storage/sd.py", line 627, 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: 
()
2020-08-04 13:52:58,819-0500 INFO  (jsonrpc/1) [storage.TaskManager.Task] 
(Task='6bb381fd-9620-46bd-8c9a-0c6206e2cea4') aborting: Task is aborted: 
'value=Could not initialize cluster lock: () abortedcode=701' (task:1190)
2020-08-04 13:52:58,819-0500 ERROR (jsonrpc/1) [storage.Dispatcher] FINISH 
createStorageDomain error=Could not initialize cluster lock: () (dispatcher:83)
2020-08-04 13:52:58,819-0500 INFO  (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC call 
StorageDomain.create failed (error 701) in 0.79 seconds (__init__:312)
2020-08-04 13:52:58,918-0500 INFO  (jsonrpc/7) [vdsm.api] START 
disconnectStorageServer(domType=1, 
spUUID='----', conList=[{'password': 
'', 'protocol_version': 'auto', 'port': '', 'iqn': '', 'connection': 
'storage01:/mnt/ovirt', 'ipv6_enabled':'false', 'id': 
'49d6da66-aecb-442e-9852-4c91f6440182', 'user': '', 'tpgt': '1'}], 
options=None) from=:::192.168.222.200,37322, 
flow_id=55c0cda3-5d44-4cd8-8020-47893c09ad5f, 
task_id=c2ecd861-39d7-4dc0-aca2-938794adefcb (api:48)
2020-08-04 13:52:58,918-0500 INFO  (jsonrpc/7) [storage.Mount] unmounting 
/rhev/data-center/mnt/storage01:_mnt_ovirt (mount:215)
2020-08-04 13:52:58,961-0500 INFO  (jsonrpc/7) [storage.StorageDomainCache] 
Refreshing storage domain cache (resize=False) (sdc:80)

[ovirt-users] Setting Up oVirt + NFS Storage Issues

[Arden Shackelford]

Hello!

Been looking to get setup with oVirt for a few weeks and had a chance the past 
week or so to attempt getting it all setup. Ended up doing a bit of 
troubleshooting but finally got to the point where the Cockpit setup prompts 
for me setting up the storage piece, for which I've opted for NFS (path of 
least resistance for now). However, I constantly run into this issue (pulled 
from the administration portal events page):

VDSM asgard.shackfam.net command CreateStorageDomainVDS failed: Could not 
initialize cluster lock: ()

This specifically shows up in the following task for the Ansible piece:

 [ovirt.hosted_engine_setup : Add NFS storage domain]

When I browse the NFS share, I do see a file structure being created, which 
kind of confuses me based on the error provide in the Administration portal.

Any suggestions on what would be best steps forward at this point?

For reference, here's my setup:

1x oVirt Node
1x NFS server (storage01: NFS shares mainly managed by ZFS)
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BNVXUH5B26FBFCGYLG62JUSB5SOU2MN7/