How does RHEV-M technically report that RHEV host status is Non-Operational?

Solution Verified - Updated -

Issue

  • We had updated a firmware of a storage controller out of two controllers. Even though the other storage controller, whose firmware was not being updated, was alive, hosts connected with the other storage controller (by multipath configuration) went into Non-Operational status due to disconnection of "Storage Domain".

We expected that it should not have been in Non-Operational status because two paths were alive, even though other two paths were also disconnected due to updated firmware.

How do we understand this behavior technically?

Environment

  • Red Hat Enterprise Virtualization 3.x

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.