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

Apicast fails to process requests is some cases if versionOverride is used

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 2.14.0 GA
    • Gateway
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Hide
      1. deploy staging apicast via Apicast Operator
          cacheConfigurationSeconds: 0
          configurationLoadMode: lazy
          deploymentEnvironment: staging
      1. create service one (e.g. with httpbin backed)
      2. create service two (e.g. with httpbin backed) but set OpenID Connect Issuer to "example.com:81" or other url that will cause timeout
      3. Apicast works as expected at this time:
        1. calls to service one gets 200
        2. calls to service two will get 404
      4. add override into APIcast object for a service one with the latest configuration version like:
          serviceConfigurationVersionOverride:
            '1': '1'
      5. after Apicast is redeployed:
        1. calls to service one will get 404
        2. calls to service two will get 404
      Show
      deploy staging apicast via Apicast Operator cacheConfigurationSeconds: 0 configurationLoadMode: lazy deploymentEnvironment: staging create service one (e.g. with httpbin backed) create service two (e.g. with httpbin backed) but set OpenID Connect Issuer to "example.com:81" or other url that will cause timeout Apicast works as expected at this time: calls to service one gets 200 calls to service two will get 404 add override into APIcast object for a service one with the latest configuration version like: serviceConfigurationVersionOverride:     '1' : '1' after Apicast is redeployed: calls to service one will get 404 calls to service two will get 404

      When serviceConfigurationVersionOverride is set and there is a services with OIDC issuer which timeouts, Apicast will respond 404 to all calls for all services.

        1. apicast-after-log
          12 kB
        2. apicast-before-log
          8 kB
        3. apicast-config-mdujava-one-sandbox-1.json
          4 kB
        4. apicast-config-mdujava-two-sandbox-5.json
          4 kB
        5. overrideAPIcast.log
          8 kB
        6. plainAPIcast.log
          11 kB

              Unassigned Unassigned
              mdujava@redhat.com Matej Dujava
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: