- From: Ringo De Smet <
>
- To:
- Subject: [chef] Re: apt package provider: a lot of return code 100 on apt-get
- Date: Thu, 30 Sep 2010 13:34:41 +0200
- 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; b=dSeXHmMuFePEeIrtZI/ZmrilxV2HGXNuU6eQPBJKLzghwylLxHeHJqseCc7miaRtqA WEBBaWCFXsn7zrlw10hKZ2ztDn1X295yPikRMcwTJlGA8iTzxtNqZMLndVyvcJd7uyLV Zmcos62puXMcp+OIQnOw9hc2BXAxFNd+x4iX4=
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
Archive powered by MHonArc 2.6.16.