Phillip,

 

The relevant lines from the vdsm logs are the following:

 

jsonrpc.Executor/6::INFO::2017-07-17 14:24:41,005::logUtils::49::dispatcher::(wrapper) Run and protect: connectStorageServer(domType=1, spUUID=u'00000000-0000-0000-0000-000000000000', conList=[{u'protocol

_version': 3, u'connection': u'192.168.1.21:/srv/ovirt', u'user': u'kvm', u'id': u'dbeb8ab4-849f-4728-8ee9-f891bb84ce2f'}], options=None)

jsonrpc.Executor/6::DEBUG::2017-07-17 14:24:41,006::fileUtils::209::Storage.fileUtils::(createdir) Creating directory: /rhev/data-center/mnt/192.168.1.21:_srv_ovirt mode: None

jsonrpc.Executor/6::DEBUG::2017-07-17 14:24:41,007::fileUtils::218::Storage.fileUtils::(createdir) Using existing directory: /rhev/data-center/mnt/192.168.1.21:_srv_ovirt

jsonrpc.Executor/6::INFO::2017-07-17 14:24:41,007::mount::226::storage.Mount::(mount) mounting 192.168.1.21:/srv/ovirt at /rhev/data-center/mnt/192.168.1.21:_srv_ovirt

jsonrpc.Executor/6::ERROR::2017-07-17 14:26:46,098::hsm::2403::Storage.HSM::(connectStorageServer) Could not connect to storageServer

Traceback (most recent call last):

  File "/usr/share/vdsm/storage/hsm.py", line 2400, in connectStorageServer

    conObj.connect()

  File "/usr/share/vdsm/storage/storageServer.py", line 456, in connect

    return self._mountCon.connect()

  File "/usr/share/vdsm/storage/storageServer.py", line 238, in connect

    six.reraise(t, v, tb)

  File "/usr/share/vdsm/storage/storageServer.py", line 230, in connect

    self._mount.mount(self.options, self._vfsType, cgroup=self.CGROUP)

  File "/usr/lib/python2.7/site-packages/vdsm/storage/mount.py", line 229, in mount

    timeout=timeout, cgroup=cgroup)

  File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 53, in __call__

    return callMethod()

  File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 51, 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: Connection timed out\n')

 

 

From: <users-bounces@ovirt.org> on behalf of Phillip Bailey <phbailey@redhat.com>
Date: Tuesday, 18 July 2017 at 13:48
To: Luca 'remix_tj' Lorenzetto <lorenzetto.luca@gmail.com>
Cc: users <users@ovirt.org>
Subject: Re: [ovirt-users] Hosted Engine/NFS Troubles

 

On Mon, Jul 17, 2017 at 3:34 PM, Luca 'remix_tj' Lorenzetto <lorenzetto.luca@gmail.com> wrote:

On Mon, Jul 17, 2017 at 9:05 PM, Phillip Bailey <phbailey@redhat.com> wrote:
> Hi,
>
> I'm having trouble with my hosted engine setup (v4.0) and could use some
> help. The problem I'm having is that whenever I try to add additional hosts
> to the setup via webadmin, the operation fails due to storage-related
> issues.
>
> webadmin shows the following error messages:
>
> "Host <host name> cannot access the Storage Domain(s) hosted_storage
> attached to the Data Center Default. Setting Host state to Non-Operational.
> Failed to connect Host ovirt-node-1 to Storage Pool Default"
>

Hi Phillip,

your hosted engine storage is on nfs, right? Did you test if you can
mount manually on each host?

Hi Luca,

 

Yes, both storage domains are on NFS (v3) and I am able to successfully mount them manually on the hosts.

 

Luca



--
"E' assurdo impiegare gli uomini di intelligenza eccellente per fare
calcoli che potrebbero essere affidati a chiunque se si usassero delle
macchine"
Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)

"Internet è la più grande biblioteca del mondo.
Ma il problema è che i libri sono tutti sparsi sul pavimento"
John Allen Paulos, Matematico (1945-vivente)

Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , <lorenzetto.luca@gmail.com>