Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-3380

It's not possible to create a service from time to time

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • None
    • 2.6 GA
    • Backend
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started

      In integreatly QE we have automated test, which basically follows the part from walkthrough 2 ("Managing and protecting APIs using API management" from Integreatly). First post request we do to 3scale is something like:

      axios.post(`${threeScaleDashboardUrl}/admin/api/services.json`, {
            access_token: accessToken,
            name: threeScaleServiceName,
            system_name: threeScaleServiceName,
          });
      

      Unfortunately this fails from time to time (we haven't seen anything like that in 2.5). I can see the following error in `system-provider` container log:

      [eefb8667-f9bd-40bc-bd3b-d967c74df5fe] [3scale-admin.apps.tremes-cdb1.open.redhat.com] [66.187.233.202] Enqueued ZyncWorker#94c0e032fac8d50772bffd23 with args: ["f507f009-6142-42f7-829a-41b8e18d0d56", {:type=>"Service", :id=>3, :parent_event_id=>"65510199-546e-4603-9502-9bf7afb73859", :parent_event_type=>"OIDC::ServiceChangedEvent", :tenant_id=>2}]
      [eefb8667-f9bd-40bc-bd3b-d967c74df5fe] [3scale-admin.apps.tremes-cdb1.open.redhat.com] [66.187.233.202] PermissionEnforcer#ensure clear level
      [eefb8667-f9bd-40bc-bd3b-d967c74df5fe] [3scale-admin.apps.tremes-cdb1.open.redhat.com] [66.187.233.202] PermissionEnforcer: level = 
      [eefb8667-f9bd-40bc-bd3b-d967c74df5fe] [3scale-admin.apps.tremes-cdb1.open.redhat.com] [66.187.233.202] Completed 500 Internal Server Error in 5219ms (ActiveRecord: 42.5ms)
      Exception -- [eefb8667-f9bd-40bc-bd3b-d967c74df5fe] [3scale-admin.apps.tremes-cdb1.open.redhat.com] [66.187.233.202] {:exception=>{:class=>ThreeScale::Core::APIClient::ConnectionError, :message=>"ThreeScale::Core::APIClient::ConnectionError: execution expired", :backtrace=>["/opt/system/vendor/bundle/ruby/2.4.0/gems/pisoni-1.26.0/lib/3scale/core/api_client/operations.rb:110:in `rescue in api_http'", "/opt/system/vendor/bundle/ruby/2.4.0/gems/pisoni-1.26.0/lib/3scale/core/api_client/operations.rb:99:in `api_http'", "/opt/system/vendor/bundle/ruby/2.4.0/gems/pisoni-1.26.0/lib/3scale/core/api_client/operations.rb:186:in `api'", "/opt/system/vendor/bundle/ruby/2.4.0/gems/pisoni-1.26.0/lib/3scale/core/api_client/operations.rb:74:in `api_do_put'"]}, :parameters=>{}}
      [eefb8667-f9bd-40bc-bd3b-d967c74df5fe] [3scale-admin.apps.tremes-cdb1.open.redhat.com] [66.187.233.202] 
      ThreeScale::Core::APIClient::ConnectionError (ThreeScale::Core::APIClient::ConnectionError: execution expired):
        app/lib/backend/model_extensions/service.rb:26:in `update_backend_service'
        app/models/account/provider_methods.rb:318:in `block in create_service'
        app/models/account/provider_methods.rb:317:in `create_service'
        app/controllers/admin/api/services_controller.rb:47:in `create'
        lib/api_authentication/by_access_token.rb:159:in `enforce'
        lib/api_authentication/by_access_token.rb:109:in `enforce_access_token_permission'
        app/controllers/admin/api/base_controller.rb:40:in `block in notification_center'
        lib/notification_center.rb:30:in `silent_about'
        app/controllers/application_controller.rb:179:in `silent_about'
        app/controllers/admin/api/base_controller.rb:39:in `notification_center'
        lib/three_scale/middleware/multitenant.rb:116:in `_call'
        lib/three_scale/middleware/multitenant.rb:111:in `call'
        lib/action_dispatch/rails5_ssl.rb:86:in `call'
      
      
      66.187.233.202 - - [04/Sep/2019:12:48:59 +0000] "POST /500 HTTP/1.1" 500 48 5.2289
      

              dortiz-1 David Ortiz (Inactive)
              tremes1@redhat.com Tomas Remes
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: