Select Your Language

Infrastructure and Management

Cloud Computing

Storage

Runtimes

Integration and Automation

  • Comments
  • VMs unknown state and RHEV-H's Non Responsive

    Posted on

    Running latest RHEV-H and latest RHEV-M on RHEL 6.6.
    Just did a yum update which updated the following,

    Transaction performed with:
    Installed rpm-4.8.0-38.el6_6.x86_64 @rhel-x86_64-server-6
    Updated subscription-manager-1.12.14-7.el6.x86_64 @rhel-x86_64-server-6
    Installed yum-3.2.29-60.el6.noarch @rhel-x86_64-server-6
    Installed yum-metadata-parser-1.1.2-16.el6.x86_64 @anaconda-RedHatEnterpriseLinux-201311111358.x86_64/6.5
    Installed yum-plugin-versionlock-1.1.30-30.el6.noarch @rhel-x86_64-server-6
    Packages Altered:
    Updated java-1.7.0-openjdk-1:1.7.0.71-2.5.3.2.el6_6.x86_64 @rhel-x86_64-server-6
    Update 1:1.7.0.75-2.5.4.0.el6_6.x86_64 @rhel-x86_64-server-6
    Updated openssl-1.0.1e-30.el6_6.4.x86_64 @rhel-x86_64-server-6
    Update 1.0.1e-30.el6_6.5.x86_64 @rhel-x86_64-server-6
    Updated selinux-policy-3.7.19-260.el6_6.1.noarch @rhel-x86_64-server-6
    Update 3.7.19-260.el6_6.2.noarch @rhel-x86_64-server-6
    Updated selinux-policy-targeted-3.7.19-260.el6_6.1.noarch @rhel-x86_64-server-6
    Update 3.7.19-260.el6_6.2.noarch @rhel-x86_64-server-6
    Updated subscription-manager-1.12.14-7.el6.x86_64 @rhel-x86_64-server-6
    Update 1.12.14-9.el6_6.x86_64 @rhel-x86_64-server-6

    After that and a RHEV-M reboot all, VM's went in unkown state, all hosts (RHEV-H), storage domains, clusters, datacenters went in Non Responsive.
    Lots of errors in engine.log, like

    2015-01-21 21:55:25,414 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (DefaultQuartzScheduler_Worker-31) Command GetCapabilitiesVDSCommand(HostName = rhevbohnw01.unix.regionh.top.local, HostId = 4256f307-fbab-4ae7-bdf0-7025d1ecf007, vds=Host[rhevbohnw01.unix.regionh.top.local,4256f307-fbab-4ae7-bdf0-7025d1ecf007]) execution failed. Exception: VDSNetworkException: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)

    One per Host.

    Decided to do a yum undo and without reboot everything is fine again.

    Did the same yum update on another environment also with same versions RHEV-M and RHEV-H. Exact same issue here where undo also corrected the problem.

    Anybody experienced the same??

    by

    points

    Responses

    Red Hat LinkedIn YouTube Facebook X, formerly Twitter

    Quick Links

    Help

    Site Info

    Related Sites

    © 2025 Red Hat