juju should provide more useful error when no ssh keys avaliable

Bug #1004937 reported by Dave Walker
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
pyjuju
Triaged
Low
Unassigned

Bug Description

Currently, if no ~/.ssh/id_* is available, juju provides output similar to:

$ juju bootstrap
2011-09-28 08:24:04,511 INFO Bootstrapping environment 'sample' (type: ec2)...
SSH authorized/public key not found.
2011-09-28 08:24:05,063 ERROR SSH authorized/public key not found.

This error could be more useful, suggesting the next steps to create a key.

As reported, https://answers.launchpad.net/ubuntu/+source/ensemble/+question/172588 .. and a user questioning this with me today.

Thanks :)

Changed in juju:
status: New → Triaged
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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