self hosted-engine install fails with "Waiting for cluster 'Default' to become operational" error message.

Solution Verified - Updated -

Environment

  • Red Hat Enterprise Virtualization 3.3

Issue

  • Installation issues with the self-hosted engine:
Waiting for cluster 'Default' to become operational...
[ ERROR ] Timed out while waiting for cluster to become ready. Please check the logs.
[ ERROR ] Failed to execute stage 'Closing up': 'NoneType' object has no attribute '__dict__'
[ INFO  ] Stage: Clean up
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination

         2014-05-02 17:47:29 DEBUG otopi.plugins.ovirt_hosted_engine_setup.engine.add_host add_host._wait_cluster_cpu_ready:254 cluster <ovirtsdk.infrastructure.brokers.Cluster object at 0x3086d10> cluster.__dict__ {'_Base__context': 49616976, 'glusterhooks': <ovirtsdk.infrastructure.brokers.ClusterGlusterHooks object at 0x3086d90>, 'glustervolumes': <ovirtsdk.infrastructure.brokers.ClusterGlusterVolumes object at 0x3086dd0>, 'superclass': <ovirtsdk.xml.params.Cluster object at 0x3086f50>, 'networks': <ovirtsdk.infrastructure.brokers.ClusterNetworks object at 0x3086850>, 'permissions': <ovirtsdk.infrastructure.brokers.ClusterPermissions object at 0x3086ad0>}

Resolution

  • This issue has been resolved with the following bug fix:

http://rhn.redhat.com/errata/RHBA-2014-0546.html

Root Cause

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.