[RHEV] Host becomes Non-Operational with alert "can't access the storage domain"

Solution Verified - Updated -

Environment

  • Red Hat Enterprise Virtualization (RHEV) v2.x
  • Red Hat Enterprise Virtualization (RHEV) v3.x

Issue

  • Hyperviser name "host1" became Non-Operational with alert "can't access the storage domain xxxx" on other cluster. Why it needs to access storage domain on other cluster?

Resolution

  • Storage domains are associated with Data Centers/Storage Pools and not with clusters inside a data center. All hosts in a data center/storage pool must have access to all of the storage domains in that pool (including ISO domains and Export domains), regardless of which cluster they are in.

  • RHEV requires that the storage storage domains be accessible from all hosts and have a low latency, as high latency to the storage can also cause VDSM to believe that host is not responding and RHEV will put the host into a non-responsive state. This same behavior (non-responsive) is seen with a complete disconnect from the storage as well.

Root Cause

Storage domain was not accessible from host1.

Diagnostic Steps

Entries from vdc-log.txt file.

09Aug 15:19:38 [5736] WARN  - domain <uuid of storage domain> in problem. vds: host1
09Aug 15:24:38 [1812] WARN  - vds host1 not see domain <uuid of storage domain>:VM_Name moved to nonoperational
09Aug 15:24:38 [1812] INFO  - Running command: SetNonOperationalVdsCommand
09Aug 15:24:38 [1472] WARN  - vds host1 not see domain <uuid of storage domain>:VM_Name - vds is in status NonOperational, no need to move to nonoperational

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.