RHV: Non-Operational Hosts after Restoring Backup or Migrating to Self-Hosted Engine

Solution Verified - Updated -

Issue

  • After restoring an upgraded RHEV environment into a brand new 3.6 RHEV environment, the host(s) is being shown as non-operational with rhevm logical network missing
  • Migrated bare-to-Self Hosted-Engine from a bare metal RHEV environment originated on version (3.5 or before), won't list the HE host as Up
  • Management network still called rhevm in original environment.

Environment

  • Bare-Metal Red Hat Virtualization 4.x, 3.6
    • Upgraded from 3.5 or earlier.
    • Migrated to a Self Hosted-Engine(HE) environment

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

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