| 2014-10-30 16:12:25 |
Aaron Bentley |
bug |
|
|
added bug |
| 2014-10-30 16:14:07 |
Aaron Bentley |
summary |
Cannot set user for juju scp |
Extremely hard to set user for juju scp |
|
| 2014-10-30 16:15:45 |
Aaron Bentley |
description |
The scp command uses a user@hostname format to allow the user to be specified, as does ssh.
The juju versions of these commands do not accept this format:
$ juju scp buildvars.json jenkins@jenkins/0:
ERROR exit status 1 (cp: cannot create regular file ‘ubuntu@jennkins@jenkins/0:’: No such file or directory)
With ssh, the -l parameter can be used instead, but scp does not accept -l. scp accepts -o, but only before the file list, and "juju scp" interprets -o before the file list as a "juju scp" option, not an "scp" option:
$ juju scp -o User=jenkins buildvars.json jenkins/0:
error: flag provided but not defined: -o
So there is no way to specify a user for juju scp. |
The scp command uses a user@hostname format to allow the user to be specified, as does ssh.
The juju versions of these commands do not accept this format:
$ juju scp buildvars.json jenkins@jenkins/0:
ERROR exit status 1 (cp: cannot create regular file ‘ubuntu@jennkins@jenkins/0:’: No such file or directory)
With ssh, the -l parameter can be used instead, but scp does not accept -l. scp accepts -o, but only before the file list, and "juju scp" interprets -o before the file list as a "juju scp" option, not an "scp" option:
$ juju scp -o User=jenkins buildvars.json jenkins/0:
error: flag provided but not defined: -o
The magic invocation is:
$ juju scp -- -o User=jenkins buildvars.json jenkins/0:
This is counter-intuitive, because -- should mean that juju passes "jenkins/0:" to scp verbatim. |
|
| 2014-10-30 16:16:07 |
Aaron Bentley |
juju-core: importance |
Medium |
Low |
|
| 2014-10-30 16:23:26 |
Aaron Bentley |
description |
The scp command uses a user@hostname format to allow the user to be specified, as does ssh.
The juju versions of these commands do not accept this format:
$ juju scp buildvars.json jenkins@jenkins/0:
ERROR exit status 1 (cp: cannot create regular file ‘ubuntu@jennkins@jenkins/0:’: No such file or directory)
With ssh, the -l parameter can be used instead, but scp does not accept -l. scp accepts -o, but only before the file list, and "juju scp" interprets -o before the file list as a "juju scp" option, not an "scp" option:
$ juju scp -o User=jenkins buildvars.json jenkins/0:
error: flag provided but not defined: -o
The magic invocation is:
$ juju scp -- -o User=jenkins buildvars.json jenkins/0:
This is counter-intuitive, because -- should mean that juju passes "jenkins/0:" to scp verbatim. |
The scp command uses a user@hostname format to allow the user to be specified, as does ssh.
The juju versions of these commands do not accept this format:
$ juju scp buildvars.json jenkins@jenkins/0:
ERROR exit status 1 (cp: cannot create regular file ‘ubuntu@jennkins@jenkins/0:’: No such file or directory)
With ssh, the -l parameter can be used instead, but scp does not accept -l. scp accepts -o, but only before the file list, and "juju scp" interprets -o before the file list as a "juju scp" option, not an "scp" option:
$ juju scp -o User=jenkins buildvars.json jenkins/0:
error: flag provided but not defined: -o
This invocation is accepted:
$ juju scp -- -o User=jenkins buildvars.json jenkins/0:
But the user is still set to "ubuntu", even though normal scp honours "-o User=jenkins" |
|
| 2014-10-30 16:23:31 |
Aaron Bentley |
juju-core: importance |
Low |
Medium |
|
| 2014-10-30 16:24:39 |
Aaron Bentley |
description |
The scp command uses a user@hostname format to allow the user to be specified, as does ssh.
The juju versions of these commands do not accept this format:
$ juju scp buildvars.json jenkins@jenkins/0:
ERROR exit status 1 (cp: cannot create regular file ‘ubuntu@jennkins@jenkins/0:’: No such file or directory)
With ssh, the -l parameter can be used instead, but scp does not accept -l. scp accepts -o, but only before the file list, and "juju scp" interprets -o before the file list as a "juju scp" option, not an "scp" option:
$ juju scp -o User=jenkins buildvars.json jenkins/0:
error: flag provided but not defined: -o
This invocation is accepted:
$ juju scp -- -o User=jenkins buildvars.json jenkins/0:
But the user is still set to "ubuntu", even though normal scp honours "-o User=jenkins" |
The scp command uses a user@hostname format to allow the user to be specified, as does ssh.
The juju versions of these commands do not accept this format:
$ juju scp buildvars.json jenkins@jenkins/0:
ERROR exit status 1 (cp: cannot create regular file ‘ubuntu@jennkins@jenkins/0:’: No such file or directory)
With ssh, the -l parameter can be used instead, but scp does not accept -l. scp accepts -o, but only before the file list, and "juju scp" interprets -o before the file list as a "juju scp" option, not an "scp" option:
$ juju scp -o User=jenkins buildvars.json jenkins/0:
error: flag provided but not defined: -o
This invocation is accepted:
$ juju scp -- -o User=jenkins buildvars.json jenkins/0:
But the user is still set to "ubuntu", even though normal scp honours "-o User=jenkins". It is also counter-intuitive, because -- should mean that juju passes "jenkins/0:" to scp verbatim. |
|
| 2014-10-30 16:24:59 |
Aaron Bentley |
summary |
Extremely hard to set user for juju scp |
Cannot set user for juju scp |
|
| 2014-10-31 00:05:36 |
Ian Booth |
juju-core: milestone |
|
1.21 |
|
| 2014-10-31 07:28:52 |
Andrew Wilkins |
juju-core: status |
Triaged |
In Progress |
|
| 2014-10-31 07:28:53 |
Andrew Wilkins |
juju-core: assignee |
|
Andrew Wilkins (axwalk) |
|
| 2014-10-31 12:29:11 |
Ian Booth |
juju-core: milestone |
1.21 |
1.21-alpha3 |
|
| 2014-10-31 12:29:16 |
Andrew Wilkins |
juju-core: status |
In Progress |
Fix Committed |
|
| 2014-11-04 15:35:30 |
Curtis Hovey |
juju-core: status |
Fix Committed |
Fix Released |
|
