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.

This is documentation bug.

Documentation for live-migration of the nodes in the pacemaker cluster is close
to non-existant not only on our (redhat) pages but altogether everywhere. 

The problem you would have trouble find documentation for:

  * how do I set-up live migration of virtual domains in the cluster
  * how do I test that it works
  * how do I setup pacemaker resource agent VirtualDomain to allow
     live migration of the guest?

I believe at least third option should be documented in our knowledgebase along
with the fact that live migration of virtual domains that are remote node in
the cluster is not supported.

It requires allow-migrate=true, and setting SSH as transport makes it easier to setup (instead of SSL certificates):
# pcs resource create VM VirtualDomain config=/etc/libvirt/qemu/vm.xml migration_transport=ssh meta allow-migrate=true

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