How to Clean Up a Failed Self-hosted Engine Deployment?
Issue
- If a self-hosted engine installation was interrupted and the deployment is re-run, the following error is shown:
Failed to connect to broker, the number of errors has exceeded the limit (1). -
In the installation logs (
/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-*.log) you will see something like:2015-09-01 07:23:13 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in _executeMethod File "/usr/share/ovirt-hosted-engine-setup/plugins/ovirt-hosted-engine-setup/vm/configurevm.py", line 112, in _late_setup RuntimeError: Cannot setup Hosted Engine with other VMs running 2015-09-01 07:23:13 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Environment setup': Cannot setup Hosted Engine with other VMs running
Environment
- Red Hat Enterprise Virtualization (RHEV) >= 3.6
- Self-hosted-engine on FibeChannel or iSCSI
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
