- From: Grig Gheorghiu <
>
- To:
- Subject: [chef] Re: Re: Re: Adding a recipe to an existing role in chef-server
- Date: Wed, 26 Jan 2011 15:41:43 -0800
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=Vkhtr3gbqFnaU/siHsLh8EEQbZl5hoVemiVNKX3eu9kNHjFM8paTTTdv5jJAjxHh7M OEw8zfq7oVGt7k2A60V2b+RFpjq6sECR9zHEOvUXdrl+Rv8cqHFIY6DgJk9CjdVFXmUu 1B7fLq2447lFSDUKvHCQNlEAxOdgAs+tjxEVU=
Can you run your chef client with debug logging and see what the log
file tells you? Something like
chef-client -j /etc/chef/chef.json -L /var/log/chef-debug.log -l debug
On Wed, Jan 26, 2011 at 3:16 PM, Ben Marini
<
>
wrote:
>
I did that, and verified that the role is updated on my chef server. Still
>
though, my client isn't picking it up.
>
>
On 1/26/11 3:13 PM, "Grig Gheorghiu"
>
<
>
>
wrote:
>
>
>On Wed, Jan 26, 2011 at 3:07 PM,
>
><
>
>
> wrote:
>
>> My chef client node has an "app" role in it's run_list, that has
>
>>already run on
>
>> my node. Let's say it that the app role has two recipes in it's
>
>>run_list:
>
>> "nginx" and "varnish". I update my my app role on my chef server, so
>
>>that it
>
>> now has three recipes: "nginx", "varnish", and "git". When I run `sudo
>
>> chef-client` on my node, it doesn't pick up on the fact that the app
>
>>role has
>
>> changed, and run the new "git" recipe...has anyone else has this
>
>>problem? Is
>
>> this by design or am I doing something wrong?
>
>>
>
>
>
>You need to also update the role via knife on the chef server:
>
>
>
>$ knife role from file roles/myrole.rb
>
>$ knife role show myrole
>
>
>
>Grig
>
>
Archive powered by MHonArc 2.6.16.