Description of problem: Hi guys. With 'migrateuri' in use, generated URI contains an extra, redundant white-space. eg. -> $ pcs resource update node1 attr migrateuri=?no_verify=1 results in (with some more attr set) virsh --connect=qemu:///system --quiet migrate --live --unsafe node1 qemu+tls://dzien.direct/system ?no_verify=1 and it should be, or what I would expect: virsh --connect=qemu:///system --quiet migrate --live --unsafe node1 qemu+tls://dzien.direct/system?no_verify=1 Version-Release number of selected component (if applicable): resource-agents-4.10.0-36.el9.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
migrateuri is added to the command line as a separate token separated by a space: https://github.com/ClusterLabs/resource-agents/blame/v4.10.0/heartbeat/VirtualDomain#L1013 The virsh(1) man page suggests that the migrateuri is supposed to be a full URI, starting with a prefix. So it should be able to stand on its own after the space. See also: https://libvirt.org/migration.html#migration-using-only-unix-sockets "?no_verify=1" looks like an incomplete URI.
Perhaps what you want is to set remoteuri (to something like remoteuri='qemu+tls://%n/system?no_verify=1' -- I haven't tried that yet so it may need tweaking).
Yes, it does the trick. btw. something like cluster_map similar or identical to what for eg. ocf_heartbeat_galera has would really do the trick - perhaps an enhancement in the future.
So, not a bug.