JUJU_HOME never gets initialized ("no public ssh keys found")
Bug #1600307 reported by
Eric Snow
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fake Juju |
Triaged
|
High
|
Unassigned |
Bug Description
fake-juju should always initialize $JUJU_HOME (by calling github.
For instance, InitJujuHome will ensure that $JUJU_HOME has a juju-specific SSH key. If that doesn't happen (and you don't happen to have a generically-named key in $HOME/.ssh) then the environment config will fail to find any keys. In the case of bootstrap that results in a failure with a message of "no public ssh keys found".
InitJujuHome() should be called as the first thing done in handleCommand() (http://
Changed in fake-juju: | |
importance: | Undecided → High |
status: | New → Triaged |
To post a comment you must log in.