Replaying the bad command with the raw command does not reproduce the error. ssh just works for me, juju does not. I imagine juju and ssh just works for you. I issued these commands in the same terminal in quick succession and only juju reports a problem.
$ ssh -l ubuntu -t -o "StrictHostKeyChecking no" -o "PasswordAuthentication no" 10.55.32.60
ubuntu@juju-staging-machine-3:~$ ls /bogus
ls: cannot access /bogus: No such file or directory
ubuntu@juju-staging-machine-3:~$ logout
Connection to 10.55.32.60 closed.
ubuntu@juju-staging-machine-3:~$ ls /bogus
ls: cannot access /bogus: No such file or directory
ubuntu@juju-staging-machine-3:~$ logout
Connection to 10.55.32.60 closed.
ERROR exit status 2
Thank you for looking into this John.
Replaying the bad command with the raw command does not reproduce the error. ssh just works for me, juju does not. I imagine juju and ssh just works for you. I issued these commands in the same terminal in quick succession and only juju reports a problem.
$ ssh -l ubuntu -t -o "StrictHostKeyC hecking no" -o "PasswordAuthen tication no" 10.55.32.60 juju-staging- machine- 3:~$ ls /bogus juju-staging- machine- 3:~$ logout
ubuntu@
ls: cannot access /bogus: No such file or directory
ubuntu@
Connection to 10.55.32.60 closed.
ubuntu@ juju-staging- machine- 3:~$ ls /bogus juju-staging- machine- 3:~$ logout
ls: cannot access /bogus: No such file or directory
ubuntu@
Connection to 10.55.32.60 closed.
ERROR exit status 2