Description of problem: 'hosted-engine --deploy' fails when using an NFS share that is available over NFSv4 only Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-1.0.0-0.9.beta4.el6ev.noarch from is24.2 build How reproducible: always Steps to Reproduce: 1. run hosted-engine --deploy 2. when prompted for a storage path, provide a path which is available only over NFSv4 Actual results: Setup fails after providing the path. Sometimes it presents as a bogus SSL error, and sometimes as a read timeout. The two errors I have seen are: [ ERROR ] Failed to execute stage 'Environment customization': [Errno 1] _ssl.c:492: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed and [ ERROR ] Failed to execute stage 'Environment customization': The read operation timed out Expected results: The share is mounted and setup continues Additional info: Both errors disappeared for me when I enabled NFS v3 on the storage server as well as NFSv4. Mounting the share manually from the same system worked both before and after enabling NFSv3
Federico, is NFS v4 supported by VDSM? If so, how may I specify to enable support for that while connecting the storage?
(In reply to Sandro Bonazzola from comment #1) > Federico, is NFS v4 supported by VDSM? If so, how may I specify to enable > support for that while connecting the storage? protocol_version in connectStorageServer: Thread-8155::INFO::2013-11-28 07:27:35,768::logUtils::44::dispatcher::(wrapper) Run and protect: connectStorageServer(domType=1, spUUID='00000000-0000-0000-0000-000000000000', conList=[{'port': '', 'connection': ' vm-rhsrv1:/srv/export1/nfs/ovirt2', 'iqn': '', 'portal': '', 'user': '', 'protocol_version': '4', 'password': '******', 'id': '1f2b41ec-23a6-493c-9bfe-bb274ad45663'}], options=None)
Didi, can you change storage type selection dialog for adding NFSv3 and NFSv4 instead of NFS and change the protocol version accordingly?
Merged on upstream master and 1.0 branches.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0083.html