2018-04-16 05:50:09,331+0800 DEBUG otopi.plugins.otopi.network.firewalld plugin.executeRaw:813 execute: ('/usr/bin/firewall-cmd', '--list-all-zones'), executable='None', cwd='None', env=None
2018-04-16 14:21:26,331+0800 DEBUG otopi.plugins.otopi.network.firewalld plugin.executeRaw:869 execute-result: ('/usr/bin/firewall-cmd', '--list-all-zones'), exception
'firewall-cmd --list-all-zones' got stuck on the engine VM; we had similar issue in the past to SELinux rues.
If you are deploying with a custom cloud-init ISO image with custom script please try disabling SELinux there just for engine-setup execution time.
As a general rule I'd suggest to move instead to the new ansible based flow where engine-setup is executed via ansible in a more controllable way.