tutorial should ensure people don't see 'ssh authorized/public key not found' errors.

Bug #819019 reported by Robert Collins
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
pyjuju
Triaged
Low
Unassigned

Bug Description

I have a freshly installed machine, grabbed ensemble, and following the user tutorial; ensemble bootstrap errors with
SSH authorized/public key not found.

This may be a doc issue, or something else - I don't know enough to say :)

Revision history for this message
Thomas Risberg (trisberg-7) wrote :

I'm seeing the same error. Any workaround for getting the bootstrap done?

Revision history for this message
Thomas Risberg (trisberg-7) wrote :

Since this was a fresh install there were no keys in ~/.ssh so I copied an id_dsa.pub key from another system and got it working. Maybe the tutorial should be updated.

William Reade (fwereade)
summary: - ensemble bootstrap reports 'ssh authorized/public key not found'.
+ tutorial should ensure people don't see 'ssh authorized/public key not
+ found' errors.
Revision history for this message
nutznboltz (nutznboltz-deactivatedaccount) wrote :

Is this a duplicate of Bug #813112 ?

It does seem to be a bogus test; copying any id_dsa.pub into ~/.ssh without regard to that key file's relevance to juju or AWS etc. makes "juju bootstrap" work for me. Got a "SSH authorized/public key not found." error and no running EC2 instance without a dsa pub key file in ~/.ssh/

Revision history for this message
nutznboltz (nutznboltz-deactivatedaccount) wrote :

Hmm, the resulting EC2 instance could not be connected to due to "Invalid SSH key".

Cannot connect to machine i-e6e38d86 (perhaps still initializing): Invalid SSH key
2011-09-27 23:11:39,199 ERROR Cannot connect to machine i-e6e38d86 (perhaps still initializing): Invalid SSH key

I terminated the image and deleted the bucket and security group modifications. Was I just too impatient? Does this thing actually work?

Revision history for this message
Clint Byrum (clint-fewbar) wrote :

Its not related to bug 813112 , no. That was just the fact that the tests required a user to have an ssh key and therefore weren't runnable in isolation.

In this case, you need the both the public and private key file in ~/.ssh. Juju does not check to make sure you actually have the private part, it just copies the public part into the environment.

Getting back to the original bug, this is definitely a deficiency in this document:

https://juju.ubuntu.com/docs/user-tutorial.html

We will need to add a note about setting up SSH keys.

Changed in juju:
status: New → Triaged
importance: Undecided → Low
tags: added: documentation
Revision history for this message
nutznboltz (nutznboltz-deactivatedaccount) wrote :
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.