Juju uses user known hosts file
Bug #1659385 reported by
Nicholas Skaggs
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-ci-tools |
Triaged
|
High
|
Unassigned | ||
Bug Description
Juju will use ~/.ssh/known_hosts when it doesn't have information on key matching for new machines. This causes our tests to log "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!" warnings on initial connection. The connections will continue to fail until the controller recieves correct information from the agent. At this point the connection is achieved.
Juju 1.X does not use a temporary known hosts file, and thus will pollute our ~/.ssh/known_hosts. Juju 2.x only recently acquired this ability.
We should clear all current known_hosts files, and ensure they stay pure during runs.
| Changed in juju-ci-tools: | |
| status: | New → Triaged |
| importance: | Undecided → High |
Revision history for this message
| Nicholas Skaggs (nskaggs) wrote | #1 |
Revision history for this message
| Nicholas Skaggs (nskaggs) wrote | #2 |
Revision history for this message
| Nicholas Skaggs (nskaggs) wrote | #3 |
To post a comment you must log in.
Note, just deleting the files can cause us issues with our CI.