juju ssh/debug-log fails on local provider when using passphrase protected ssh key

Bug #1233497 reported by Paul Czarkowski
38
This bug affects 6 people
Affects Status Importance Assigned to Milestone
juju-core
Won't Fix
Low
Unassigned

Bug Description

➜ ~ sudo juju bootstrap
➜ ~ juju ssh 0
zsh: correct 'ssh' to '.ssh' [nyae]? n
Permission denied (publickey,password).
error: exit status 255
➜ ~ sudo juju ssh 0
Permission denied (publickey,password).
error: exit status 255

Revision history for this message
Paul Czarkowski (paulcz) wrote :

➜ juju juju version
1.14.1-raring-amd64

Revision history for this message
John A Meinel (jameinel) wrote :

Arguably "juju debug-log" when using the local provider should just tail the file directly, and not try to "juju ssh 0" first.

There is still a bug about not being able to enter your password for "juju ssh".

Changed in juju-core:
importance: Undecided → Low
status: New → Triaged
Curtis Hovey (sinzui)
tags: added: debug-log local-provider ssh
Revision history for this message
Alex Chiang (achiang) wrote :

The tutorial prominently tells users to run "juju debug-log"

https://juju.ubuntu.com/docs/authors-charm-writing.html

Considering the fact that potential charm authors just testing out juju for the first time will probably use a local provider and have a password on their ssh key, I think an importance > Low might be justified here.

It's a fairly annoying papercut to experience when evaluating a brand new toolset.

Changed in juju-core:
milestone: none → 1.18.0
assignee: nobody → Dimiter Naydenov (dimitern)
Changed in juju-core:
assignee: Dimiter Naydenov (dimitern) → nobody
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 1.20.0 → none
Curtis Hovey (sinzui)
Changed in juju-core:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.