5:53 p.m.
This is a multi-part message in MIME format.
--------------030906080804030905060804
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hi All,
I am validating GLUSTERFS Storage domain engine patches (worked on
by Sharad, in Cc) as posted here...
http://gerrit.ovirt.org/#/q/status:open+project:ovirt-engine+branch:maste...
against VDSM Glusterfs domain support (already upstream in VDSM)
I see the below issue as part of me creatign a new Gluster Storage
DOmain in the UI
Engine logs...
2013-03-18 13:27:29,149 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand]
(http--0.0.0.0-8700-1) [4b751967] START,
ConnectStorageServerVDSCommand(HostName = vm-vdsm-de-1, HostId =
c0ff5edc-4e30-4553-9125-2d1cee9f19ec, storagePoolId =
00000000-0000-0000-0000-000000000000, storageType = GLUSTERFS,
connectionList = [{ id: null, connection: vm-vdsm-de-1:dpkvol4, iqn:
null, vfsType: glusterfs, mountOptions: null, nfsVersion: null,
nfsRetrans: null, nfsTimeo: null };]), log id: f88d42d
VDSM Logs...
Thread-77::INFO::2013-03-18
13:32:35,541::logUtils::44::dispatcher::(wrapper) Run and protect:
connectStorageServer(domType=7,
spUUID='00000000-0000-0000-0000-000000000000', conList=[{'connection':
'vm-vdsm-de-1:dpkvol4', 'iqn': '', 'portal': '',
'user': '', 'password':
'******', 'id': '00000000-0000-0000-0000-000000000000',
'port': ''}],
options=None)*--> Notice no vfs_type here !!!*
VDSM doesn't recv. the vfs_type in the conList dict !!!
I had this small chat with Saggi of VDSM, just to confirm that there
isn't a possibility that VDSM might be stripping args that are recd.
from Engine.. and it doesn't.
---------------------------------------------------------------------------------------------------------------------
<deepakcs> saggi, Hi
<saggi> deepakcs: hi
<deepakcs> saggi, Is it possible that VDSM might strip down some of the
connparams that are recd. as part of connectStorageServer ?
<deepakcs> saggi, In engine log for GLUSTERFS_DOMAIN i see vfsType being
passed, but connectStorageServer log doesn't show vfs_type in the params
dict
<deepakcs> saggi, so wodering where vfs_type is getting dropped in this
whole process
<saggi> Probably not being sent
<saggi> if it's not being logged
<deepakcs> saggi, engine log has this....
<deepakcs> 2013-03-18 13:27:29,149 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand]
(http--0.0.0.0-8700-1) [4b751967] START,
ConnectStorageServerVDSCommand(HostName = vm-vdsm-de-1, HostId =
c0ff5edc-4e30-4553-9125-2d1cee9f19ec, storagePoolId =
00000000-0000-0000-0000-000000000000, storageType = GLUSTERFS,
connectionList = [{ id: null, connection: vm-vdsm-de-1:dpkvol4, iqn:
null, vfsType: glusterfs, mountOptions: null, nfsVersion: nul
<deepakcs> l, nfsRetrans: null, nfsTimeo: null };]), log id: f88d42d
<deepakcs> saggi, on VDSM side i see this...
<deepakcs> Thread-77::INFO::2013-03-18
13:32:35,541::logUtils::44::dispatcher::(wrapper) Run and protect:
connectStorageServer(domType=7,
spUUID='00000000-0000-0000-0000-000000000000', conList=[{'connection':
'vm-vdsm-de-1:dpkvol4', 'iqn': '', 'portal': '',
'user': '', 'password':
'******', 'id': '00000000-0000-0000-0000-000000000000',
'port': ''}],
options=None) --> Notice no vfs_type here !!!
<saggi> Then you are not sending the correct connection type
<deepakcs> saggi, 'you' means the engine side of code ? engine patches
is being done by Sharad, and I amtrying to work with them on this issue
<deepakcs> saggi, domType=7 is GLUSTERFS_DOMAIN, so its correct on that
front
<saggi> If it show nfsRetrans you are using nfs which doesn't have a
vfs_type argument
<deepakcs> saggi, but engine log says storageType = GLUSTERFS
<deepakcs> saggi, maybe i can send mail to users@ovirt list to see if
anybody can provide more clues
<deepakcs> saggi, but definitely this doesn't looks like a vdsm side of
issue rite ?
<saggi> We log the params as we get them
<deepakcs> saggi, right, thats what i also see.. just wanted to confirm
once with you, before i sent mail to ovirt folks
---------------------------------------------------------------------------------------------------------------------
Can someone help provide any clues on what might be the issue here ?
Because VDSM doesn't see vfs_type, the connectStorageServer fails and
hence new SD cannot be created !
thanx,
deepak
--------------030906080804030905060804
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>Hi All,<br>
I am validating GLUSTERFS Storage domain engine
patches
(worked on by Sharad, in Cc) as posted here...<br>
<a class="moz-txt-link-freetext"
href="http://gerrit.ovirt.org/#/q/status:open+project:ovirt-engine+b...
against VDSM Glusterfs domain support (already upstream in VDSM)<br>
<br>
I see the below issue as part of me creatign a new Gluster Storage
DOmain in the UI<br>
<br>
Engine logs...<br>
<br>
2013-03-18 13:27:29,149 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand]
(http--0.0.0.0-8700-1) [4b751967] START,
ConnectStorageServerVDSCommand(HostName = vm-vdsm-de-1, HostId =
c0ff5edc-4e30-4553-9125-2d1cee9f19ec, storagePoolId =
00000000-0000-0000-0000-000000000000, storageType = GLUSTERFS,
connectionList = [{ id: null, connection: vm-vdsm-de-1:dpkvol4,
iqn: null, vfsType: glusterfs, mountOptions: null, nfsVersion:
null, nfsRetrans: null, nfsTimeo: null };]), log id: f88d42d<br>
<br>
VDSM Logs...<br>
<br>
Thread-77::<a class="moz-txt-link-freetext"
href="INFO::2013-03-18">INFO::2013-03-18</a>
13:32:35,541::logUtils::44::dispatcher::(wrapper) Run and protect:
connectStorageServer(domType=7,
spUUID='00000000-0000-0000-0000-000000000000',
conList=[{'connection': 'vm-vdsm-de-1:dpkvol4', 'iqn':
'',
'portal': '', 'user': '', 'password':
'******', 'id':
'00000000-0000-0000-0000-000000000000', 'port': ''}],
options=None)<b> --> Notice no vfs_type here !!!</b><br>
<br>
VDSM doesn't recv. the vfs_type in the conList dict !!!<br>
<br>
I had this small chat with Saggi of VDSM, just to confirm that
there isn't a possibility that VDSM might be stripping args that
are recd. from Engine.. and it doesn't.<br>
<br>
</tt><br>
<tt><tt>---------------------------------------------------------------------------------------------------------------------<br>
</tt><deepakcs> saggi, Hi<br>
<saggi> deepakcs: hi<br>
<br>
<deepakcs> saggi, Is it possible that VDSM might strip down
some of the connparams that are recd. as part of
connectStorageServer ?<br>
<deepakcs> saggi, In engine log for GLUSTERFS_DOMAIN i see
vfsType being passed, but connectStorageServer log doesn't show
vfs_type in the params dict<br>
<deepakcs> saggi, so wodering where vfs_type is getting
dropped in this whole process<br>
<saggi> Probably not being sent<br>
<saggi> if it's not being logged<br>
<deepakcs> saggi, engine log has this....<br>
<deepakcs> 2013-03-18 13:27:29,149 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand]
(http--0.0.0.0-8700-1) [4b751967] START,
ConnectStorageServerVDSCommand(HostName = vm-vdsm-de-1, HostId =
c0ff5edc-4e30-4553-9125-2d1cee9f19ec, storagePoolId =
00000000-0000-0000-0000-000000000000, storageType = GLUSTERFS,
connectionList = [{ id: null, connection: vm-vdsm-de-1:dpkvol4,
iqn: null, vfsType: glusterfs, mountOptions: null, nfsVersion: nul<br>
<deepakcs> l, nfsRetrans: null, nfsTimeo: null };]), log id:
f88d42d<br>
<deepakcs> saggi, on VDSM side i see this...<br>
<deepakcs> Thread-77::<a class="moz-txt-link-freetext"
href="INFO::2013-03-18">INFO::2013-03-18</a>
13:32:35,541::logUtils::44::dispatcher::(wrapper) Run and protect:
connectStorageServer(domType=7,
spUUID='00000000-0000-0000-0000-000000000000',
conList=[{'connection': 'vm-vdsm-de-1:dpkvol4', 'iqn':
'',
'portal': '', 'user': '', 'password':
'******', 'id':
'00000000-0000-0000-0000-000000000000', 'port': ''}],
options=None) --> Notice no vfs_type here !!!<br>
<saggi> Then you are not sending the correct connection
type<br>
<br>
<deepakcs> saggi, 'you' means the engine side of code ?
engine patches is being done by Sharad, and I amtrying to work
with them on this issue<br>
<br>
<deepakcs> saggi, domType=7 is GLUSTERFS_DOMAIN, so its
correct on that front<br>
<saggi> If it show nfsRetrans you are using nfs which
doesn't have a vfs_type argument<br>
<deepakcs> saggi, but engine log says storageType =
GLUSTERFS<br>
<deepakcs> saggi, maybe i can send mail to users@ovirt list
to see if anybody can provide more clues<br>
<deepakcs> saggi, but definitely this doesn't looks like a
vdsm side of issue rite ?<br>
<saggi> We log the params as we get them<br>
<br>
<deepakcs> saggi, right, thats what i also see.. just wanted
to confirm once with you, before i sent mail to ovirt folks<br>
<br>
---------------------------------------------------------------------------------------------------------------------<br>
<br>
<br>
Can someone help provide any clues on what might be the issue here
?<br>
Because VDSM doesn't see vfs_type, the connectStorageServer fails
and hence new SD cannot be created !<br>
<br>
thanx,<br>
deepak<br>
<br>
</tt>
</body>
</html>
--------------030906080804030905060804--