r2286 breaks bootstrap with authorized-keys in env.yaml
Bug #1275657 reported by
Curtis Hovey
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Critical
|
Andrew Wilkins |
Bug Description
With juju-core r2286, all tests juju bootstraps that embeds the ssh keys in the yaml using authorized-keys fail. Tests that use authorized-
Related branches
lp:~axwalk/juju-core/lp1275657-default-ssh-identities
- Juju Engineering: Pending requested
-
Diff: 92 lines (+41/-2)3 files modifiedutils/ssh/export_test.go (+1/-0)
utils/ssh/ssh_openssh.go (+25/-2)
utils/ssh/ssh_test.go (+15/-0)
Changed in juju-core: | |
assignee: | nobody → Andrew Wilkins (axwalk) |
milestone: | none → 1.18.0 |
Changed in juju-core: | |
status: | Triaged → In Progress |
Changed in juju-core: | |
milestone: | 1.18.0 → 1.17.3 |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Does the client machine still specify the identity to use in ~/.ssh/config? Maybe -i *does* override that, but not the defaults.