Hello, I think options for mounting the hosted-engine Volume changed in latest vdsm to support mounting from backup-volfile-servers.
[root@microcloud28 ~]# rpm -qi vdsm Name : vdsm Version : 4.17.28 Release : 1.el7 Architecture: noarch Install Date: Fri 10 Jun 2016 11:17:37 AM CEST Group : Applications/System Size : 3828639 License : GPLv2+ Signature : RSA/SHA1, Fri 03 Jun 2016 12:53:20 AM CEST, Key ID 7aebbe8261e8806c Source RPM : vdsm-4.17.28-1.el7.src.rpm Now my hosts have problems to mount the Volume. On hosted-engine setup I configured the (Replica 3) volume to be "glusterfs.rxmgmt.databay.de:/engine" which ist a Round-Robin DNS to my gluster hosts and _not_ the DNS-Name of any gluster-brick. Now VDSM logs: jsonrpc.Executor/3::DEBUG::2016-06-25 19:40:02,520::fileUtils::143::Storage.fileUtils::(createdir) Cre ating directory: /rhev/data-center/mnt/glusterSD/glusterfs.rxmgmt.databay.de:_engine mode: None jsonrpc.Executor/3::DEBUG::2016-06-25 19:40:02,520::storageServer::364::Storage.StorageServer.MountCon nection::(_get_backup_servers_option) Using bricks: ['microcloud21.rxmgmt.databay.de', 'microcloud24.r xmgmt.databay.de', 'microcloud27.rxmgmt.databay.de'] jsonrpc.Executor/3::WARNING::2016-06-25 19:40:02,520::storageServer::370::Storage.StorageServer.MountC onnection::(_get_backup_servers_option) gluster server u'glusterfs.rxmgmt.databay.de' is not in bricks ['microcloud21.rxmgmt.databay.de', 'microcloud24.rxmgmt.databay.de', 'microcloud27.rxmgmt.databay.de' ], possibly mounting duplicate servers jsonrpc.Executor/3::DEBUG::2016-06-25 19:40:02,520::mount::229::Storage.Misc.excCmd::(_runcmd) /usr/bi n/taskset --cpu-list 0-7 /usr/bin/sudo -n /usr/bin/systemd-run --scope --slice=vdsm-glusterfs /usr/bin /mount -o backup-volfile-servers=microcloud21.rxmgmt.databay.de:microcloud24.rxmgmt.databay.de:microcl oud27.rxmgmt.databay.de glusterfs.rxmgmt.databay.de:/engine /rhev/data-center/mnt/glusterSD/glusterfs. rxmgmt.databay.de:_engine (cwd None) jsonrpc.Executor/3::ERROR::2016-06-25 19:40:02,540::hsm::2473::Storage.HSM::(connectStorageServer) Cou ld not connect to storageServer 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 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, ';Running scope as unit run-13461.scope.\nmount.nfs: an incorrect mount option was specified\n') So the mount is tried as NFS which hasn't the option "-o backup-volfile-servers=...". As a consequence the host is disabled in engine. The only way to get it up is mounting the volume manually to /rhev/data-center/mnt/glusterSD/glusterfs. rxmgmt.databay.de:_engine and activate it manually in Management-GUI. Should and can I change the hosted_storage entry-point globally to i.e. "microcloud21.rxmgmt.databay.de" or wouldn't it be better globally that VDSM uses "-t glusterfs" to try to mount the gluster-Volume regardless which DNS Name for the gluster-service is used ? Ovirt is: ovirt-release36.noarch 1:3.6.6-1 Bye -- *Ralf Schenk* fon +49 (0) 24 05 / 40 83 70 fax +49 (0) 24 05 / 40 83 759 mail *r...@databay.de* <mailto:r...@databay.de> *Databay AG* Jens-Otto-Krag-Straße 11 D-52146 Würselen *www.databay.de* <http://www.databay.de> Sitz/Amtsgericht Aachen • HRB:8437 • USt-IdNr.: DE 210844202 Vorstand: Ralf Schenk, Dipl.-Ing. Jens Conze, Aresch Yavari, Dipl.-Kfm. Philipp Hermanns Aufsichtsratsvorsitzender: Klaus Scholzen (RA) ------------------------------------------------------------------------
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users