How to update expired RHEV certificates when all RHEV hosts got 'Non-responsive'

Solution Verified - Updated -

Issue

  • All hosts went into non responsive status in RHV-M and engine is unable to communicate with the hosts.

  • The engine log shows below error messages

    2017-02-02 13:58:12,812 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (DefaultQuartzScheduler_Worker-29) [2e3629ad] Command GetCapabilitiesVDSCommand(HostName = , HostId = 01e21216-9071-406d-9f01-65f8a0fc560d, vds=Host[01e21216-9071-406d-9f01-65f8a0fc560d]) execution failed. Exception: VDSNetworkException: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_expired

Environment

  • Red Hat Enterprise Virtualization 3.2 to 3.6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content