Bug 1529458

Summary: [VDSM] in case the vdsm not up the broker try to reconnect and causes a lot of unhandled close events
Product: [oVirt] vdsm Reporter: Kobi Hakimi <khakimi>
Component: Bindings-APIAssignee: Irit Goihman <igoihman>
Status: CLOSED DUPLICATE QA Contact: Raz Tamir <ratamir>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.20.9.3CC: bugs, igoihman, mperina
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-28 08:50:53 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:
Attachments:
Description Flags
broker log and vdsm log from the problematic host lynx24 none

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 ***