[chef] Re: Re: Re: Re: Supervisor missing templates

[AJ Christensen < >]

The stack-trace in OP is not a template resource.

"Supervisor service job_activity_search cannot be restarted because it
does not exist"

Perhaps :create needs to be called before :enable/:restart. I'm not
familiar with the supervisor cookbook.

111:     action [:enable, :restart]

One might anticipate :enable to call :create, but  would have to dig
into the supervisor (L|H)WRP itself, to find out!

Cheers,

AJ

On Tue, Jul 22, 2014 at 2:30 PM, Ben Bytheway 
<
 >
 wrote:
> Yes, the chef run fails with an error that the template cannot be found, 
> even when specifying the cookbook where the template is located in the 
> resource call.
>
>> On Jul 21, 2014, at 8:09 PM, Daniel DeLeo 
>> <
 >
>>  wrote:
>>
>>> On Monday, July 21, 2014 at 6:59 PM, Ben Bytheway wrote:
>>> I have also seen this behavior, but haven't gotten to the bottom of it. 
>>> If I knife download my cookbook, the template is there, but chef-client 
>>> doesn't get it. Isn't in /var/chef/cache at all.
>>
>>
>> Templates are downloaded on demand, as they are used by resources. If you 
>> never use them, then chef doesn’t download them. If I remember correctly, 
>> there might also be a small bug where templates that are used can be 
>> removed at the end of a chef-client run (but they’re downloaded the next 
>> time so it’s just wasting a bit of IO). Have you seen a cookbook fail to 
>> execute for this reason?
>>
>> Also, if you just don’t like this behavior, you can configure 
>> `no_lazy_load true` to make chef-client fetch all templates (and cookbook 
>> files, which have the same behavior) eagerly.
>>
>> FWIW, eager load will be the default in Chef 12 since the URLs to fetch 
>> the files are time-limited and on long chef-client runs (an hour or more), 
>> the URLs expire and cause errors.
>>
>> --
>> Daniel DeLeo
>>