- From: John Hanks <
>
- To:
- Subject: [chef] Registering client when old client exists.
- Date: Sun, 27 Jun 2010 21:43:19 -0400
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=ngtDK6ZTZTT+E4OKFmOsxNUwPaZjiABytp33zQh5cApwLb/VQMOXvsgK67KMXiuTS4 N05JFmrf57XtdUpQ3OvQ6XaG1yP8xIbefYkPCJsBTFV5Ea53buKBwNn0EoFDnIK1PLxK 519rWSGqRy5o7YoSleWKMhePJH2uaOGXRwjWg=
Hello,
Before upgrading to 0.8.16 when my nodes booted they registered
themselves regardless of whether or not a client with the same name
existed. With my fresh install of 0.8.16, this behavior has changed
and rebooted nodes fail to register because of the existing client. Is
there a way I can select/revert the old behavior? My nodes are
diskless and boot from a common base OS image so while it's trivial to
have a validation.pem on the image, it'd be complicated and kludgy to
work out how to keep track of the client.pem for every client/node
across reboots.
Thanks,
griznog
- [chef] Registering client when old client exists., John Hanks, 06/27/2010
Archive powered by MHonArc 2.6.16.