Do we have any idea what is causing the intermittent errors pulling
rubygems on the Rackspace slaves? The errors take the form of:
15:12:36 ERROR: While executing gem …
(Gem::RemoteFetcher::FetchError)15:12:36 Errno::ETIMEDOUT:
Connection timed out - connect(2) for "rubygems.global.ssl.fastly.net"
port 443 (https://api.rubygems.org/gems/bundler-1.12.5.gem)15:12:36
Looks like we may not be the only people experiencing this issue currently:
http://help.rubygems.org/discussions/problems/22609-intermittent-problems-when-pulling-gems
Do we have any idea what is causing the intermittent errors pulling
rubygems on the Rackspace slaves? The errors take the form of:15:12:36 ERROR: While executing gem … (Gem::RemoteFetcher::FetchError)15:12:36 Errno::ETIMEDOUT: Connection timed out - connect(2) for “rubygems.global.ssl.fastly.net” port 443 (https://api.rubygems.org/gems/bundler-1.12.5.gem)15:12:36 + result=1
–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University
–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University
> Do we have any idea what is causing the intermittent errors pulling
> rubygems on the Rackspace slaves? The errors take the form of:
>
> 15:12:36 ERROR: While executing gem … (Gem::RemoteFetcher::FetchError)15:12:36 Errno::ETIMEDOUT: Connection timed out - connect(2) for "rubygems.global.ssl.fastly.net" port 443 (https://api.rubygems.org/gems/bundler-1.12.5.gem)15:12:36 + result=1
>
>
>
I had similar problem when I've used docker compose to build foreman, you
could do something like that which will fail less often:
bundle install --clean --retry=100 --jobs=10 Ohad
–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.