I found another bug that is related to this problem: https://bugzilla.redhat.com/show_bug.cgi?id=1449217 On the initial oVirt install, the gdeploy version is 2.0.1, which causes the problem stated in bug # 1449217 After upgrading gdeploy to 2.0.2, you are left with the problem I described in my original post. This link also had the same issue https://www.spinics.net/lists/gluster-users/msg31220.html Let me know if you still want me to file the bug On 2017-06-08 00:09, knarra wrote:
On 06/07/2017 10:33 PM, ovirt@fateknollogee.com wrote:
I just used all the default setting installing from the iso. ansible v2.3.0.0 gdeploy v2.0.2 Thanks for conforming. I thought i have logged bug for this but when i went and looked back realized that i do not have any. would you mind logging bug for this?
On 2017-06-07 09:41, knarra wrote:
On 06/07/2017 03:15 AM, ovirt@fateknollogee.com wrote:
I finally figured out what the error was all about....
The default location for the gdeploy script is: /usr/share/ansible/gdeploy/scripts/grafton-sanity-check.sh
The oVirt node installer "ovirt-node-ng-installer-ovirt-4.1-2017060504.iso" installed it in a different location: /usr/share/gdeploy/scripts/grafton-sanity-check.sh
I copied the "gdeploy" folder to the default location & the error went away.
**btw, I installed oVirt from scratch twice & both times got the same error**
just wondering how did this change happen. I will install with the iso what you mentioned above and let you know the results. But before that have few questions. Can you please tell me what is the version of ansible and gdeploy you have on the node ?
On 2017-06-06 13:01, ovirt@fateknollogee.com wrote:
Ok, I will re-check a few things based on this: https://bugzilla.redhat.com/show_bug.cgi?id=1405447
On 2017-06-06 12:58, ovirt@fateknollogee.com wrote:
How do I check that?
Today, I'm re-installing but getting this error message:
PLAY [gluster_servers] *********************************************************
TASK [Run a shell script] ****************************************************** fatal: [ovirt-N1-f25.fatek-dc.lab]: 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: [ovirt-N3-f25.fatek-dc.lab]: 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: [ovirt-N2-f25.fatek-dc.lab]: 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/tmpEzKSy6/run-script.retry
PLAY RECAP ********************************************************************* ovirt-N1-f25.fatek-dc.lab : ok=0 changed=0 unreachable=0 failed=1 ovirt-N2-f25.fatek-dc.lab : ok=0 changed=0 unreachable=0 failed=1 ovirt-N3-f25.fatek-dc.lab : ok=0 changed=0 unreachable=0 failed=1
On 2017-06-01 00:08, knarra wrote: > On 06/01/2017 01:19 AM, ovirt@fateknollogee.com wrote: >> Any ideas what this is: >> >> TASK [Run a shell script] >> ****************************************************** >> fatal: [ovirt-node1.lab]: 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: [ovirt-node3.lab]: 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: [ovirt-node2.lab]: 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/tmpaOHOtY/run-script.retry >> _______________________________________________ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users > > Hi, > > Can you see if the script which is getting execute is present > in that path ? > > Thanks > > kasturi