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',
'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.
On Mon, Apr 16, 2018 at 8:44 AM, <dhy...@sina.com> wrote:
> when I depoy hosted engine by #hosted-engine --deploy
> |- [ INFO ] Stage: Transaction setup
> |- [ INFO ] Stopping engine service
> |- [ INFO ] Stopping ovirt-fence-kdump-listener service
> |- [ INFO ] Stopping dwh service
> |- [ INFO ] Stopping Image I/O Proxy service
> |- [ INFO ] Stopping vmconsole-proxy service
> |- [ INFO ] Stopping websocket-proxy service
> |- [ INFO ] Stage: Misc configuration
> [ ERROR ] Engine setup got stuck on the appliance
> [ ERROR ] Failed to execute stage 'Closing up': Engine setup is
> stalled on the appliance since 1800 seconds ago. Please check
> its log on the appliance.
> [ INFO ] Stage: Clean up
> [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-
> [ INFO ] Stage: Pre-termination
> [ INFO ] Stage: Termination
> [ ERROR ] Hosted Engine deployment failed: this system is not
> reliable, please check the issue,fix and redeploy
> Log file is located at /var/log/ovirt-hosted-engine-
> engine-setup take a lot time in "Stage: Misc configuration", and finaly
> My mail attachment is hosted-engine --deploy log and VM engine-setup log.
> would you give me some advise? Thanks...
> Users mailing list
Users mailing list