RHEV hypervisor is stuck in 'Unassigned' status in RHEVM WebUI after activating it

Solution Verified - Updated -

Environment

  • Red Hat Enterprise Virtualization 3.1

Issue

  • RHEVM shows hypervisor status as unassigned even after hypervisor has been rebooted and status is up.
  • RHEVM also shows incorrect number of virtual machines running on hypervisor.
  • How to fix this issue so RHEVM shows the correct status.

Resolution

Try restarting ovirt-engine service on RHEV Manager to fix the issue. First stop the ovirt-engine service:

# service ovirt-engine stop

Make sure no jboss/java processes are running on the RHEVM. This command should produce no output:

# ps ax | egrep 'jboss|java' | grep -v grep

If so, then start the ovirt-engine service again:

# service ovirt-engine start

After restarting the service RHEV Manager should show correct information again.

Root Cause

  • RHEV Manager and hypervisor out of sync

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.