Bug 1168723 - After adding host rhev-hypervisor 7.0 to RHEVM 3.5, host change state to non-responsive
Summary: After adding host rhev-hypervisor 7.0 to RHEVM 3.5, host change state to non-...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: rhev-hypervisor
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 3.5.0
Assignee: Fabian Deutsch
QA Contact: Petr Kubica
URL:
Whiteboard: node
Depends On:
Blocks: rhevh-7.0
TreeView+ depends on / blocked
 
Reported: 2014-11-27 16:25 UTC by Petr Kubica
Modified: 2016-02-10 20:07 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-30 12:45:05 UTC
oVirt Team: Node
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
engine-log (402.57 KB, application/x-gzip)
2014-11-27 16:25 UTC, Petr Kubica 		no flags Details
vdsm-log (21.00 KB, application/x-gzip)
2014-11-27 16:27 UTC, Petr Kubica 		no flags Details
View All

Description Petr Kubica 2014-11-27 16:25:59 UTC 
Created attachment 962161 [details]
engine-log

Description of problem:
After adding host rhev-hypervisor 7.0 to RHEVM 3.5, host change state to non-responsive.

Version-Release number of selected component (if applicable):
RHEVM 3.5.0-0.21.el6ev
RHEVH rhev-hypervisor7-7.0-20141120.1152948.3

How reproducible:
Always

Steps to Reproduce:
1. Install rhevm 3.5
2. Install host -> rhev-hypervisor7
3. Try to add host to engine  

Actual results:
Host after sucessful install, changed state to non-responsive

Additional info:
attached engine logs and logs from rhev-h
Comment 1 Petr Kubica 2014-11-27 16:27:11 UTC 
Created attachment 962162 [details]
vdsm-log
Comment 7 Fabian Deutsch 2014-11-28 07:09:20 UTC 
I saw this in the vdsm logs:

MainThread::DEBUG::2014-11-27 15:48:04,660::libvirtconnection::143::root::(wrapper) Unknown libvirterror: ecode: 43 edom: 19 level: 2 message: Network not found: no network with matching name 'vdsm-rhevm'

Dan, could this lead to connection issues?
Comment 8 Liushihui 2014-11-28 10:53:41 UTC 
This bug can't reproduce every time. I try it as the following steps. it can't reproduce now.
1. when rhevh in non-responsive status,the bug can't reproduce after reboot it, rhevh can register to rhevm server successfully. 
2. Reinstall the rhev-hypervisor7-7.0-20141119.0.el7ev on the same machine which occurred this problem, then registered it to rhevm-3.5.0-0.21.el6ev.noarch, it's success to register it to rhevm. 
3.Install the same rhevh on another two machines, then register it to rhevm3.5. it also can't reproduce.
Comment 9 Dan Kenigsberg 2014-11-28 12:12:28 UTC 
(In reply to Fabian Deutsch from comment #7)
> I saw this in the vdsm logs:
> 
> MainThread::DEBUG::2014-11-27
> 15:48:04,660::libvirtconnection::143::root::(wrapper) Unknown libvirterror:
> ecode: 43 edom: 19 level: 2 message: Network not found: no network with
> matching name 'vdsm-rhevm'
> 
> Dan, could this lead to connection issues?

I don't think so. this log noise looks much more like

 bug 1121571 	annoying false error when starting vdsmd

Could you share connectivity.log from the host?
Comment 10 Petr Kubica 2014-11-28 14:50:38 UTC 
I cannot reproduce with my step now, thought yesterday it happen to me with two rhev-h 7.0 machine. Now it seems, that everything working correctly with no error.
Comment 11 Doron Fediuck 2014-11-30 12:45:05 UTC 
Closing since no reproducer available (comment 8 and comment 10).
Please re-open if there's a way to reproduce this issue.
Note You need to log in before you can comment on or make changes to this bug.