-
Bug
-
Resolution: Done
-
Critical
-
SaaS, 2.11.0 GA
-
False
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Current behaviour
When APICAST_PATH_ROUTING is enabled and the config is being reloaded but only some of the services can be fetched from system due to some unavailability of the system service then APIcast doesn't fall back to the stale configuration. This causes a 404 even though the services are still cached in the gateway from the previous configuration.
Expected behaviour
All stale config service objects can be referenced in the cache in case some were not refreshed successfully.
Further discussion on the source of the issue in THREESCALE-5769
- is incorporated by
-
THREESCALE-8508 Loading configuration via /admin/api/account/proxy_configs
- Closed