Created attachment 1432574 [details] nfsv4 Description of problem: Deploy HE failed via cockpit with NFSv4 or NFSv4.1 Version-Release number of selected component (if applicable): rhvh-4.2.3.0-0.20180504.0+1 ovirt-hosted-engine-setup-2.2.20-1.el7ev.noarch cockpit-ovirt-dashboard-0.11.24-1.el7ev.noarch ovirt-hosted-engine-ha-2.2.11-1.el7ev.noarch rhvm-appliance-4.2-20180504.0.el7.noarch How reproducible: 100% Steps to Reproduce: 1. Deploy HE via cockpit 2. Choose the NFS v4 or v4.1 version. Actual results: After step2, deploy HE failed. Expected results: Deploy HE successfully Additional info:
(In reply to Yihui Zhao from comment #0) > Created attachment 1432574 [details] > nfsv4 > > Description of problem: > Deploy HE failed via cockpit with NFSv4 or NFSv4.1 > > Version-Release number of selected component (if applicable): > rhvh-4.2.3.0-0.20180504.0+1 > ovirt-hosted-engine-setup-2.2.20-1.el7ev.noarch > cockpit-ovirt-dashboard-0.11.24-1.el7ev.noarch > ovirt-hosted-engine-ha-2.2.11-1.el7ev.noarch > rhvm-appliance-4.2-20180504.0.el7.noarch > > How reproducible: > 100% > > > Steps to Reproduce: > 1. Deploy HE via cockpit > 2. Choose the NFS v4 or v4.1 version. > > Actual results: > After step2, deploy HE failed. > > > Expected results: > Deploy HE successfully > > Additional info: In the same ENV, the nfsv3 or auto work well.
Is the NFS v4 environment using kerberos or any other additional configuration?
(In reply to Ryan Barry from comment #2) > Is the NFS v4 environment using kerberos or any other additional > configuration? No, there is no other additional configuration.
(In reply to Yihui Zhao from comment #3) > (In reply to Ryan Barry from comment #2) > > Is the NFS v4 environment using kerberos or any other additional > > configuration? > > No, there is no other additional configuration. Here is the permission of the nfs dir: drwxr-xr-x. 3 vdsm kvm 4096 May 7 14:33 nfs1
(In reply to Ryan Barry from comment #2) > Is the NFS v4 environment using kerberos or any other additional > configuration? Is the NFS v4 need the higher permission of the nfs dir(>755)?
Can you please upload also vdsm.log and engine.log ?
Created attachment 1432578 [details] engine.log
Created attachment 1432579 [details] vdsm.log
In vdsm.log we see: 2018-05-07 19:47:58,395+0800 INFO (jsonrpc/4) [vdsm.api] START connectStorageServer(domType=1, spUUID=u'00000000-0000-0000-0000-000000000000', conList=[{u'id': u'00000000-0000-0000-0000-000000000000', u'connection': u'10.66.148.11:/home/jiawu/nfs2', u'iqn': u'', u'user': u'', u'tpgt': u'1', u'protocol_version': u'4', u'password': '********', u'port': u''}], options=None) from=::ffff:192.168.124.198,34154, flow_id=4b43c2f5-b644-4794-bb99-fbd00ee5e076, task_id=5dc38d85-696f-40e7-8fc4-a2088c5ddc7e (api:46) 2018-05-07 19:47:58,398+0800 INFO (jsonrpc/4) [storage.StorageServer.MountConnection] Creating directory u'/rhev/data-center/mnt/10.66.148.11:_home_jiawu_nfs2' (storageServer:167) 2018-05-07 19:47:58,398+0800 INFO (jsonrpc/4) [storage.fileUtils] Creating directory: /rhev/data-center/mnt/10.66.148.11:_home_jiawu_nfs2 mode: None (fileUtils:197) 2018-05-07 19:47:58,399+0800 INFO (jsonrpc/4) [storage.Mount] mounting 10.66.148.11:/home/jiawu/nfs2 at /rhev/data-center/mnt/10.66.148.11:_home_jiawu_nfs2 (mount:204) 2018-05-07 19:47:58,452+0800 ERROR (jsonrpc/4) [storage.HSM] Could not connect to storageServer (hsm:2398) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2395, in connectStorageServer conObj.connect() File "/usr/lib/python2.7/site-packages/vdsm/storage/storageServer.py", line 430, in connect return self._mountCon.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: (32, ';mount.nfs: mounting 10.66.148.11:/home/jiawu/nfs2 failed, reason given by server: No such file or directory\n')
I just checked it and that share works with NFSv3 but not with NFSv4: [stirabos@t470s ~]$ sudo mount -t nfs4 10.66.148.11:/home/jiawu/nfs2 /tmp/test mount.nfs4: mounting 10.66.148.11:/home/jiawu/nfs2 failed, reason given by server: No such file or directory [stirabos@t470s ~]$ sudo mount -t nfs 10.66.148.11:/home/jiawu/nfs2 /tmp/test [stirabos@t470s ~]$ echo $? 0 I suggest to double check NFS server configuration.
Closing. Please re-open if this can be mounted and HE deployment still does not work