Created attachment 1459643 [details] log from failed re-run of the --deploy Description of problem: next run (start over) hosted-engine --deploy failed Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-2.2.22-1.el7.noarch ovirt-hosted-engine-setup-2.2.23-1.el7.noarch How reproducible: I run deploy, but it failed. Even I deleted bridge (see bug #1602250) and run ovirt-hosted-engine-cleanup, at the next run the script fails. Actual results: [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "network default not found"} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook Expected results: able to run again
Not identified as blocker for 4.2.7, moving to 4.2.8
The ovirt bridge and virsh default net are 2 different things. After deleting the bridge, you'll need to have a default virsh net for the deployment to succeed. I would check that there's no default network defined in virsh. # virsh net-list Name State Autostart Persistent ---------------------------------------------------------- If not, go ahead and recreate the default virsh net: # virsh net-define /usr/share/libvirt/networks/default.xml Network default defined from /usr/share/libvirt/networks/default.xml # virsh net-autostart default Network default marked as autostarted # virsh net-start default Network default started Then retry the deploy. This should resolve your issue: "[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "network default not found"}".
re-targeting to 4.3.1 since this BZ has not been proposed as blocker for 4.3.0. If you think this bug should block 4.3.0 please re-target and set blocker flag.
The bug is not reproducible anymore. Closing as NOTABUG.