[ovirt-users] Installation of oVirt 4.1, Gluster Storage and Hosted Engine

[Gianluca Cecchi]

Il 07/Lug/2017 18:38, "Simone Marchioni" <s.marchioni at lynx2000.it> ha
scritto:

Hi to all,

I have an old installation of oVirt 3.3 with the Engine on a separate
server. I wanted to test the last oVirt 4.1 with Gluster Storage and Hosted
Engine.

Followed the following tutorial:

http://www.ovirt.org/blog/2017/04/up-and-running-with-ovirt-
4.1-and-gluster-storage/




... snip ...


[script1]
action=execute
ignore_script_errors=no
file=/usr/share/ansible/gdeploy/scripts/grafton-sanity-check.sh -d sdb -h
ha1.domain.it,ha2.domain.it,ha3.domain.it

... snip ...




When I hit "Deploy" button the Deployment fails with the following error:

PLAY [gluster_servers] ******************************
***************************

TASK [Run a shell script] ******************************
************************
fatal: [ha1.domain.it]: FAILED! => {"failed": true, "msg": "The conditional
check 'result.rc != 0' failed. The error was: error while evaluating
conditional (result.rc != 0): 'dict object' has no attribute 'rc'"}
fatal: [ha2.domain.it]: FAILED! => {"failed": true, "msg": "The conditional
check 'result.rc != 0' failed. The error was: error while evaluating
conditional (result.rc != 0): 'dict object' has no attribute 'rc'"}
fatal: [ha3.domain.it]: FAILED! => {"failed": true, "msg": "The conditional
check 'result.rc != 0' failed. The error was: error while evaluating
conditional (result.rc != 0): 'dict object' has no attribute 'rc'"}
    to retry, use: --limit @/tmp/tmpcV3lam/run-script.retry

PLAY RECAP ************************************************************
*********
ha1.domain.it            : ok=0    changed=0    unreachable=0 failed=1
ha2.domain.it            : ok=0    changed=0    unreachable=0 failed=1
ha3.domain.it            : ok=0    changed=0    unreachable=0 failed=1

What I'm doing wrong? Maybe I need to initializa glusterfs in some way...
What are the logs used to log the status of this deployment so I can check
the errors?

Thanks in advance!
Simone
_______________________________________________



Gdeploy uses ansible that seems to fail at its first step when executing
its shell module

http://docs.ansible.com/ansible/shell_module.html

In practice in my opinion the shell script defined by [script1] (
grafton-sanity-check.sh) above doesn't exit with a return code (rc) for
some reason...
Perhaps you have already done a partial step previously?  or your disks
already contain a label?
Is it correct sdb as the target for your disk configuration for gluster?
I would try to reinitialize the disks, such as

dd if=/dev/zero of=/dev/sdb bs=1024k count=1

ONLY if it is correct that sdb is the disk to format for brick filesystem..
Hih,
Gianluca
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170707/b84efe22/attachment-0001.html>