Created attachment 1168419 [details] vdsm.log Description of problem: While trying to setup new ovirt-engine (Centos 7, 3.6.7.4-1), after adding a new host (Centos 7), got some errors when adding NFS storage, that is a directory shared from ovirt-engine machine. Logs attached. Version-Release number of selected component (if applicable): ovirt-engine-3.6.7.4-1 How reproducible: Steps to Reproduce: 1. install ovirt-engine-3.6.7.4-1 on fresh CentOS 7 machine. 2. add host (another fresh CentOS 7 machine) 3. create nfs-shared directory on engine machine 4. try to add nfs storage to engine. Actual results: Error while trying to mount nfs storage Expected results: New storage attached to host, and datacenter up Additional info: More logs can be provided on request
Created attachment 1168420 [details] engine.log
It looks like you encounter a problem to mount the storage domain. Can u please try to mount the storage domain manually from the Host server
Relevant part of the log: Traceback (most recent call last): File "/usr/share/vdsm/storage/hsm.py", line 2470, in connectStorageServer conObj.connect() File "/usr/share/vdsm/storage/storageServer.py", line 455, in connect return self._mountCon.connect() File "/usr/share/vdsm/storage/storageServer.py", line 237, in connect six.reraise(t, v, tb) File "/usr/share/vdsm/storage/storageServer.py", line 229, in connect self._mount.mount(self.options, self._vfsType, cgroup=self.CGROUP) File "/usr/share/vdsm/storage/mount.py", line 225, in mount return self._runcmd(cmd, timeout) File "/usr/share/vdsm/storage/mount.py", line 241, in _runcmd raise MountError(rc, ";".join((out, err))) MountError: (32, ';mount.nfs: Connection timed out\n')
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
(In reply to Maor from comment #2) > It looks like you encounter a problem to mount the storage domain. > Can u please try to mount the storage domain manually from the Host server I tried it, and it fails with the same error. Seems to be an environment issue. I'm investigating to make sure it is not engine-related in any way, but don't seems to be.
Got it working, the NFS daemons in the engine machine were in bad state. Feel free to close