Bug 1543805
| Summary: | Empty backup-volfile-servers option passed for distribute volume | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Sahina Bose <sabose> |
| Component: | BLL.Gluster | Assignee: | Sahina Bose <sabose> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | SATHEESARAN <sasundar> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.2.1.4 | CC: | bugs |
| Target Milestone: | ovirt-4.2.2 | Flags: | rule-engine:
ovirt-4.2?
sasundar: planning_ack? rule-engine: devel_ack+ sasundar: testing_ack+ |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-03-29 11:02:22 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: | |||
Tested with RHV 4.2.2-4 and able to create glusterfs storage domain with distribute gluster volume type This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |
Description of problem: An empty backup-volfile-servers option is passed while creating a gluster storage domain using the "Managed Gluster Volumes" option . This is when a single brick gluster volume is chosen. Version-Release number of selected component (if applicable): 4.2 Additional info: 2018-02-09 16:17:11,452+0530 INFO (jsonrpc/7) [vdsm.api] START connectStorageServer(domType=7, spUUID=u'00000000-0000-0000-0000-000000000000', conList=[{u'mnt_options': u'backup-volfile-servers=', u'id': u'0000 0000-0000-0000-0000-000000000000', u'connection': u'dhcp43-86.lab.eng.blr.redhat.com:/data', u'iqn': u'', u'user': u'', u'tpgt': u'1', u'vfs_type': u'glusterfs', u'password': '********', u'port': u''}], options= None) from=::ffff:10.70.40.199,36994, flow_id=45af8852-8f5b-4301-bb1f-c3e8b0131715, task_id=7c17c548-6b86-4c6c-8920-404ac2e1f7c5 (api:46) 2018-02-09 16:17:11,623+0530 ERROR (jsonrpc/7) [storage.HSM] Could not connect to storageServer (hsm:2407) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2404, in connectStorageServer conObj.connect() File "/usr/lib/python2.7/site-packages/vdsm/storage/storageServer.py", line 179, in connect six.reraise(t, v, tb) File "/usr/lib/python2.7/site-packages/vdsm/storage/storageServer.py", line 171, in connect self._mount.mount(self.options, self._vfsType, cgroup=self.CGROUP) File "/usr/lib/python2.7/site-packages/vdsm/storage/mount.py", line 207, in mount cgroup=cgroup) File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 55, in __call__ return callMethod() File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 53, in <lambda> **kwargs) File "<string>", line 2, in mount File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod raise convert_to_error(kind, result) MountError: (1, ';Running scope as unit run-7812.scope.\nInvalid option backup-volfile-servers\n')