Bug 1575584 - Deploy HE failed via cockpit with NFSv4 or NFSv4.1
Summary: Deploy HE failed via cockpit with NFSv4 or NFSv4.1
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: cockpit-ovirt
Classification: oVirt
Component: Hosted Engine
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Ryan Barry
QA Contact: Yihui Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-07 11:01 UTC by Yihui Zhao
Modified: 2018-05-07 12:05 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-07 12:05:13 UTC
oVirt Team: Node
cshao: testing_ack+


Attachments (Terms of Use)
nfsv4 (67.69 KB, image/png)
2018-05-07 11:01 UTC, Yihui Zhao
no flags Details
engine.log (133.86 KB, text/plain)
2018-05-07 11:52 UTC, Yihui Zhao
no flags Details
vdsm.log (6.59 MB, text/plain)
2018-05-07 11:53 UTC, Yihui Zhao
no flags Details

Description Yihui Zhao 2018-05-07 11:01:10 UTC
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:

Comment 1 Yihui Zhao 2018-05-07 11:02:39 UTC
(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.

Comment 2 Ryan Barry 2018-05-07 11:05:42 UTC
Is the NFS v4 environment using kerberos or any other additional configuration?

Comment 3 Yihui Zhao 2018-05-07 11:08:38 UTC
(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.

Comment 4 Yihui Zhao 2018-05-07 11:33:32 UTC
(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

Comment 5 Yihui Zhao 2018-05-07 11:38:50 UTC
(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)?

Comment 6 Simone Tiraboschi 2018-05-07 11:45:10 UTC
Can you please upload also vdsm.log and engine.log ?

Comment 7 Yihui Zhao 2018-05-07 11:52:22 UTC
Created attachment 1432578 [details]
engine.log

Comment 8 Yihui Zhao 2018-05-07 11:53:05 UTC
Created attachment 1432579 [details]
vdsm.log

Comment 9 Simone Tiraboschi 2018-05-07 11:55:40 UTC
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')

Comment 10 Simone Tiraboschi 2018-05-07 12:00:04 UTC
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.

Comment 11 Ryan Barry 2018-05-07 12:05:13 UTC
Closing. Please re-open if this can be mounted and HE deployment still does not work


Note You need to log in before you can comment on or make changes to this bug.