How to Clean Up a Failed Self-hosted Engine Deployment?

Solution Verified - Updated -


  • 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/", line 142, in _executeMethod
      File "/usr/share/ovirt-hosted-engine-setup/plugins/ovirt-hosted-engine-setup/vm/", 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


  • 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, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content