Bug 1171747 - It takes a very long time to run 'bundle install' in ruby-1.8 app compare with ruby-1.9
Summary: It takes a very long time to run 'bundle install' in ruby-1.8 app compare wit...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: ImageStreams
Version: 2.1.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: ---
Assignee: Jason DeTiberus
QA Contact: libra bugs
URL:
Whiteboard:
Depends On: 1089967
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-08 14:19 UTC by Scott Dodson
Modified: 2015-01-22 19:32 UTC (History)
10 users (show)

Fixed In Version: rubygem-thor-0.18.1-2.el6 rubygem-net-http-persistent-2.3.2-4.el6 rubygem-bundler-1.3.5-4.el6
Doc Type: Bug Fix
Doc Text:
Cause: Ruby Bundler for ruby18 applications was out of date and had compatibility issues with rubygems.org. Consequence: ruby18 applications that used bundle install would take prohibitively long to deploy. Fix: Ruby Bundler has been updated. Result: bundle install completes in a timely manner.
Clone Of: 1089967
Environment:
Last Closed: 2015-01-22 19:32:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0078 0 normal SHIPPED_LIVE Red Hat OpenShift Enterprise 2.1.10 bug fix update 2015-01-23 00:31:38 UTC

Comment 5 Gaoyun Pei 2014-12-10 02:41:14 UTC 
Verify this bug on puddle 2.1.z/2014-12-09.2

[root@dhcp-129-188 rb18]# time bundle install
Fetching gem metadata from https://rubygems.org/..........
Resolving dependencies...
Using rack (1.5.2)
Installing ref (1.0.5)
Using bundler (1.5.3)
Your bundle is complete!
Use `bundle show [gemname]` to see where a bundled gem is installed.

real	0m14.144s
user	0m1.506s
sys	0m0.111s
Comment 7 errata-xmlrpc 2015-01-22 19:32:28 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0078.html
Note You need to log in before you can comment on or make changes to this bug.