Bug 1152191

Summary: Adding 3.2 hosts to 3.5 cluster in RHEV-M 3.5 (vt5.1/el6) results in hung hosts
Product: Red Hat Enterprise Virtualization Manager Reporter: Bill Sanford <bsanford>
Component: vdsm-jsonrpc-javaAssignee: Piotr Kliczewski <pkliczew>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Stehlik <pstehlik>
Severity: medium Docs Contact:
Priority: urgent    
Version: 3.5.0CC: bazulay, benl, bsanford, dfediuck, ecohen, gklein, iheim, jbelka, lsurette, oourfali, pvine, Rhev-m-bugs, sherold, smizrahi, tpelka, vipatel
Target Milestone: ---Keywords: Regression
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 17:15:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1149655    
Bug Blocks:    
Attachments:
Description Flags
The log files of the ovirt directory on the RHEV-M server
none
Screenshot of the Non-responsive hosts and the greyed menu buttons.
none
VDSM logfiles of Salusa
none
VDSM logfiles of Kaitain none

Description Bill Sanford 2014-10-13 14:41:21 UTC 
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:
Comment 1 Bill Sanford 2014-10-13 14:43:35 UTC 
Created attachment 946432 [details]
Screenshot of the Non-responsive hosts and the greyed menu buttons.
Comment 3 Oved Ourfali 2014-10-13 15:35:31 UTC 
Can you also attach the vdsm logs of these hosts?
Comment 4 Bill Sanford 2014-10-13 17:50:46 UTC 
Created attachment 946525 [details]
VDSM logfiles of Salusa
Comment 5 Bill Sanford 2014-10-13 17:51:18 UTC 
Created attachment 946526 [details]
VDSM logfiles of Kaitain
Comment 6 Bill Sanford 2014-10-13 17:52:39 UTC 
Upon further review, I did use the default XMLRPC (JSON) that hosts are defaulting to when they are created.
Comment 7 Bill Sanford 2014-10-13 17:52:40 UTC 
Upon further review, I did use the default XMLRPC (JSON) that hosts are defaulting to when they are created.
Comment 8 Piotr Kliczewski 2014-10-13 18:19:05 UTC 
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.
Comment 9 Oved Ourfali 2014-10-13 18:58:39 UTC 
Due to last comment, it is neither a test blocker nor a blocker. Setting it accordingly.
Comment 11 Jiri Belka 2014-11-21 09:05:18 UTC 
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.
Comment 12 Eyal Edri 2015-02-17 17:15:56 UTC 
rhev 3.5.0 was released. closing.