[openstack-dev] Nodepool: puppet puts wrong key in authorized_keys in slave

Eduard Matei eduard.matei at cloudfounders.com
Sat May 30 07:26:25 UTC 2015


Hi,

Recently i updated nodepool and the devstack where it's supposed to create
slaves.
After some minor issues i managed to get it running, and it is able to
create an image and i can login to an instance created from that image
using user "ubuntu" (image is trusty).

While trying to add the slave to jenkins it fails with ssh error.
After a little debugging i found that in the authorized_keys of user ubuntu
is the correct key (so i can ssh as user ubuntu) - the one i put in the
Key-pair, but for user jenkins there is another key which i can't find for
any user in the jenkins master.

The authorized_keys for user jenkins contains:
# HEADER: This file was autogenerated at 2015-05-29 12:35:49 +0000
# HEADER: by puppet.  While it can still be managed manually, it
# HEADER: is definitely not recommended.
... then the key... and at the end: jenkins-master-2014-04-24

While for user ubuntu:
... the key from user jenkins on the master... and at the
end: jenkins at jenkins-cinderci

I didn't make any changes to nodepool.yaml or the keys themselves.

I've been looking inside nodepool's scripts, but this looks like a puppet
script and i don't know how to debug those.

Thanks,

Eduard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150530/02a3e2e8/attachment.html>


More information about the OpenStack-dev mailing list