[chef] Re: Re: apt package provider: a lot of return code 100 on apt-get

[Daniel DeLeo < >]

You'll have to modify the bootstrap script. Knife supports templates,
including user-defined ones, for bootstrap scripts. So copy the
bootstrap script from the source:

http://github.com/opscode/chef/tree/master/chef/lib/chef/knife/bootstrap/

to ~/.chef/bootstrap/debug.erb and modify it to run chef-client with
`-l debug`. Then run `knife bootstrap` with `-d debug`

HTH,

Dan DeLeo

On Thu, Sep 30, 2010 at 4:34 AM, Ringo De Smet 
<
 >
 wrote:
> On 28 September 2010 15:06, Ringo De Smet 
> <
 >
>  wrote:
>>
>> I just bootstrapped a new set of VMs using 'knife' (0.9.8). When my
>> cookbooks are executed, I get errors on the apt-get command of the
>> package provider. See the following gist for an example:
>>
>> http://gist.github.com/600926
>>
>> If I execute the apt-get command manually, the command succeeds
>> without any problem. At the following chef-client run, the cookbook
>> barfs at the next package. Is there any way to debug why the apt-get
>> lines fail via Chef, but succeed manually?
>
> I have a perfectly reproducible case. Bootstrapping new VMs have
> apt-package install errors just after knife bootstrap. If I restart
> chef-client on these nodes, all apt-get works fine.
>
> I looked in the Knife wiki page, but couldn't find how I can get the
> chef-client configured in debug logging via knife bootstrap. Since the
> problem disappears after chef-client restart, I really want that first
> run in debug logging. Any info on how to do this?
>
> Ringo
>