Bug 1337203 - VM is running on more than one Hypervisor after network outage
Summary: VM is running on more than one Hypervisor after network outage
Keywords:
Status: CLOSED DUPLICATE of bug 1342388
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.6.5
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: ---
: ---
Assignee: Arik
QA Contact: Nisim Simsolo
URL:
Whiteboard:
Depends On: 1339291
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-18 13:32 UTC by Alexandros Gkesos
Modified: 2019-11-14 08:06 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-13 22:02:13 UTC
oVirt Team: Virt
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1339291 0 high CLOSED VM split brain during networking issues 2021-02-22 00:41:40 UTC
Red Hat Knowledge Base (Solution) 2356491 0 None None None 2016-06-08 07:22:02 UTC

Internal Links: 1339291

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 ***
Note You need to log in before you can comment on or make changes to this bug.