Created attachment 946427 [details] The log files of the ovirt directory on the RHEV-M server Description of problem: The RHEL 6.6 hosts in a RHEV-M 3.5 (vt5.1/el6) environment are in a "Non-responsive" state and can't be Activated or Removed, leaving the user to reinstall environment because the hosts are "hung." Rebooting the hosts from a terminal window did nothing for the Admin Portal. Version-Release number of selected component (if applicable): RHEV-M 3.5 (vt5.1/el6) RHEL-6.5-20131111.0 - RHEV-M engine RHEL-6.6-20140926.0 - Hosts How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 946432 [details] Screenshot of the Non-responsive hosts and the greyed menu buttons.
Can you also attach the vdsm logs of these hosts?
Created attachment 946525 [details] VDSM logfiles of Salusa
Created attachment 946526 [details] VDSM logfiles of Kaitain
Upon further review, I did use the default XMLRPC (JSON) that hosts are defaulting to when they are created.
Looking at the logs you are adding 3.2 vdsm to cluster 3.5 so this issue is related to bug 1149655. This version of vdsm seems to work a bit differently than newer vdsms so we need to provide a fix for it.
Due to last comment, it is neither a test blocker nor a blocker. Setting it accordingly.
ok, rhevm-webadmin-portal-3.5.0-0.20.el6ev.noarch 3.2 host (rhel6.5/vdsm-4.10.2-30.1.el6ev.x86_64) in 3.2 clstr in rhevm35 env.
rhev 3.5.0 was released. closing.