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

Unable to deploy apicast-production after upgrading from 2.1

    XMLWordPrintable

Details

    • Hide

      1) Have a existing 2.1 on premise instalation of 3scale
      2) Follow these instructions
      3) In Openshift you should see apicast-production failing
      Alternatively you can try to test echo API or any other API on staging gateway, it should fail as well.

      Show
      1) Have a existing 2.1 on premise instalation of 3scale 2) Follow these instructions 3) In Openshift you should see apicast-production failing Alternatively you can try to test echo API or any other API on staging gateway, it should fail as well.

    Description

      I followed these instructions on how to upgrade from 2.1 to 2.2-ER2 and I am currently unable to deploy apicast-production.

      Problem is also present when trying to test echo or any other API through staging gateway, which means that problem is probably with fetching configuration from master. That could mean that this and https://issues.jboss.org/browse/THREESCALE-809 are caused by similar or same problem

      I have attached logs from 2 different apicast deployments and one staging.

      Attachments

        Issue Links

          is blocked by

          Feature Request - Feature requests from customers and/or users THREESCALE-551 Upgrade path from 2.1 to 2.2

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. THREESCALE-809 Can't login into master portal when upgrading from 2.1

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              Unassigned Unassigned
              phala@redhat.com Petr Hála
              Petr Hála Petr Hála
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: