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

Unable to update mapping rules for Istio services after updating from 2.5 to 2.6

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • None
    • 2.6 ER1
    • System
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Hide

      1) Deploy 2.5
      2) Create new Istio service
      3) Update to 2.6
      4) Try to update mapping rules in UI
      5) Notice that no changes were applied (It should fail with Cannot update the staging configuration message)

      Show
      1) Deploy 2.5 2) Create new Istio service 3) Update to 2.6 4) Try to update mapping rules in UI 5) Notice that no changes were applied (It should fail with Cannot update the staging configuration message)
    • 3scale 2019-07-01

      When you update from 2.5 to 2.6 you are unable to change mapping rules for any existing Istio services.

      When you try to update mapping rules from integration page, it will fail with Cannot update the staging configuration.

      Based on my investigation I think it is because proxy configuration in 2.6 has these new fields which are now required.

            "error_headers_limits_exceeded":"text/plain; charset=us-ascii",
            "error_status_limits_exceeded":429,
            "error_limits_exceeded":"Usage limit exceeded"
      

      These fields are not present in 2.5 which causes proxy updates to fail because these required fields are missing.

      You can workaround this by adding the new staging configuration from API with the new fields, I don't think its sufficient enough for Istio because the staging configuration is not visible.

              Unassigned Unassigned
              phala@redhat.com Petr Hála (Inactive)
              Hery Ramihajamalala Hery Ramihajamalala (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: