It seems as though there is a problem with the grafton sanity check script. It took me a moment to spot the error below. Note the inconsistencies in the host names. changed: [obe.cyber-range.lan] (this is the correct piece of info) ping: ovir-be.cyber-range.lan (the ping portion changed the host name somehow) I'm not quite strong enough with scripting to fix it. Can anyone take a look at it? [root@vmh ~]# gdeploy -c gdeploy.conf -vv ansible-playbook 2.6.2 config file = /etc/ansible/ansible.cfg configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib/python2.7/site-packages/ansible executable location = /usr/bin/ansible-playbook python version = 2.7.5 (default, Jul 13 2018, 13:06:57) [GCC 4.8.5 20150623 (Red Hat 4.8.5-28)] Using /etc/ansible/ansible.cfg as config file PLAYBOOK: run-script.yml *********************************************************************************************************************************************** 1 plays in /tmp/tmpubmQdM/run-script.yml PLAY [gluster_servers] ************************************************************************************************************************************************* META: ran handlers TASK [Run a shell script] ********************************************************************************************************************************************** task path: /tmp/tmpubmQdM/run-script.yml:7 changed: [obe.cyber-range.lan] => (item=/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d /dev/sda -h ovir-be.cyber-range.lan) => {"changed": true, "failed_when_result": false, "item": "/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d /dev/sda -h ovir-be.cyber-range.lan", "rc": 0, "stderr": "Shared connection to obe.cyber-range.lan closed.\r\n", "stderr_lines": ["Shared connection to obe.cyber-range.lan closed."], "stdout": "ping: ovir-be.cyber-range.lan: Name or service not known\r\nping failed unable to reach ovir-be.cyber-range.lan\r\nUsage: grep [OPTION]... PATTERN [FILE]...\r\nTry 'grep --help' for more information.\r\n", "stdout_lines": ["ping: ovir-be.cyber-range.lan: Name or service not known", "ping failed unable to reach ovir-be.cyber-range.lan", "Usage: grep [OPTION]... PATTERN [FILE]...", "Try 'grep --help' for more information."]} META: ran handlers META: ran handlers PLAY RECAP ************************************************************************************************************************************************************* obe.cyber-range.lan : ok=1 changed=1 unreachable=0 failed=0 Error: Unsupported disk type! Only ['raid10', 'raid5', 'raid6', 'jbod'] are supported BTW, this is directly related to my previous post: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/IPSNXA3GHYFU... . I did change some parameters since then. I made sure I blacklisted my multipath device and dont have GPT label in the MBR. This is the most recent results of my efforts. Closer but not done quite yet.... 😉