Bug 804382 - split brain in RHEVM where vm process recovery failed
Summary: split brain in RHEVM where vm process recovery failed
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Eduardo Warszawski
QA Contact: yeylon@redhat.com
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-18 13:45 UTC by Avihai Shoham
Modified: 2016-04-18 06:44 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-08 15:25:45 UTC
Target Upstream Version:


Attachments (Terms of Use)
VDSM_Log (725.71 KB, application/x-xz)
2012-03-18 13:47 UTC, Avihai Shoham
no flags Details

Description Avihai Shoham 2012-03-18 13:45:12 UTC
my VM ran on host while vdsm restart and recovery flow failed ( recovery file didn't create since hard drive was full)

RHEVM display it as 'Down' and i re-run it.
This cause to VM to run on two hosts.

vmId = 2d3ff57d-b8ed-4402-90ee-a0b8d3a97d48

hosts:
	nott-vdsb (run time 2-23:40:02) vdsId = 130b0f06-cdae-11e0-995a-00145e832c40
	nott-vds4 (run time 20-04:06:32) vdsId = 1128d414-c824-11e0-8d7c-00145e832c40

Comment 1 Avihai Shoham 2012-03-18 13:47:09 UTC
Created attachment 570889 [details]
VDSM_Log

Comment 3 Eduardo Warszawski 2012-04-30 09:15:48 UTC
From the attached log the 2d3ff57d-b8ed-4402-90ee-a0b8d3a97d48 VM was not running after the VDSM restart.
There are no traces of this VM running after the VDSM reset in the log.
Therefore, why split brain?
Please reproduce and put the logs of the two hosts.


From the provided log:
MainThread::INFO::2012-03-13 15:23:16,679::vdsm::71::vds::(run) I am the actual vdsm 4.9-112.6
<snip>
clientIFinit::DEBUG::2012-03-13 15:23:20,606::clientIF::1005::vds::(_cleanOldFiles) removing old file 2d3ff57d-b8ed-4402-90ee-a0b8d3a97d48.recovery

The last one runs only if up to libvirt such VM is not running.

Comment 4 Dan Kenigsberg 2012-05-08 15:25:45 UTC
Lacking needed information and time to deliberate on this, I have to close the bug. I'm not convinced it is real.


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