If that was the issue, it's now fixed in lucid/1.6.2.
Please reopen if this can be triggered /without/ creating two times the same
key.
** Changed in: eucalyptus (Ubuntu)
Status: Incomplete => Fix Released
--
SSH key stopped working
https://bugs.launchpad.net/bugs/514198
You received thi
Quite possible, the students are instructed to create a key called
'mykey' in the exercise. With this the problem can be reproduced:
$ euca-add-keypair mykey2 > mykey2.priv
$ euca-add-keypair mykey2 > mykey2.priv
$ euca-run-instances -t c1.medium -k mykey2 emi-DF481077
$ ssh -i mykey2.priv 172.24.
Apparently there /was/ a known issue in eucalyptus 1.6 where if someone
was to create the same key twice, eucalyptus would end up having a
private key that no longer matches the public key. Could that be what
happened here ?
--
SSH key stopped working
https://bugs.launchpad.net/bugs/514198
You re
The sshd is started, the last few lines from euca-get-console-output:
ec2:
ec2: #
ec2: -BEGIN SSH HOST KEY FINGERPRINTS-
ec2: 2048 c5:e6:f6:21:16:bf:b4:d8:00:fa:1b:ad:29:12:86:de
/etc/ssh/ssh_host_rsa_key.pub (RSA)
ec2: 1024 b9
On Fri, Jan 29, 2010 at 08:28:42PM -, Torsten Spindler wrote:
> On Fri, 2010-01-29 at 19:26 +, Dustin Kirkland wrote:
> ...
> > Or, rather, did they create and use instances with that key, and then
> > later, create instances but not be able to use that key?
>
> This I meant with stopped w
On Fri, 2010-01-29 at 19:26 +, Dustin Kirkland wrote:
...
> Or, rather, did they create and use instances with that key, and then
> later, create instances but not be able to use that key?
This I meant with stopped working.
--
SSH key stopped working
https://bugs.launchpad.net/bugs/514198
Yo
Each student should be able to create and use a key called "mykey" as
long as they're unique users with unique keys on a give machine (or
separate machines).
What do you mean by "stopped working"?
Did the user have a running instance that they were able to login with
that key, and then later, cou
