Manually resync auto created routes in 3scale

Solution Verified - Updated -

Issue

  • When deploying 3scale using the operator, there were issues with system-* pods due to system-mysql deployment error.
  • The error for the system-mysql failure was due to reusing the same PV without removing the previous database data. We have removed the old data from the PV and redeployed the system-mysql pod successfully.
  • Now all the 3scale components are running without any errors.
  • When we try to view the admin-portal URL in the routes, it is missing in the route listing.
  • How can we trigger a re-sync of routes from 3scale to OpenShift?

Environment

  • Red Hat 3scale API Management
    • 2.6+ On-Premises

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content