Bug 1529458 - [VDSM] in case the vdsm not up the broker try to reconnect and causes a lot of unhandled close events
Summary: [VDSM] in case the vdsm not up the broker try to reconnect and causes a lot o...
Keywords:
Status: CLOSED DUPLICATE of bug 1525453
Alias: None
Product: vdsm
Classification: oVirt
Component: Bindings-API
Version: 4.20.9.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Irit Goihman
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-28 08:04 UTC by Kobi Hakimi
Modified: 2017-12-28 08:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-28 08:50:53 UTC
oVirt Team: Infra
Embargoed:


Attachments (Terms of Use)
broker log and vdsm log from the problematic host lynx24 (5.46 MB, application/x-tar)
2017-12-28 08:04 UTC, Kobi Hakimi
no flags Details

Description Kobi Hakimi 2017-12-28 08:04:14 UTC
Created attachment 1373106 [details]
broker log and vdsm log from the problematic host lynx24

Description of problem:
[VDSM] in case the vdsm not up the broker try to reconnect and causes a lot of unhandled close events

Version-Release number of selected component (if applicable):
Software Version:4.2.0-0.6.el7
vdsm-4.20.9.3-1.el7ev


How reproducible:
sometimes

Steps to Reproduce:
1. Deploy Hosted engine environment 
2. In the end of GE Builder, we doing a restart to vdsm to all hosts.

Actual results:
The 3rd host was in "Non-Responsive" status with 1 VM in it.

Expected results:
To be able to do a vdsm restart without any problem. 


Additional info:
dan and irit saw this issue

Comment 1 Irit Goihman 2017-12-28 08:44:27 UTC
vdsm version doesn't contain the fix from https://bugzilla.redhat.com/show_bug.cgi?id=1525453

Please try to reproduce after applying the fix - it seems related.

Comment 2 Irit Goihman 2017-12-28 08:50:53 UTC
After further inspection of the logs I see it's the same issue described in the above bug.

*** This bug has been marked as a duplicate of bug 1525453 ***


Note You need to log in before you can comment on or make changes to this bug.