Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
The sanlock user was missing in some upgrade circumstances, so
the "sanlock lockspace add" command could fail when creating new NFS storage pools on the hypervisor. Now, the sanlock user is checked on upgrade, and is created if it does not exist. The lockspace errors no longer occur.
Description of problem:
Getting Sanlock exception while creating NFS storage pool on RHEV-H node.
Happens with certain storage domains. Seems like a problem with sanlock and Root squash permission on storage domain.
Thread-1039::ERROR::2013-02-18 12:44:15,759::task::833::TaskManager.Task::(_setError) Task=`6c012945-be3f-4d12-834d-769e2d3185c3`::Unexpected error
Traceback (most recent call last):
File "/usr/share/vdsm/storage/task.py", line 840, in _run
File "/usr/share/vdsm/logUtils.py", line 38, in wrapper
File "/usr/share/vdsm/storage/hsm.py", line 893, in createStoragePool
File "/usr/share/vdsm/storage/sp.py", line 568, in create
File "/usr/share/vdsm/storage/sp.py", line 510, in _acquireTemporaryClusterLock
File "/usr/share/vdsm/storage/sd.py", line 436, in acquireHostId
File "/usr/share/vdsm/storage/clusterlock.py", line 187, in acquireHostId
AcquireHostIdFailure: Cannot acquire host id: ('c6c5d903-e05f-4b1d-89c5-2fdfd0b1b255', SanlockException(19, 'Sanlock lockspace add failure', 'No such device'))
Version-Release number of selected component (if applicable):
How reproducible:
Reproduces 100% with certain storage domain.
Steps to Reproduce:
1.Create Storage Pool on master domain.
2.
3.
Actual results:
Pool creation failed.
Expected results:
Pool creation succeed.
[root@purple-vds1 vdsm]# rpm -q sanlock
sanlock-2.6-2.el6.x86_64
[root@purple-vds1 vdsm]# rpm -q vdsm
vdsm-4.10.2-1.4.el6.x86_64
[root@purple-vds1 vdsm]# rpm -q libvirt
libvirt-0.10.2-18.el6.x86_64
vdsm log attached
This is marked regression. Can you tell me when it worked? there is no logic in rhev-h or ovirt-node for using sanlock at all. That logic is all held in vdsm.
(In reply to comment #8)
> This is marked regression. Can you tell me when it worked? there is no
> logic in rhev-h or ovirt-node for using sanlock at all. That logic is all
> held in vdsm.
it worked with RHEV-H on 6.3 version.
from what I understand, sanlock user in rhev-h runs in root context instead of sanlock context, problem start with shares that configured with root_squash configuration, which prevent sanlock from acquiring the lockspace on the lease.
also, sanlock user is missing from /etc/passwd.
please make proper changes in the rhev-h rpm.
Description of problem: Getting Sanlock exception while creating NFS storage pool on RHEV-H node. Happens with certain storage domains. Seems like a problem with sanlock and Root squash permission on storage domain. Thread-1039::ERROR::2013-02-18 12:44:15,759::task::833::TaskManager.Task::(_setError) Task=`6c012945-be3f-4d12-834d-769e2d3185c3`::Unexpected error Traceback (most recent call last): File "/usr/share/vdsm/storage/task.py", line 840, in _run File "/usr/share/vdsm/logUtils.py", line 38, in wrapper File "/usr/share/vdsm/storage/hsm.py", line 893, in createStoragePool File "/usr/share/vdsm/storage/sp.py", line 568, in create File "/usr/share/vdsm/storage/sp.py", line 510, in _acquireTemporaryClusterLock File "/usr/share/vdsm/storage/sd.py", line 436, in acquireHostId File "/usr/share/vdsm/storage/clusterlock.py", line 187, in acquireHostId AcquireHostIdFailure: Cannot acquire host id: ('c6c5d903-e05f-4b1d-89c5-2fdfd0b1b255', SanlockException(19, 'Sanlock lockspace add failure', 'No such device')) Version-Release number of selected component (if applicable): How reproducible: Reproduces 100% with certain storage domain. Steps to Reproduce: 1.Create Storage Pool on master domain. 2. 3. Actual results: Pool creation failed. Expected results: Pool creation succeed. [root@purple-vds1 vdsm]# rpm -q sanlock sanlock-2.6-2.el6.x86_64 [root@purple-vds1 vdsm]# rpm -q vdsm vdsm-4.10.2-1.4.el6.x86_64 [root@purple-vds1 vdsm]# rpm -q libvirt libvirt-0.10.2-18.el6.x86_64 vdsm log attached