- From: Ted <
- To: "
- Subject: [chef] Re: Re: Re: ERROR: No socketless chef-zero server
- Date: Tue, 19 May 2015 07:17:04 +1000
- Domainkey-signature: a=rsa-sha1; c=nofws; d=pobox.com; h=subject :references:from:content-type:in-reply-to:message-id:date:to :content-transfer-encoding:mime-version; q=dns; s=sasl; b=QZRcmJ xEPsQVQzrkQwmcz73qId039W2uA1B6FitDlIqi7MzXOgdwdUifk20FXpKpyPUFpP zlFveFIHzi4JI2GwTzAoWtt+vHTMTYQTA2r6vH/4jQvTajzP9mjAu27v9nzr2yYU GNV5Za827u179C0LVJ/3sP2qXXVrDD1YWplVc=
> On 19 May 2015, at 04:24, Daniel DeLeo
>> On Monday, May 18, 2015 at 12:17 AM, Ted B wrote:
>> I’m having the same issue - but I’m using chef-provisioning for bootstrap.
>> It only fails when the chef zero socketless mode is tried to be used by
>> the client on each node.
>> Using chefDK 0.6.0 and client 12.3 as well.
> This is an incompatibility between Chef 12.3 and Chef Provisioning 1.1.1. A
> fix has been committed for this and will be released in the next version of
> Chef Provisioning.
Is this the issue tracking this?
Archive powered by MHonArc 2.6.16.