[chef] Re: Re: Chef DK 0.5.0 RC 1 released

[Torben Knerr < >]

Hey Tyler,

not sure if that would justify a rollback to Ruby 2.0 for the Windows
builds. Can't speak for others whether they are using the BUNDLE_JOBS
setting / downloading gem bundles in parallel.

For me personally, the workaround is sufficient, as I roll out the
windows-based development environments with their own $HOME directory,
so I can easily add the https -> http mirror setting in the
~/.bundle/config.

Not sure how you could fix that in the omnibus installer side, or
whether that should be worked around at all -- maybe documenting that
there might be issues in specific cases along with potential
workarounds would be sufficient in this case.

Well, you could write to ~/.bundle/config during the installation for
sure, but that might be unexpected at least and could conflict with
other mirror settings (like for an internal gem mirror)...

HTH,
Torben


On Mon, Apr 6, 2015 at 9:11 PM, Tyler Ball 
<
 >
 wrote:
> Nevermind, I see that the bug affects windows 2.1 and 2.2 - should have 
> read more before I replied!.  I’ll get started on an RC5 right now that 
> either includes your workaround or rolls back to 2.0 in the Windows builds.
>
> -T
>
>> On Apr 6, 2015, at 2:08 PM, Tyler Ball 
>> <
 >
>>  wrote:
>>
>> Hey Torben - I just released RC4 which pins the Ruby version to 2.1.5 
>> across both Windows and Linux/OSX.  Can you try this latest RC and see if 
>> you still get the same problem?
>>
>> -T
>>
>>> On Apr 4, 2015, at 6:03 AM, Torben Knerr 
>>> <
 >
>>>  wrote:
>>>
>>> If anyone else is running into this: it's likely a Ruby core bug in
>>> some OpenSSL / threading related code:
>>> https://bugs.ruby-lang.org/issues/11033
>>>
>>> Workaround: `bundle config mirror.https://rubygems.org
>>> http://rubygems.org` to bypass HTTPS for bundle-installing gems --
>>> plain HTTP is still working with multiple parallel downloads
>>>
>>>
>>> On Fri, Apr 3, 2015 at 6:23 PM, Torben Knerr 
>>> <
 >
>>>  wrote:
>>>> Quick heads up: exactly the same is happening with a plain Ruby 2.2.1
>>>> installation => nothing ChefDK related and sorry for the false alert
>>>> ;-)
>>>>
>>>> Cheers, Torben
>>>>
>>>> On Fri, Apr 3, 2015 at 3:09 PM, Torben Knerr 
>>>> <
 >
>>>>  wrote:
>>>>> Hi Tylers,
>>>>>
>>>>> with RC2 everything was fine, with RC3 I get some weird issues when
>>>>> installing gems with bundler in parallel (BUNDLE_JOBS=16). I'm testing
>>>>> this on Windows, and it might as well be a Ruby 2.1.5 issue.
>>>>>
>>>>> This is my ~/.bundle/config:
>>>>> ```
>>>>> ---
>>>>> BUNDLE_PATH: ~/.chefdk/gem/ruby/2.1.0
>>>>> BUNDLE_JOBS: 16
>>>>> BUNDLE_RETRY: 3
>>>>> ```
>>>>>
>>>>> Here's the Gemfile I'm using:
>>>>> https://github.com/tknerr/sample-toplevel-cookbook/blob/master/Gemfile
>>>>>
>>>>> This is what I get on `bundle install` with RC3:
>>>>> ```
>>>>> ...
>>>>> Installing sawyer 0.6.0
>>>>> Installing net-ssh-gateway 1.2.0
>>>>> Installing net-scp 1.2.1
>>>>> Installing stove 3.2.3
>>>>>
>>>>> OpenSSL::SSL::SSLError: SSL_read: cert already in hash table
>>>>> Installing rspec-mocks 3.2.1
>>>>> Installing celluloid-io 0.16.2
>>>>> Installing pry 0.10.1
>>>>> Installing highline 1.7.1
>>>>> Installing rspec-core 3.2.2
>>>>> Installing tailor 1.4.1
>>>>> Installing net-ssh-multi 1.2.0
>>>>>
>>>>> OpenSSL::SSL::SSLError: SSL_read: cert already in hash table
>>>>> Installing octokit 3.8.0
>>>>> Installing specinfra 2.28.0
>>>>> Installing ffi 1.9.8
>>>>> An error occurred while installing foodcritic (4.0.0), and Bundler 
>>>>> cannot
>>>>> continue.
>>>>> Make sure that `gem install foodcritic -v '4.0.0'` succeeds before 
>>>>> bundling.
>>>>> ```
>>>>>
>>>>>
>>>>> => The "OpenSSL::SSL::SSLError: SSL_read: cert already in hash table"
>>>>> warnings I did not get with RC2
>>>>> => The error at the end is somehow "transient". After running `bundle
>>>>> install` a few more times (with other gems erroring) I get them
>>>>> finally all installed
>>>>>
>>>>>
>>>>> Once I remove the BUNDLE_JOBS from the bundler config it is working
>>>>> again (but takes certainly longer).
>>>>>
>>>>> Any ideas? Anyone can reproduce this?
>>>>>
>>>>>
>>>>> Cheers,
>>>>> Torben
>>>>>
>>>>> On Thu, Apr 2, 2015 at 6:56 PM, Tyler Ball 
>>>>> <
 >
>>>>>  wrote:
>>>>>> Greetings again!  I just released ChefDK 0.5.0 RC3 - RC2 did a quiet 
>>>>>> release
>>>>>> because it was quite a small change.  But RC3 is not!
>>>>>>
>>>>>> Updated dependencies:
>>>>>>
>>>>>> Chef 12.2.1
>>>>>> chef-provisioning - 1.0.0.rc.2
>>>>>> chef-provisioning-aws - 1.0.0.rc.3
>>>>>> test-kitchen - 1.4.0.rc.1
>>>>>> kitchen-vagrant - 0.17.0.rc.1
>>>>>>
>>>>>>
>>>>>> Ruby has been updated to 2.1.5 on all systems including Windows.  All
>>>>>> Windows users - please try this and let me know if you find issues!
>>>>>>
>>>>>> The links are the same, but here they are again:
>>>>>>
>>>>>> Mac
>>>>>> Ubuntu
>>>>>> Windows
>>>>>>
>>>>>>
>>>>>> Cheers!
>>>>>> -Tyler
>>>>>>
>>>>>> On Mar 27, 2015, at 4:59 PM, Tyler Ball 
>>>>>> <
 >
>>>>>>  wrote:
>>>>>>
>>>>>> Gah, thats totally my fault - its a copy pasta error.
>>>>>>
>>>>>> Test Kitchen is 1.4.0.beta.2 and kitchen-vagrant is 0.17.0.beta.4.
>>>>>>
>>>>>> Thanks for pointing that out!
>>>>>>
>>>>>> -T
>>>>>>
>>>>>> On Mar 27, 2015, at 3:45 PM, Lloyd 
>>>>>> <
 >
>>>>>>  wrote:
>>>>>>
>>>>>> On Fri, Mar 27, 2015 at 11:33 AM, Tyler Ball 
>>>>>> <
 >
>>>>>>  wrote:
>>>>>>>
>>>>>>> Updated dependencies (some bundled with the omnibus build)
>>>>>>>
>>>>>>> Chef - 12.2.0
>>>>>>> chef-provisioning - 0.19
>>>>>>> chef-provisioning-fog - 0.13.1
>>>>>>> chef-provisioning-azure - 0.2.1
>>>>>>> chef-provisioning-aws - 0.5.0
>>>>>>> test-kitchen - 1.4.0
>>>>>>> kitchen-vagrant - 0.17.0
>>>>>>
>>>>>> It would be useful for me if specific versions for each of these were
>>>>>> included in these emails, example Test Kitchen version is 1.4.0.beta.2.
>>>>>>
>>>>>> Thank you,
>>>>>> Lloyd
>>>>>>
>>>>>>
>>>>>>
>>
>