Bug 1428851
| Summary: | RDMA Glusterfs does not recognized as mounted | ||
|---|---|---|---|
| Product: | [oVirt] vdsm | Reporter: | Arman <arm2arm> |
| Component: | Gluster | Assignee: | Denis Chaplygin <dchaplyg> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | SATHEESARAN <sasundar> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.19.4 | CC: | bugs, nsoffer, rkavunga, sabose, tnisan |
| Target Milestone: | ovirt-4.2.0 | Flags: | rule-engine:
ovirt-4.2+
rule-engine: planning_ack+ rule-engine: devel_ack+ sasundar: testing_ack+ |
| Target Release: | 4.20.9 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: Gluster mount name changes during mount
Consequence: As VDSM compares actual mount name and recorded mount name using strict string comparison, RDMA volumes was considered to be unmounted.
Fix: Strip RDMA suffix from gluster rdma volume name
Result: RDMA volume can be verified by VDSM and now is reported as mounted.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-05-10 06:30:57 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Gluster | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
This looks like a gluster bug, not vdsm bug. Sahina, can you get someone from gluster to explain why the mount fs_spec is modified? this would break any client trying to check if a mount exists. Rafi, can you please respond? gluster maintain separate volfile for rdma and tcp. But it doesn't had enough argument to specify the transport during the rpc request. Hence this was an hack introduced. I agree that we should fix this issue. I will take that up and see how we can fix this issue. We may need to wait for another major release to get the fix if it involves any change in rpc req. Tested with RHV 4.2.3 with IB client and IB servers. 1. Created gluster volume with transport=rdma 2. Created a storage domain with additional mount options mentioned as transport=rdma 3. The storage domain comes up operational This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |
3 identical nodes with zfs+glusterfs as ovirt hosts. If I change the mount option of the storage to: backup-volfile-servers=10.10.10.44:10.10.10.42:10.10.10.41,transport=rdma the storage doesnot come up. apparently the storage is mounted correctly: root@clei21 ~]# df| grep glu 10.10.10.41:/GluReplica.rdma 3770658816 407789568 3362869248 11% /rhev/data-center/mnt/glusterSD/10.10.10.41:_GluReplica It looks that vdsm checks are not able to detect if storage mounted or not The log error stating: 2017-03-03 13:43:14,733 ERROR (jsonrpc/5) [storage.HSM] Could not connect to storageServer (hsm:2391) Traceback (most recent call last): File "/usr/share/vdsm/storage/hsm.py", line 2388, in connectStorageServer conObj.connect() File "/usr/share/vdsm/storage/storageServer.py", line 167, in connect self.getMountObj().getRecord().fs_file) File "/usr/lib/python2.7/site-packages/vdsm/storage/mount.py", line 237, in getRecord (self.fs_spec, self.fs_file)) OSError: [Errno 2] Mount of `10.10.10.41:/GluReplica` at `/rhev/data-center/mnt/glusterSD/10.10.10.41:_GluReplica` does not exist 2017-03-03 13:43:14,734 INFO (jsonrpc/5) [dispatcher] Run and protect: connectStorageServer, Return response: {'statuslist': [{'status': 100, 'id': u'4b2ea911-ef35-4de0-bd11-c4753e6048d8'}]} (logUtils:52)