RHEV Hypervisor does not automatically detect iSCSI volume after reboot in Red Hat Enterprise Virtualization 3.4
Issue
-
After a reboot of a RHEV hypervisor, the host couldn't connect/login to one of the iSCSI targets, resulting in the host being marked as non-operational because the storage domain could not be activated.
-
After manually executing
iscsiadm
commands to discover and login to the iSCSI target/session, the storage domain was then able to be activated and the host was marked asUp
;
iscsiadm -m discovery -t st -p <ip>
iscsiadm -m node -L all
Environment
- Red Hat Enterprise Virtualization (RHEV) 3.4
- Red Hat Enterprise Virtualization Hypervisor (RHEV-H) 20150115.0.el6
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.