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.

Created attachment 486882 [details]
vdsm source and destenation logs

Description of problem:

during scale testing, *failed migration of a vm to destination host that runs 90 vms, finish with split brain. 

* Failed migration - libvirt daemon was restarted during that operation on source host. 

Flow: 

- destination host runs 90 vms 
- call migrate on source - migration starts
- 5-10 seconds later - /etc/init.d/libivrtd restart 
- connection to libvirt is broken - vdsm takes it self down 
- on destination server, call destroy is initiated, but fails due to operation time-out, vm runs on destination server in paused state.
- on source server, vdsm performs vm recovery, and runs the vm. 

result: split brain. 

vdsClient -s 0 list table:

destination host:
4afaa2bb-d570-4ae4-964a-f19507ca786b  73182  FC-0-30              Paused*

source host:
4afaa2bb-d570-4ae4-964a-f19507ca786b  79552  FC-0-30              Up


Versions:
-vdsm-4.9-55.el6.x86_64
-libvirt-0.8.7-13.el6.x86_64

attached source and destination vdsm logs.

Come to think of it, we reflect the state that libvirt reports as of bug 690175, so there's nothing we can do about it here.

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