Details
Description
3scale on-prem tries to send requests to segment.io. When it's not reachable, system-provider pod throws this exception.
execution expired
/opt/rh/rh-ruby23/root/usr/share/ruby/net/http.rb:880:in `initialize'
/opt/rh/rh-ruby23/root/usr/share/ruby/net/http.rb:880:in `open'
/opt/rh/rh-ruby23/root/usr/share/ruby/net/http.rb:880:in `block in connect'
/opt/rh/rh-ruby23/root/usr/share/ruby/timeout.rb:101:in `timeout'
/opt/rh/rh-ruby23/root/usr/share/ruby/net/http.rb:878:in `connect'
/opt/rh/rh-ruby23/root/usr/share/ruby/net/http.rb:863:in `do_start'
/opt/rh/rh-ruby23/root/usr/share/ruby/net/http.rb:852:in `start'
/opt/rh/rh-ruby23/root/usr/share/ruby/net/http.rb:1384:in `request'
/opt/system/vendor/bundle/ruby/2.3.0/gems/analytics-ruby-2.0.13/lib/segment/analytics/request.rb:53:in `post'
/opt/system/vendor/bundle/ruby/2.3.0/gems/analytics-ruby-2.0.13/lib/segment/analytics/worker.rb:45:in `run'
/opt/system/vendor/bundle/ruby/2.3.0/gems/analytics-ruby-2.0.13/lib/segment/analytics/client.rb:349:in `block (2 levels) in ensure_worker_running'
Exception -- {:error_message=>"Connection error: execution expired", :parameters=>{:status=>-1}}
Since the request is meaningless on 3scale on-prem, 3scale on-prem should not send request to segment.io.
Attachments
Issue Links
- links to