- From: Joshua Sierles <joshua@37signals.com>
- To: chef@lists.opscode.com
- Subject: Re: chef + vlad/capistrano?
- Date: Tue, 10 Mar 2009 18:48:44 +0100
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:from:to:in-reply-to:content-type:mime-version :subject:date:references:x-mailer; b=r9o+aRUWC7ZwqmM4d18qZ+IhYCgunGvX5snOPki1V24xQken7zh2AsUjLwX9u+ZqaU 1JGBFKFCG59QJvLbgwXA+LHJ+txg5daplhh5923ET8iqjcO7mUFFqB4HDdZ3m7qPFTNz cDxb1WCDKjkrFhkC+ljk5z3zByW/AaDe8gASQ=
It looks like the problem is with the node name itself. It took us
at least an hour, but when we do:
chef-client -j dna.json -n foonode
it works perfectly.
Another way to avoid this sort of problem is to set the hostname
before using the client. We calculate the desired hostname first (like
something-app-05) and assign it using a chef recipe and chef-solo.
Then when you run the client, it will use the new hostname rather than
the EC2-assigned one.
Joshua Sierles
37signals
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
Archive powered by MHonArc 2.6.16.