Description of problem: During dev test functionality was working in ansible-2.5 But now in ansible-2.5.2 it's failing. Below is the error: [ ERROR ] [WARNING]: The loop variable 'item' is already in use. You should set the [ ERROR ] `loop_var` value in the `loop_control` option for the task to something else to [ ERROR ] avoid variable collisions and unexpected behavior. [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Failing to add other hosts and SD creation Expected results: Should auto add other 2 hosts and create other Storage Domains Additional info:
Sahina, is this a blocker?
This should not be blocker.As only HE deployment working fine. Only issue with gluster deployment + HE deployment.
What do you mean by describing "During HE deployment auto add 2nd and 3rd Hosts is failing"? What are reproduction steps? During deployment there is no option to add second and third ha-host automatically in otopi, there is no such option.
Hi Nikolai, We have new feature in RHHI-2.0 to auto add 2nd and 3rd hosts after HE deployment. Here are the ralated bzs for feature. https://bugzilla.redhat.com/show_bug.cgi?id=1573789 https://bugzilla.redhat.com/show_bug.cgi?id=1523568
This
This bug can't be verified as the automatic addition of hosts to the cluster is blocked with BZ 1466132 Moving the target milestone to 4.2.5 same as the dependent bug.
Tested the bug on ovirt-hosted-engine-setup-2.2.23-1 and ansible-2.6.0-5. Could see the hosts 2 and 3 successfully added in the RHV-M. No sign of ansible error. So moving to verified Logs of successfully HE deployment @http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/1574881/
This bugzilla is included in oVirt 4.2.5 release, published on July 30th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.5 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.