Hide Forgot
Description of problem: Adding 1 host to a 4.0 gluster datacenters fails with: host is named minidell.home and has id mini. VDSM mini command failed: 'module' object has no attribute 'GlusterHost' Gluster command [<UNKNOWN>] failed on server mini. jsonrpc.Executor/6::DEBUG::2016-05-11 14:35:03,269::__init__::511::jsonrpc.JsonRpcServer::(_serveRequest) Calling 'Host.getHardwareInfo' in bridge with {} jsonrpc.Executor/6::DEBUG::2016-05-11 14:35:03,270::__init__::539::jsonrpc.JsonRpcServer::(_serveRequest) Return 'Host.getHardwareInfo' in bridge with {'systemProductName': 'OptiPlex 7010', 'systemUUID': '4C4C45 44-0059-4310-8035-C4C04F595831', 'systemSerialNumber': 'DYC5YX1', 'systemVersion': '01', 'systemManufacturer': 'Dell Inc.'} jsonrpc.Executor/7::DEBUG::2016-05-11 14:35:04,486::__init__::511::jsonrpc.JsonRpcServer::(_serveRequest) Calling 'GlusterHost.list' in bridge with {} jsonrpc.Executor/7::ERROR::2016-05-11 14:35:04,486::__init__::532::jsonrpc.JsonRpcServer::(_serveRequest) Internal server error Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 527, in _serveRequest res = method(**params) File "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 250, in _dynamicMethod api = self._get_api_instance(className, argobj) File "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 171, in _get_api_instance apiObj = getattr(API, className) AttributeError: 'module' object has no attribute 'GlusterHost'
oVirt 4.0 beta has been released, moving to RC milestone.
Ramesh, can you check if all patches that fix this are in 4.0 branch?
These bugs where already fixed in upstream vdsm-4.18.1. Hence moving the bug to ON_QA.
Doc text not required as this bug was never reported from a GAed version.
fyi i have had SHE with glusterfs hosted storage and glusterfs data domain working fine on 4.x ovirt-engine-4.0.3-0.0.master.20160720203246.git9c88731.el7.centos.noarch
(In reply to Jiri Belka from comment #6) > fyi i have had SHE with glusterfs hosted storage and glusterfs data domain > working fine on 4.x > > ovirt-engine-4.0.3-0.0.master.20160720203246.git9c88731.el7.centos.noarch ah, my env was SHE migration from 3.6, thus the dc/cl compat was still 3.6.
(In reply to Jiri Belka from comment #7) > (In reply to Jiri Belka from comment #6) > > fyi i have had SHE with glusterfs hosted storage and glusterfs data domain > > working fine on 4.x > > > > ovirt-engine-4.0.3-0.0.master.20160720203246.git9c88731.el7.centos.noarch > > ah, my env was SHE migration from 3.6, thus the dc/cl compat was still 3.6. Moreover, this issue was about managing gluster volumes/hosts in Ovirt. Glusterfs storage domain use case was not affected.
Added the RHGS Node with upstream vdsm-gluster-4.17.33-1.el7rhgs.noarch. Able to successfully add the gluster node to 4.0 DC