Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 903276

Summary: engine: cannot remove a posix domain which is nfs over gluster because connectStorageServer is missing vers=3
Product: Red Hat Enterprise Virtualization Manager Reporter: Dafna Ron <dron>
Component: ovirt-engineAssignee: Liron Aravot <laravot>
Status: CLOSED CURRENTRELEASE QA Contact: Dafna Ron <dron>
Severity: high Docs Contact:
Priority: high    
Version: 3.1.2CC: abaron, acathrow, amureini, dyasny, fsimonce, hateya, iheim, lpeer, Rhev-m-bugs, sgrinber, yeylon, ykaul
Target Milestone: ---   
Target Release: 3.2.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: storage
Fixed In Version: SF9 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
logs none

Description Dafna Ron 2013-01-23 16:00:23 UTC
Created attachment 686060 [details]
logs

Description of problem:

I added a posix domain with nfs over gluster. 
when I tried to remove it I failed because connectStorageServer in vdsm appears without vers=3. 
the odd thing is that the engine log shows the ConnectStorageServer command with vers=3 but the command which is actually run in vdsm is missing vers=3. 
we are not sure if this is engine or vdsm issue but speaking to Alon we decided to open the bug on engine and see if its just logged with vers=3 but not actually sent that way.

Version-Release number of selected component (if applicable):

vdsm-4.9.6-45.1.el6_3.x86_64
si26

How reproducible:

100%

Steps to Reproduce:
1. create a posix domain with nfs over gluster
2. try to remove the domain 
3. 
4.  
  
Actual results:

we fail to remove the domain since connectStorageServer is run without vers=3

Expected results:

we should succeed to remove the domain

Additional info:

engine: 

2013-01-23 17:25:57,663 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (http-/0.0.0.0:8443-11) [38af6fc5] START, ConnectStorageServerVDSCommand(HostName = cougar01, HostId = 4b5e0708-63c8-11e2-ad49-001a4a16971d, storagePoolId = 00000000-0000-0000-0000-000000000000, storageType = POSIXFS, connectionList = [{ id: 738cfab0-a42d-4563-8a27-9d6990ec1868, connection: filer01.qa.lab.tlv.redhat.com:/Daffi, iqn: null, vfsType: nfs, mountOptions: vers=3, nfsVersion: null, nfsRetrans: null, nfsTimeo: null };]), log id: 25038d64


vdsm: 

hread-96398::INFO::2013-01-23 15:49:25,404::logUtils::37::dispatcher::(wrapper) Run and protect: connectStorageServer(domType=6, spUUID='00000000-0000-0000-0000-000000000000', conList=[{'port': '', 'connection': 'filer01.qa.lab.tlv.red
hat.com:/Daffi', 'iqn': '', 'portal': '', 'user': '', 'vfs_type': 'nfs', 'password': '******', 'id': '738cfab0-a42d-4563-8a27-9d6990ec1868'}], options=None)

Comment 1 Liron Aravot 2013-01-27 13:14:45 UTC
this patch introduced it - we don't send those parameters for version lower than 3.1:
http://gerrit.ovirt.org/#/c/3802/5

i guess that it's because of lack of support in vdsm side on that version - fede, can you elaborate?

Comment 2 Federico Simoncelli 2013-01-28 12:33:24 UTC
(In reply to comment #1)
> this patch introduced it - we don't send those parameters for version lower
> than 3.1:
> http://gerrit.ovirt.org/#/c/3802/5
> 
> i guess that it's because of lack of support in vdsm side on that version -
> fede, can you elaborate?

Not sending them for version < 3.1 is fine but I don't think it's relevant here.

I think Dafna was able to create the domain (pool 3.1?) using those options but then when the domain was removed the same options weren't used/sent.

Comment 3 Dafna Ron 2013-03-13 09:33:14 UTC
verified on sf10
I was able to add and remove the domain

Comment 4 Itamar Heim 2013-06-11 08:24:03 UTC
3.2 has been released

Comment 5 Itamar Heim 2013-06-11 08:25:39 UTC
3.2 has been released