"juju ssh" adds an additional strings to all commands when used on Windows, in interactive mode
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Martin Packman | ||
2.0 |
Fix Released
|
High
|
Martin Packman | ||
2.1 |
Fix Released
|
High
|
Martin Packman | ||
juju-core |
Won't Fix
|
Undecided
|
Unassigned | ||
1.25 |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
When used on Windows, juju ssh (interactive) adds additional strings to the ssh commands. As a consequence, every ssh command fails with command not found.
juju bootstrap still works, as the commands are given in a way that this bug does not affect them. Furthermore, if I add blank spaces before and after the command, the command partially works.
Example:
PS C:\Users\user> .\juju.exe ssh 0
Welcome to Ubuntu 14.04.2 LTS (GNU/Linux 3.13.0-55-generic x86_64)
* Documentation: https:/
System information as of Thu Jun 25 12:07:06 UTC 2015
System load: 0.06 Processes: 251
Usage of /: 17.8% of 15.62GB Users logged in: 0
Memory usage: 5% IP address for eth0: 192.168.1.101
Swap usage: 0%
Graph this data and manage this system at:
https:/
-bash: line 1: $'\r': command not found
-bash: line 41: $'\r': command not found <<<----- when I press Enter
ls
-bash: line 42: $'ls\r': command not found
ls .. <<<---- when I add spaces after and before the "ls .." command
..:
ubuntu
: No such file or directory
Tested with juju-1.24, juju-1.25-alpha1 on Windows 8.1.
tags: | added: ssh windows |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 1.25.0 |
Changed in juju-core: | |
milestone: | 1.25.0 → 1.25.1 |
Changed in juju-core: | |
milestone: | 1.25.1 → 1.25.2 |
Changed in juju-core: | |
milestone: | 1.25.2 → 1.25.3 |
Changed in juju-core: | |
milestone: | 1.25.3 → 1.25.4 |
Changed in juju-core: | |
milestone: | 1.25.4 → 1.25.5 |
Changed in juju-core: | |
milestone: | 1.25.5 → 1.25.6 |
Changed in juju-core: | |
milestone: | 1.25.6 → 1.25.7 |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.0-beta18 |
Changed in juju-core: | |
status: | Triaged → Won't Fix |
milestone: | 1.25.7 → none |
Changed in juju: | |
milestone: | 2.0-beta18 → 2.0-beta19 |
Changed in juju: | |
milestone: | 2.0-beta19 → 2.0-rc1 |
Changed in juju: | |
milestone: | 2.0-rc1 → 2.0.1 |
Changed in juju: | |
assignee: | nobody → Richard Harding (rharding) |
Changed in juju: | |
milestone: | 2.0.1 → 2.0.2 |
Changed in juju: | |
assignee: | Richard Harding (rharding) → Martin Packman (gz) |
status: | Triaged → In Progress |
Changed in juju: | |
milestone: | 2.0.2 → 2.0.3 |
Changed in juju: | |
status: | In Progress → Fix Committed |
milestone: | 2.0.3 → 2.2.0-alpha1 |
Changed in juju-core: | |
milestone: | none → 1.25.11 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Changed in juju-core: | |
importance: | Critical → Undecided |
milestone: | 1.25.11 → none |
So, this is still happening and is clearly a dos vs unix line endings problem. This is a big problem for any dev using Windows... Any timeframe for a fix or a workaround?