Hi,

So I wiped everything and went through the wizard to set up hyper converged Storage & Hosted engine…
Storage was created OK and it went straight on to hosted engine deployment
this failed with the same error…

I have this in vdsm.log

Do you have any idea ?

the system it’s self created the Gluster storage etc


cat: 8.9G: No such file or directory
[root@ovirt3 ~]# [root@ovirt3 tmp]# tail /var/log/vdsm/vdsm.log
-bash: [root@ovirt3: command not found
[root@ovirt3 ~]# 2019-12-07 19:45:19,879+0000 INFO  (jsonrpc/6) [api.host] FINISH getAllVmStats return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} from=::ffff:192.168.222.198,35950 (api:54)
-bash: syntax error near unexpected token `('
[root@ovirt3 ~]# 2019-12-07 19:45:19,880+0000 INFO  (jsonrpc/6) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:312)
-bash: syntax error near unexpected token `('
[root@ovirt3 ~]# 2019-12-07 19:45:19,945+0000 INFO  (vmrecovery) [vdsm.api] START getConnectedStoragePoolsList(options=None) from=internal, task_id=621dfe30-de01-428d-b9fb-c6fd2e6df33e (api:48)
-bash: syntax error near unexpected token `('
[root@ovirt3 ~]# 2019-12-07 19:45:19,946+0000 INFO  (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=621dfe30-de01-428d-b9fb-c6fd2e6df33e (api:54)
-bash: syntax error near unexpected token `('
[root@ovirt3 ~]# 2019-12-07 19:45:19,946+0000 INFO  (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:711)
-bash: syntax error near unexpected token `('
[root@ovirt3 ~]# 2019-12-07 19:45:24,770+0000 INFO  (periodic/3) [vdsm.api] START repoStats(domains=()) from=internal, task_id=434e98ab-eb9c-4dff-b92d-81f57fdf6ed3 (api:48)
-bash: syntax error near unexpected token `('
[root@ovirt3 ~]# 2019-12-07 19:45:24,770+0000 INFO  (periodic/3) [vdsm.api] FINISH repoStats return={} from=internal, task_id=434e98ab-eb9c-4dff-b92d-81f57fdf6ed3 (api:54)
-bash: syntax error near unexpected token `('
[root@ovirt3 ~]# 2019-12-07 19:45:24,950+0000 INFO  (vmrecovery) [vdsm.api] START getConnectedStoragePoolsList(options=None) from=internal, task_id=3c831c51-3f79-4d87-ad8a-a4a794f47b8f (api:48)
-bash: syntax error near unexpected token `('
[root@ovirt3 ~]# 2019-12-07 19:45:24,950+0000 INFO  (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=3c831c51-3f79-4d87-ad8a-a4a794f47b8f (api:54)
-bash: syntax error near unexpected token `('
[root@ovirt3 ~]# 2019-12-07 19:45:24,950+0000 INFO  (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:711)
-bash: syntax error near unexpected token `('
[root@ovirt3 ~]# [root@ovirt3 tmp]# 
-bash: [root@ovirt3: command not found
[root@ovirt3 ~]# 

On 24 Nov 2019, at 23:07, Strahil Nikolov <hunter86_bg@yahoo.com> wrote:

I guess it's filtered because /dev/sdb today is not /dev/sdb after a reboot.
You'd better use a persistent name like /dev/disk/by-id/scsi-xxx or anything in /dev/disk/by-id/, /dev/disk/by/uuid/, /dev/disk/by-path/, /dev/disk/by-partuuid/ - as they are supposed to be persistent.

Best Regards,
Strahil Nikolov

В събота, 23 ноември 2019 г., 21:27:38 ч. Гринуич+2, <rob.downer@orbitalsystems.co.uk> написа:


Gluster fails with
vdo: ERROR - Device /dev/sdb excluded by a filter.\n",

however I have run

[root@ovirt1 ~]# vdo create --name=vdo1 --device=/dev/sdb --force
Creating VDO vdo1
Starting VDO vdo1
Starting compression on VDO vdo1
VDO instance 1 volume is ready at /dev/mapper/vdo1

there are no filters in lvm.conf

I have run

wipefs -a /dev/sdb —force

on all hosts before start
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org