Received disconnect from ...: 2: Too many authentication failures for ubuntu
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
Medium
|
Eric Snow | ||
| 1.23 |
Fix Released
|
Medium
|
Eric Snow | ||
| 1.24 |
Fix Released
|
High
|
Unassigned | ||
Bug Description
Trying to bootstrap on AWS, I ran into the following (after adding some logging):
Waiting for address
Attempting to connect to 172.31.4.197:22
Attempting to connect to 54.84.161.203:22
ssh: connect to host 54.84.161.203 port 22: Connection refused
ssh: connect to host 54.84.161.203 port 22: Connection refused
ssh: connect to host 54.84.161.203 port 22: Connection refused
ssh: connect to host 54.84.161.203 port 22: Connection refused
Warning: Permanently added '54.84.161.203' (ECDSA) to the list of known hosts.
Received disconnect from 54.84.161.203: 2: Too many authentication failures for ubuntu
Received disconnect from 54.84.161.203: 2: Too many authentication failures for ubuntu
Received disconnect from 54.84.161.203: 2: Too many authentication failures for ubuntu
...
I happen to have several identity files loaded and presumably bootstrap tries to authenticate using them before trying the Juju client SSH key. Apparently that is too many keys, thus the error.
Bootstrap should be using the "-o 'IdentitiesOnly yes'" option at the commandline.
| Eric Snow (ericsnowcurrently) wrote | #1 |
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| assignee: | nobody → Eric Snow (ericsnowcurrently) |
| milestone: | none → 1.25.0 |
| milestone: | 1.25.0 → none |
| status: | Triaged → In Progress |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| milestone: | none → 1.25.0 |
| status: | Fix Committed → Fix Released |
| Katherine Cox-Buday (cox-katherine-e) wrote | #2 |
Here's a fix: http://