A path naming an instance that does not exist reached the user as
"neither rsync nor scp found on host", because the auto backend
discarded the parse error, skipped rsync, and reported whatever the scp
fallback said. Only a host without scp saw that message; everywhere else
the auto backend built the copy tool without complaint and the real
error surfaced later, from the copy command itself. The explicit rsync
backend reduced the same error to "rsync not available on guest(s)".
The fallback message no longer guesses which tool is missing, since
rsync may well have been found and rejected for another reason.
Signed-off-by: Jan Dubois <jan.dubois@suse.com>
Jan Dubois
dd7558fc3b