Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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 3Eduardo 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.