Open ahgittin opened 10 years ago
I tried to reproduce this with the tests in JcloudsLoginLiveTest
(e.g. testSpecifyingNothingAndNoDefaultKeyFilesExist
). That worked fine.
It did give the log.warn about invalid files for privateKeyFile because the defaults couldn't be found, but then it went on to auto-generate a random password.
Is your machine sshable with a password, or is that forbidden by default in the sshd_config perhaps?
(Note that we also call jclouds AdminAccess.lockSsh(false)
when using password. Without that, jclouds would have written to /etc/ssh/sshd_config
to add PasswordAuthentication no
and PermitRootLogin no
.)
An alternative within brooklyn is that we could auto-generate an rsa key to use, rather than falling back to an auto-generated password. (this is not currently supported, but could be implemented - thoughts?)
i was using AWS with no special image selection or anything else. perhaps it does have passwords disabled? (likely the people who reported it to me were doing the same?)
+1 to generating an rsa key as the fallback
cloud machine creation fails if
~/.ssh/id_rsa
(orid_dsa
or otherprivate-key-file
is not set)if no
getConfigRaw
indicates no key is set (it was using the default) then brooklyn should just make up a key -- rather than failyou will see warnings such as this as soon as the problem manifests (after a minute or two in AWS and GCE):
then much later: