VirtualDomain , live migration , if no config- problem.

Hello!

We use gluster as VM shared storage using gfapi and as domain definition (xml files) storage , mounted.
Problem here is that sometimes for some reason config files may not be mounted, but, because libvirt uses gfapi, VM's storage is available.
So, if we move VM to node , where there is no config directory mounted, then VM will be moved, but pacemaker can't monitor it, so it can be started twice and VM storage will be damaged.

Is it possible to add config presence check in pacemaker before doing live migration?

Thank you!

No file, test, or entry point is identified. Start by locating the Pacemaker resource agent responsible for VirtualDomain and review how live migration and monitoring are handled. Done means the agent checks for the required configuration on the destination before migration and has coverage for the missing-mount case.

Written by the indexing model from the issue text.