Bug 1337203

Summary: VM is running on more than one Hypervisor after network outage
Product: Red Hat Enterprise Virtualization Manager Reporter: Alexandros Gkesos <agkesos>
Component: ovirt-engineAssignee: Arik <ahadas>
Status: CLOSED DUPLICATE QA Contact: Nisim Simsolo <nsimsolo>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 3.6.5CC: agkesos, ahadas, dfediuck, gklein, inetkach, jentrena, lsurette, michal.skrivanek, mkalinin, mtessun, nsimsolo, obockows, ppostler, rbalakri, Rhev-m-bugs, srevivo, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-13 22:02:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1339291    
Bug Blocks:    

Comment 3 Michal Skrivanek 2016-05-29 18:44:22 UTC 
Please attach logs
Comment 6 Arik 2016-05-31 07:21:34 UTC 
Please also attach VDSM log from buffet.corp.tele2.com in the relevant time (in engine's time it is 2016-05-12 01:48:18,984 and there should be 2fa2c7e3 appearing there)
Comment 7 Alexandros Gkesos 2016-06-01 14:17:11 UTC 
Hello Arik,

Unfortunately the vdsm logs had been rotated

$ xzgrep 2fa2c7e3 vdsm.log* | wc -l
0

oldest log
VM Channels Listener::DEBUG::2016-05-12 11:01:01,556::vmchannels::96::vds::(_handle_timeouts) Timeout on fileno 78.

Do you think you can get anything else from the existing logs?
I talked with Roman Hodain and he explained to me that even we/you had the vdsm logs, still they are not enough and there will be further logging in 3.6.7

Thank you,
Alexandros
Comment 8 Arik 2016-06-13 22:02:13 UTC 

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