Auto-init build fail with non-zero exit status 127

[o-smirnov]

Discussed in #49

^{Originally posted by rstofi November 18, 2022}
I've tried to --auto-init from local to a remote machine, but I got the following error message:

radiopadre.client: ssh virtualenv -p python3 /home/krozgonyi/.radiopadre/venv failed with exit code 127
Traceback (most recent call last):
...
subprocess.CalledProcessError: Command '['ssh', '-t', '-t', '-o', 'ControlPath=/tmp/ssh_mux_radiopadre_%C', '-o', 'ControlMaster=auto', '-o', 'ControlPersist=1h', 'glowhpc', 'virtualenv -p python3 /home/krozgonyi/.radiopadre/venv']' returned non-zero exit status 127.

A working solution is simply to create the virtualenv on the remote via

virtualenv -p python3 /path_to_home/.radiopadre/venv

after this --auto-init works as expected.

[o-smirnov]

I suspect the --remote-login-shell option needs to be applied to all commands (at the moment it's only applied to the final run-radiopadre command, but not to the "maintenance" commands before that). It may be the case that virtualenv on the remote end is only available to a login shell. I'll modify stuff accordingly.

[o-smirnov]

@rstofi could please test with this new version? It should invoke the login shell (assuming remote_login_shell is set in the config) when creating the virtualenv, hopefully it's a little more seamless now.