[Master] Red Hat Virtualization Host in non-responding state
Environment
- Red Hat Virtualization 4.x
Issue
Red Hat Virtualization Hostis marked asnot-respondinginRHV-Mportal, theEvent Login theRHV-M Admin Portalshows:
Host host-A is not responding. It will stay in Connecting state for a grace period of 60 seconds and after that an attempt to fence the host will be issued.
Resolution
- Below are few known issues and KCS to it:
Issue KCS link Version DNS RHEV: all hosts in Not Responding state All versions Error during handshake: wrong version number RHV: After ovirt-engine restart, some hosts are in Not Responding state Red Hat Virtualization 3.6 and 4 VDSNetworkException: Heartbeat exeeded After upgrading to RHEV 3.5, hosts are periodically being reported as "not responding" RHEV 3.5 SSLError: certificate verify failed Hypervisor may go into 'Non-responsive' due to certificate expiration All versions
Root Cause
-
RHV Hostis markednon-responsiveornot-respondingwhenovirt-engine serviceofRHV-Mangercannot communicate withvdsmdservice ofHost. -
There could be various reasons for this communication gap.
- It could be Network issue on Host, Manager or Network between them.
- VDSM version on Host has stopped/died.
- Host might be hung due to which vdsm service also halted.
- SSL certificate is expired between Host and Manager.
- Host is actually in down status.
- Hosts are registered with FQDN and DNS server is down.
And any possible reason due to which Engine and VDSM service cannot talk with each other.
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.
Comments